ActionResendUpdated September 2026

How do I create a Resend broadcast?

Short answer: You can resend create broadcast in Resend by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Resend Resend Create Broadcast action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.

Resend Create Broadcast in Resend — start free All 5 Resend actions

Resend Create Broadcast in Resend — start free

Inputs

The fields this action accepts.

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	–

Sample request

{
  "audience_id": "{{trigger.audience_id}}",
  "from": "You <you@yours.com>",
  "subject": "e.g. Quick update",
  "html": "{{trigger.html}}",
  "reply_to": "{{trigger.reply_to}}"
}

Returns

{
  "id": "bc_abc",
  "name": "May Newsletter",
  "status": "draft"
}

Use these fields in downstream nodes for routing, logging, or error handling.

Triggered by

Apps that pair well as the trigger for Resend Create Broadcast.

Any of these apps can fire this action as part of a workflow.

Google Sheets → Resend

2 Google Sheets triggers

HubSpot → Resend

18 HubSpot triggers

FAQ

Questions about Resend Create Broadcast.

What does the Resend Create Broadcast action do in Resend?

Creates a marketing-email send to a Resend Audience. For newsletter automation tied to Resend's audience-management features. Separate from transactional Send Email.

What inputs does Resend Create Broadcast require?

Required: Audience ID, From, Subject, HTML Body. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if Resend returns an error?

The run history shows the failed step with its input and the error message Resend returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.

Does Resend Create Broadcast support batch operations?

Run Resend Create Broadcast inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Resend's rate limits.

More actions