Chainlink Node Setup

  1. Home
  2. Docs
  3. Chainlink Node Setup
  4. External Initiators
  5. Adding EI to Node

Adding EI to Node

Adding External Initiators to Node

Setup a new project in a different folder than the one your node runs on.

mkdir external-initiator cd external-initiator
Add your code to this folder.

Setup a new postgres database
This should not be the same as your Chainlink base.

Create External Initiator keys
Enter the Chainlink nodes CLI and run the following command

chainlink initiators create <NAME> <URL>

NAME:The name you want to use for your external initiator.

URL:The URL of your jobs endpoint. ie:

This will give you the environment variables you need to run your node. Copy the output. It will look something like this:

║ ei_name ║ http://localhost:8080/jobs ║ a4846e85727e46b48889c6e28b555696 ║ dnNfNhiiCTm1o6l+hGJVfCtRSSuDfZbj1VO4BkZG3E+b96lminE7yQHj2KALMAIk ║ iWt64+Q9benOf5JuGwJtQnbByN9rtHwSlElOVpHVTvGTP5Zb2Guwzy6w3wflwyYt ║ 56m38YkeCymYU0kr4Yg6x3e98CyAu+37y2+kMO2AL9lRMjA3hRA1ejFdG9UfFCAE

You now can use ei_name as an initiator in your jobspec. Set a new .env file, and add the respective values


At the time of writing, the output should be in order. For example, in from the output above,
and so on.
Start your EI
Whatever code you used to run your external initiator, pass it the new headers created for the access headers, and then start your service. An easy way to do this is by having it read from the
.env file you just created.

Check out the Conflux External initiator for an example.

You’ll want to test that your job is running properly. Meeting the criteria of your EI and then checking to see if a sample job kicks off is the best way to test this.

To try a real-life example, feel free to follow along with the Conflux EI demo.

Additional external initiator reference

Was this article helpful to you? Yes No

How can we help?