Build email/SMS automation flows with triggers, steps, waits, splits, and webhooks. Covers welcome series, cart abandonment, post-purchase, win-back, browse abandonment, and custom event-driven flows. Use when: "automation flow", "welcome series", "drip campaign", "cart abandonment flow", "win-back flow", "build flow", or "email sequence".
Build Flow
Help the user design and create automation flows using Nitrosend.
Understand the Goal
Ask what kind of flow they need. Common patterns:
| Flow Type | Trigger Event | Typical Steps |
|---|---|---|
| Welcome series | contact_add | Email 1 (immediate) -> Wait 1d -> Email 2 -> Wait 2d -> Email 3 |
| Cart abandonment | cart_abandoned | Wait 1h -> Email 1 -> Wait 1d -> Email 2 (with discount) |
| Post-purchase | checkout or custom | Email 1 (thank you) -> Wait 3d -> Email 2 (review request) |
| Win-back | Custom event or segment | Email 1 -> Wait 3d -> Split (opened?) -> Yes: Email 2 / No: Email 3 |
| Browse abandonment | browse_abandoned | Wait 2h -> Email with viewed products |
| Onboarding | contact_add or custom | Welcome -> Wait 1d -> Getting started -> Wait 2d -> Feature highlight |
| Re-engagement | Custom trigger | Email 1 -> Wait 7d -> Split (engaged?) -> Yes: normal cadence / No: final offer |
Design the Flow
Available Step Types
| Step | Required Props | Notes |
|---|---|---|
email | subject + (design or body) | Design uses {sections, theme} |
sms | body | SMS text content |
wait | duration (seconds) | 3600=1hr, 86400=1day, 604800=1week |
split | filters, yes steps, no steps | Conditional branching; splits may nest inside yes/no branches |
emit_event | event_name | Fire event to trigger other flows |
webhook | url | POST or PUT to external URL |
subscribe | channel (phone/email/all) | Opt contact in |
unsubscribe | channel (phone/email/all) | Opt contact out |
Split Filters
Use the filter schema returned by the intent response or nitro://schema; do
not assume this document is an exhaustive registry. Common current filters
include contact identity and subscription fields, tags and lists, creation and
interaction timestamps, delivery/engagement metrics such as
contact_last_opened_at and contact_last_clicked_at, event history, and
custom or enrichment fields. Use only names and predicates accepted by the live
schema.
Prefer behavior-based branches when the necessary evidence exists. Keep waits and message frequency proportionate to the user's audience and test the cadence against account performance rather than asserting universal timings.
Create the Flow
Use nitro_compose_flow with:
name: Descriptive flow nametrigger:{ event: "trigger_event_name" }— optionally addsegment_idorcontact_list_idsteps: Array of step objects
Offer dry_run: true first to preview the flow graph.
Composition contract: any newly authored email step enters the contract
before persistence. Call nitro_compose_flow with composition_mode: "intent".
Treat next_call.input as the selected complete baseline for the flow and its
email steps; preserve and fill it by default. Use the compact
composition_contract.creative_routes menu and start a fresh intent with
creative_route_id to select another ready route (that top-level field applies
one route to the whole sequence; to assign routes per email in a multi-email
flow, use email_baseline_selections entries of action_name + route_id —
plus that email's image_binding_ids when the route is image-led — as the
returned contract describes). If that route lacks frozen
evidence, obtain the exact reported facts. Never fall back silently or invent
evidence.
For image-led routes, follow next_call.image_choice and supply an exact image
URL plus an accurate description. Preserve all contract, binding, user
constraint, and idempotency fields. Optionally validate, then persist with
composition_mode: "draft"; full section authoring is an intentional escape
hatch. The returned metered optional_server_authoring_call
(composition_mode: "generate") may instead author, validate, and persist one
draft. SMS-only flows and rename-only patches do not need email authoring
context.
Review and Approve
- Show the dry-run preview (node types and connections)
- Get user approval on the flow design
- Create for real (without dry_run)
- Review:
nitro_review_deliverywithtarget_type: "flow",target_id, and the exact currentrevision_id(flow reviews require it) - Approve:
nitro_control_deliverywithtarget_type: "flow",target_id,operation: "approve", the exact current draftrevision_id, andexpected_brand_sid(copymeta.current_brand.sidfrom the review result) - Go live:
nitro_control_deliverywithtarget_type: "flow",target_id,operation: "live",revision_id, andexpected_brand_sid
Flow approve, reject, and live all require the exact current draft
revision_id; pause/resume omit it, and resume never publishes a draft.
Every nitro_control_delivery call requires the expected_brand_sid brand
assertion from the result you reviewed — it never switches brands.
Modify Existing Flows
To rebuild an existing flow:
- Use
nitro_compose_flowwithmode: "replace",flow_id,confirm: true,expected_draft_revision_id(the current draft revision), and a stableidempotency_key
To rename or update selected email actions:
- Use
nitro_compose_flowwithmode: "patch",flow_id, anidempotency_key, targeting email actions byaction_name+ theirif_versionconcurrency token
Every non-dry-run persistence mutation (create, rename patch, replace) requires
an idempotency_key; drafts persisted through the composition contract reuse
the stable key supplied by the returned next_call.
Related skills
- Downloads
- Security audit
- Pass
- Last updated
- 3w ago
- Current version
- v1.0.0
- License
- MIT-0
