Create an automation sequence with AI-generated or explicit email/action steps
Documentation Index
Fetch the complete documentation index at: https://docs.sequenzy.com/llms.txt
Use this file to discover all available pages before exploring further.
goal to have AI generate the email contentsteps with explicit email content and actions such as Stripe discount creationcontact_added, tag_added, segment_entered,
event_received, inactivity, or frequencycontact_added trigger)tag_added trigger)segment_entered trigger)event_received, inactivity, frequency triggers)inactivity trigger)frequency trigger)frequency trigger)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.matching_field, such as order.id or
product.providerVariantId. Leave empty for the built-in Shopify
product/variant default.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.5, maximum: 10)blocks or html; discount steps use type: "create_discount" and can run before an email that references {{discount.code}}.create_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}}matching_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.
trigger: "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}}{{event.*}}draft status. Use POST /api/v1/sequences/{id}/enable to activate it.POST /v1/sequences is still accepted as an alias.steps, each email step creates an email template in your account that can be edited later.create_discount steps require a connected Stripe integration before activation.goal, AI generates content asynchronously. Poll GET /api/v1/sequences/{id} to check enrichment status.event_received sequences, properties sent to POST /api/v1/subscribers/events are available as {{event.*}} merge tags in sequence emails.html in steps, the content is automatically converted to Sequenzy blocks using AI. This supports: