Sequences
Create Sequence
Create an automation sequence with AI-generated or explicit email/action steps
POST
Create Sequence
Create Sequence
Create an automation sequence that sends emails based on triggers. You can either:- Provide a
goalto have AI generate the email content - Provide
stepswith explicit email content and actions such as Stripe discount creation
Request
Name for the sequence
Trigger type:
contact_added, tag_added, segment_entered,
event_received, inactivity, or frequencyList ID (for
contact_added trigger)Tag name (for
tag_added trigger)Segment ID (for
segment_entered trigger)Event name (for
event_received, inactivity, frequency triggers)Event property filters (for the
event_received trigger only, maximum 10).
The sequence only starts when the triggering event’s properties match ALL
filters. Use a dot-path into the event properties; use [] to match items
inside arrays, for example lineItems[].providerProductId.Days of inactivity (for
inactivity trigger)For
inactivity triggers, when to start counting for subscribers who have
never performed the event: sequence_created_at or subscriber_created_at.
Defaults to sequence_created_at.Minimum event count (for
frequency trigger)Time window in days (for
frequency trigger)Re-entry mode:
unlimited, one_time, or matching_field. Defaults to
matching_field for Shopify replenishment and back-in-stock events, otherwise
unlimited. matching_field is only valid for event_received sequence
triggers.Dot-path event property used by
matching_field, such as order.id or
product.providerVariantId. Leave empty for the built-in Shopify
product/variant default.Optional auto-stop condition. Use
has_tag to end the sequence when a
subscriber gets a tag, does_not_have_tag when a tag is removed,
event_received when an event is tracked, added_to_list when a subscriber
joins a list, removed_from_list when a subscriber leaves a list, or none
to clear auto-stop behavior.Option A: AI Generation
Description of what the sequence should accomplish. AI will generate email
content based on this.
Number of emails to generate (default:
5, maximum: 10)Option B: Explicit Content
Array of explicit steps. Email steps must have either
blocks or html; discount steps use type: "create_discount" and can run before an email that references {{discount.code}}.Discount Merge Tags
When acreate_discount step runs, later emails in the same sequence can use discount merge tags from the most recent created discount:
{{discount.code}}{{discount.percentOff}}{{discount.amountOff}}{{discount.currency}}{{discount.expiresAt}}
Enrollment Modes
Usematching_field for event-triggered sequences where each run belongs to a specific object in the event payload. It lets a subscriber have separate active runs for different products, variants, orders, subscriptions, or other event-scoped objects, while blocking duplicate active runs for the same resolved field. Set enrollmentFieldPath for custom events, or send sequenceEnrollmentKey, enrollmentKey, or common product/variant fields in the event properties.
Event-Personalized Sequence Emails
If you create a sequence withtrigger: "event_received", the event payload that enrolls the subscriber is available inside sequence emails through event. merge tags.
For example, if your app sends:
{{event.city}}{{event.alert.maxSpeed}}{{event.duration.hours|a few}}
Examples
AI-Generated Content
Explicit Content with Blocks
Explicit Content with HTML (Auto-converted)
Use this when migrating from other platforms or when you have existing HTML templates (React Email, MJML, etc.).Explicit Discount Action
Use this when you want Sequenzy to generate a Stripe promotion code before sending a follow-up email. Connect Stripe in Settings before enabling the sequence.Inactivity Sequence
Product-Scoped Purchase Sequence (Property Filters)
UsepropertyFilters to start a purchase sequence only for one specific product, for example to deliver a digital product file. Use lineItems[].providerProductId for ecommerce.order_placed events, or productIds for Stripe saas.purchase events.
Event-Triggered Sequence With {{event.*}}
Responses
Notes
- The sequence is created in
draftstatus. UsePOST /api/v1/sequences/{id}/enableto activate it. - For backwards compatibility,
POST /v1/sequencesis still accepted as an alias. - When using email
steps, each email step creates an email template in your account that can be edited later. - Sequences with
create_discountsteps require a connected Stripe integration before activation. - When using
goal, AI generates content asynchronously. PollGET /api/v1/sequences/{id}to check enrichment status. - The first step typically has no delay (sends immediately after trigger).
- For
event_receivedsequences, properties sent toPOST /api/v1/subscribers/eventsare available as{{event.*}}merge tags in sequence emails. - When using
htmlin steps, the content is automatically converted to Sequenzy blocks using AI. This supports:- Plain HTML
- React Email rendered output
- MJML compiled output
- Any HTML-like email content
Create Sequence