Short answer: Drop the "Resend → Resend Create Broadcast" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Audience ID audience_id | string | Required | The Audience ID assigned by Resend. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
From from | string | Required | You <you@yours.com> |
Subject subject | string | Required | Message subject line. |
HTML Body html | string | Required | — |
Reply-To Email reply_to | string | Optional | — |
{"audience_id": "{{trigger.audience_id}}","from": "You <you@yours.com>","subject": "e.g. Quick update","html": "{{trigger.html}}","reply_to": "{{trigger.reply_to}}"}
{"id": "bc_abc","name": "May Newsletter","status": "draft"}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.