Sequence triggers

Every sequence has one trigger. It decides who gets enrolled and when.

The five types

• Manual. Nobody is enrolled automatically. You add contacts from the Contacts page, a segment, or the API. Good for one-off outreach.
• Tag added. A contact is enrolled the moment a given tag is applied to them.
• Segment entry. A contact is enrolled when they start matching a segment. Optionally, they're removed if they later stop matching.
• Date field. Fires a set number of days before or after a date stored on the contact (a renewal date, a birthday). Can repeat annually.
• Custom event. Your backend posts an event to POST /api/v1/events and the matching contact is enrolled. The event's properties ride along and are available in every email step as {{ event.* }}. See event-triggered sequences.

Notes

• A contact already mid-flight in a sequence is not enrolled again by the same trigger.
• Suppressed contacts (unsubscribed, bounced, complained) are never enrolled, and the event that would have enrolled them is still consumed.
• The custom_event trigger is the one people reach for when they mean "start a flow from something that happened in my product". The bare events API on its own enrolls nobody; it feeds this trigger.