Sequences are automated email workflows that send the right message at the right time based on subscriber actions, tags, segments, or events. They’re the heart of marketing automation in Sequenzy.
Add a subscriber to a list or remove them from a list
Webhook
Call an external URL with subscriber data
When you add an Update Tags step in the builder, you choose whether that step should add a tag or remove one. You can change that choice later by editing the step.When you add an Update Lists step, you choose whether the step should add the subscriber to a list or remove them from one. This is useful for routing contacts into new subscription tracks, suppressing them from a list mid-sequence, or chaining list-triggered sequences together.
Use Run sequence test in the sequence builder when you want to check the whole workflow with one real subscriber before activating or changing a live sequence.Sequence test runs execute the same graph that production uses:
The run starts from the sequence trigger and follows connected steps in order
Branches, conditions, event-property merge tags, discounts, tags, lists, subscriber attributes, and webhooks use the selected subscriber’s real data
Delay and wait steps are compressed with the selected speed multiplier, such as 60x, 120x, 240x, or 480x
Sequence emails are sent through the test-email path with a [TEST] subject prefix
Recent test runs show step-by-step logs, accelerated wait timing, sent-email references, and failures
Non-email actions run for real on the selected subscriber. Use a safe internal
or dedicated test subscriber when checking flows that update tags, lists,
attributes, discounts, or webhooks.
Before starting a run:
Save any pending changes in the builder.
Choose one existing active subscriber. Direct email recipients are not available for live sequence tests because the run needs subscriber state.
Pick a speed multiplier. 120x turns a 1-hour wait into about 30 seconds.
Confirm the run. Sequenzy prevents another queued or running test for the same sequence and subscriber.
Test emails are excluded from the normal sequence sent-email filters, but the run log keeps references to the email send records created during the test.
Personalizing Sequence Emails With Event Properties
When a sequence starts from an event trigger, Sequenzy stores that event’s properties on the sequence run. You can use those values in any later email in the same sequence with event. merge tags.Examples:
{{event.city}}
{{event.windMaxSpeed}}
{{event.alert.maxSpeed}}
This is useful when the event contains context that should stay stable across multiple emails, such as a weather alert region, the purchased plan, or the trial length that started the flow.
Enrollment mode controls whether the same subscriber can enter a sequence again.
Mode
Behavior
unlimited
A subscriber can re-enter after a previous run finishes, but cannot have duplicate active runs.
one_time
A subscriber can enter the sequence once ever.
matching_field
Event-triggered sequences can have one active run per matching event field value.
matching_field is only available when the sequence starts from an event. Use it when the same subscriber may legitimately have multiple active runs, but each run belongs to a different event-scoped object.Examples:
order.id - one active run per order
product.providerVariantId - one active run per product variant
subscription.id - one active run per subscription
In the dashboard, the Matching field path input suggests fields from recent payloads for the selected trigger event. Through the API, CLI, and MCP, set enrollmentMode to matching_field and pass enrollmentFieldPath.
{ "name": "Post-purchase follow-up", "trigger": "event_received", "eventName": "ecommerce.order_placed", "enrollmentMode": "matching_field", "enrollmentFieldPath": "order.id", "goal": "Follow up about this specific order"}
For Shopify back-in-stock and replenishment sequences, you can leave enrollmentFieldPath empty. Sequenzy uses built-in product and variant matching defaults for those events.
Event checks can be scoped with activityScope: this_sequence checks events
received since the contact entered this sequence, previous_email checks events
tied to the last sequence email, and ever checks the contact’s full event
history.
Leave the URL empty to match any tracked click, or enter part of the URL to
match a specific link. Click checks support the same activityScope values:
this_sequence, previous_email, and ever.
Holding existing subscribers and blocking new entry
archived
No longer in use
Paused sequences do not execute nodes. Subscribers already in the sequence stay
at their current step, and new subscribers who match the trigger are not
enrolled while the sequence is paused. When the sequence resumes, due
subscribers continue gradually from the step where they were held.You can also stop new enrollments without pausing the sequence. In that mode,
current subscribers keep moving until completion, but new trigger matches are
not enrolled.Waits are wall-clock based. If a subscriber is waiting three days and the wait
expires while the sequence is paused, the subscriber becomes due but does not
continue until the sequence resumes.
Company sending pauses and account-level restrictions are parent locks, not
manual sequence pauses. An active sequence remains active, still captures new
entrants, and keeps tokens at their current step while email sending is blocked.
The dashboard shows this as Sending paused so you can distinguish it from a
sequence you paused yourself.When sending is restored, due sequence work wakes automatically. If you do not
want a specific sequence to continue after sending is restored, pause that
sequence manually; the manual pause remains until you resume it.
