Email Step
Configure owned Workflow emails, sending behavior, retries, personalization, and queue guarantees.
Send a personalized email to the current subscriber. Workflow gives every EMAIL step a dedicated internal campaign owned by that exact workflow and step.
Workflow ownership
- Internal emails use campaign
type: WORKFLOWand do not appear as broadcast campaigns. - One internal campaign belongs to one workflow step.
- A broadcast campaign or another step's email is duplicated instead of linked directly.
- Deleting or replacing a step cleans up internal campaigns that are no longer referenced by any preserved version.
- Published versions preserve the email references used by existing runs.
When an agent creates or changes an email, it provides complete inline content to configure_workflow_draft. Lumail resolves the owned campaignId in the same transaction.
{
"id": "email-welcome",
"type": "EMAIL",
"name": "Welcome",
"email": {
"subject": "Welcome aboard",
"preview": "Your first steps",
"senderId": "sender-id",
"replyTo": "[email protected]",
"content": {
"type": "doc",
"content": [
{
"type": "paragraph",
"content": [{ "type": "text", "text": "Welcome!" }]
}
]
}
}
}Never use create_campaign for a Workflow email. After configuration, read and render every ID returned in configuredEmails.
Editing a live email: drafts and publishing
A workflow email keeps sending while you edit it, so edits never go live on save.
- Every change to an email step (editor autosave, AI tools, a restore from the history) is saved as that email's draft. Subscribers keep receiving the published version.
- The editor shows Not published on the email and on its canvas card, and the workflow bar shows how many emails are not published. Publish becomes available.
- Send to inbox sends the draft, so you can review the real rendering before publishing.
- Publish saves what you just typed, asks for confirmation when the workflow is active, then publishes the graph and every email draft together: either everything goes live or nothing does. Publishing only email changes does not create a new workflow version.
- Change → Discard unpublished edits returns the email to its published version. Discarded content stays in the email history.
- If the same email is edited in another tab or by a teammate, the stale tab gets an error instead of overwriting the newer draft.
For AI agents and the Tools API
| Need | Tool |
|---|---|
| Rewrite an email (saved as a draft) | configure_workflow_draft |
| See which emails have unpublished edits | get_workflow → emailsWithUnpublishedEdits |
| Read the draft of one email | get_campaign → hasUnpublishedEdits, content |
| Review the draft | render_campaign, send_test_email |
| Drop a draft | discard_workflow_email_draft |
| Make the drafts live | publish_workflow → publishedEmailCampaignIds, newVersion |
publish_workflow also publishes edits a person made in the editor. Check emailsWithUnpublishedEdits and confirm with the user before publishing a live workflow.
Behavior
- Fetches fresh subscriber data before sending
- Skips if subscriber unsubscribed (workflow continues)
- Fails validation when a required owned campaign reference is missing
- Fails if email limit reached
Duplicate Prevention
Each subscriber receives each campaign only once by default.
With Allow Repeats enabled, the subscriber can start another run after repeatCooldownMinutes. Delivery deduplication remains scoped to the run and step so retries do not duplicate accepted sends.
Sending Queue
Workflow emails are queued exactly like campaigns. Each email step is backed by a campaign behind the scenes, so its emails:
- Use the bulk lane, the same one regular campaigns use. Only transactional emails (login codes, notifications) and campaign test emails get instant priority.
- Join your organization's single sending queue, in first in, first out order.
This means a workflow email queued while a large campaign is already sending waits for that campaign to finish draining before it goes out. Workflow emails are not prioritized over campaigns, and campaigns are not prioritized over workflow emails.
Two consequences worth planning around:
- Avoid launching a large campaign during peak workflow activity if the workflow email is time-critical (welcome email, purchase confirmation sequence).
- Sending is never lost when the queue is busy — emails wait their turn, and each recipient is tracked individually so a retry never causes a duplicate.
If sending is suspended (monthly quota reached or plan suspension), the workflow run is paused rather than failed, and resumes automatically once sending is active again.
Verification
For every internal workflow email:
- Read it with
get_campaign. - Compare sender, subject, preview, reply-to, and TipTap content.
- Render it with
render_campaign. - Require non-empty HTML and text plus
hasUnsubscribeLink: true. - Confirm
list_campaignsdoes not expose it as a broadcast.
See Email Sending Queue for the full picture, including how capacity is shared between organizations and plans.
Related Documentation
Email Sending Queue - How campaigns and workflow emails share the queue
Send Email API - Send emails outside workflows
Variables - Personalize email content
Tag Action Links - Add one-click tag actions in email links
Content Deliverability - Optimize email content for inbox placement
Subscriber Events - View email delivery events