Triggered Sequences

A triggered sequence sends by itself when a contact does something: joins a list, opens, clicks, converts. You draw the flow of emails, waits and conditions once, and the entry settings above it decide how soon a contact may come back and how many may enter each hour and each day.

Instructions

1. Navigate to Triggered Sequences > Create Sequence. Enter a name for the sequence.
2. Set the sequence entry settings, which sit above the sequence flow and apply to the whole sequence:
   • Days before a contact can re-enter this sequence — 0 to 365. 0 lets a contact enter every time the trigger event fires; any higher value blocks that contact until the set number of days has passed since they last entered. New sequences default to 60.
   • Max contacts entering per 1 hr and Max contacts entering per 24 hrs — optional caps on how many contacts may enter the sequence in each rolling window. Leave a field blank for no cap.
   • Contacts over a cap are dropped, not queued. They are not held back and let in during a later window. Loading 13,000 contacts against a 1 hr cap of 1,000 admits 1,000 contacts; the other 12,000 never enter the sequence.
   • These caps are not the Send Integration caps: Send Integration caps limit how many emails are sent, these limit how many contacts enter the sequence.
3. Define the trigger event: click Edit on the Trigger card > select an event type: Clicked, Opened, Unsubscribed, Added to Contact List via API, Transactional Email API, or Conversion. Optionally narrow the scope — a specific Scheduled Email or Email Content on Clicked and Opened, a Brand on Unsubscribed, a Contact List on Added to Contact List via API.
4. Clicked and Opened fire on real engagement only. An open from an IP address or user agent on our bot list is stored as a bot open, not as an open, so it never starts a sequence and never releases a Wait For on Opened. That list covers mailbox privacy proxies, including Apple Mail Privacy Protection and Google image proxying, and known scanners. Clicks work the same way for bot clicks. Do not tell a user to prefer Clicked over Opened because of proxy opens; that filtering already happened.
5. Add actions by dragging from the left panel or clicking Add nodes. Available actions: Send Email, Add to Contact List, Delay Time (minutes/hours/days), Filter (same types as Segments), If/Else (branch by condition), Wait For (wait until condition met), Wait For/Else (wait with timeout + else path), Split (A/B split by percentage), Data Sync (send contact data to an external endpoint via HTTP — Generic connector for any URL with custom headers/body, or EmailElement connector for the EmailElement API).
6. Configure each action: for Send Email, choose Email Content and Send Integration. For If/Else, add filter conditions (Contact Attributes, Domain Groups, etc.).
7. Build both If and Else paths with their own action chains. Each path can contain any combination of actions.
8. Click Create to save and activate the sequence.
9. A contact who has entered a sequence runs it to the end. Nothing done to a contact list afterwards stops them. Removing the contact from a list, or using Remove All Contacts to empty the list, does not cancel a sequence that is already running for them. The entry caps and the re-entry days only decide who enters, so they do not affect a contact who is already in the sequence either.
10. If fewer contacts entered a sequence than expected, check the entry caps and the re-entry days on the sequence before looking at delivery problems.

Related pages

• Data Sync — Data Sync is a Triggered Sequence action that calls a webhook for every contact that reaches it
• Sequence Actions Reference — covers Available Actions, Action Details, Send Email, Add to Contact List
• Sequence Entry Controls Reference — Entry controls decide which contacts enter a triggered sequence, and how many of them
• Triggered Sequence Walkthrough — every step with screenshots, covering Creating a Sequence, Sequence Entry Settings, Configuring the Trigger
• Trigger Events Reference — A contact who has entered a sequence runs it to the end