Actions25
Overview
This node operation creates a new email broadcast using the Resend API. A broadcast is a mass email sent to a specific audience, such as a newsletter or promotional message. This operation is useful for marketers, communication teams, or anyone who needs to send bulk emails to a defined group of recipients.
Typical use cases include:
- Sending newsletters to subscribers.
- Announcing product updates or promotions to customers.
- Distributing event invitations or company announcements.
By configuring the broadcast's name, target audience, and content (HTML and/or plain text), users can automate and manage their email campaigns efficiently.
Properties
| Name | Meaning |
|---|---|
| Broadcast Name | The name of the broadcast (e.g., "My Newsletter"). |
| Audience ID | The identifier of the audience to which this broadcast will be sent. |
| Broadcast Content | Collection of content details including: |
| - From: Sender email address (can include friendly name, e.g., "Your Name sender@domain.com"). | |
| - Subject: Email subject line. | |
| - Reply To: Reply-to email address(es), comma-separated if multiple. | |
| - HTML Content: The HTML version of the email body, supporting variables like {{{FIRST_NAME}}}. | |
| - Text Content: The plain text version of the email body. | |
| - Name: Internal friendly name for the broadcast (for reference only). |
Output
The node outputs a JSON object representing the created broadcast as returned by the Resend API. This typically includes details such as the broadcast ID, name, audience ID, content fields, creation timestamps, and status.
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node makes HTTP requests to
https://api.resend.com/broadcastsendpoint. - Proper configuration of the API key in n8n credentials is necessary.
Troubleshooting
- Authentication errors: Ensure the API key credential is correctly set up and has the required permissions.
- Invalid audience ID: Verify that the provided audience ID exists and is accessible.
- Missing required fields: The broadcast name and audience ID are mandatory; ensure they are provided.
- Malformed email addresses: The "From" and "Reply To" fields should be valid email formats; otherwise, the API may reject the request.
- API rate limits or network issues: Temporary failures might occur due to API limits or connectivity; retrying may help.
Error messages from the API will generally indicate the cause, such as missing parameters or invalid values. Review the error message and adjust inputs accordingly.