documentation logo
All you’ll ever need to know about Declarative Webhooks and how to get started.

Pages

Initiate a Sequence Using a Record-Triggered Flow (Automatic Trigger)

Start a Callout Sequence automatically with a Record-Triggered Flow

One way to initiate the callout sequence is automatically with a Record-Triggered flow.

To use the Callout Sequence in a record-triggered flow, you will start by going into Set Up and selecting Flows under Process Automation (be sure to check out Salesforce documentation on Flows as well!). Click “New Flow” and select “Record-Triggered Flow”. Add your object and enter conditions for when the flow is triggered, and make sure to select “Actions and Related Records” when asked “Optimize the Flow for”.

Now, you can add an Action element to the flow. As an Action, search for “Invoke Callout Sequence”. You can reference the callout sequence by using the Sequence Developer Name or using the Sequence Id. Using the Developer Name action is recommended because it makes it easier to deploy and doesn’t hardcode record ids into your Salesforce setup.

 

After providing a label, name and description, set the Input Values.

If you are using the Sequence Developer Name, you need to provide the Sequence’s developer name. If you’re using the Sequence Id, you need to provide the Sequence’s Salesforce Id. You can identify your Sequence Template Id or Developer Name under the Administration tab, Callout Sequences subtab in the Declarative Webhooks app. If there is no Developer Name displayed, it means you are using an older version of the template. To generate the developer name, edit the callout template, save and the developer name will be automatically generated.

 

Then, you have to provide the record Id that is going to be used for this sequence. You can use the record that started the flow or a related record.

Be sure to Activate your process and test by either creating or editing a record associated with your Main Object.

We recommend testing this in your Sandbox before Production.