Skip to main content
The steps parameter on flow_set takes an ordered array of step objects. delay is measured from completion of the previous step, not from launch.
Call reference with topic: "sequence_steps" or "triggers" before authoring a sequence. It returns the live vocabulary the server validates against.

Step types

Step fields

Merge fields

Available in note, shortNote, subject and message: {{firstName}}, {{lastName}}, {{designation}}, {{location}}, {{companyName}}, {{industry}}, {{senderName}}, {{signature}} — plus anything from placeholder_list and any CSV column mapped to customVariable.

Branch conditions

A TRIGGER step branches on one of these conditions. Put the steps for each outcome under yes and no.
A TRIGGER is always the last entry in its list — anything that comes after it goes under yes or no. An omitted branch simply ends the sequence for that lead.

Example sequence

Connect with a note, then branch on acceptance. Accepted leads get a LinkedIn message and, if they don’t reply, an email. Leads who don’t accept within two weeks have their invitation withdrawn.