Actions25
Overview
This node interacts with the Resend API to manage email broadcasts, specifically allowing you to update an existing broadcast. Updating a broadcast means modifying its content or metadata such as the audience it targets, sender information, subject, and message body in both HTML and plain text formats.
Typical use cases include:
- Changing the recipient audience of a scheduled broadcast.
- Editing the email content before sending.
- Updating the sender or reply-to addresses.
- Adjusting the internal name used for reference.
For example, if you have a newsletter broadcast scheduled but want to update the subject line or add a personalized greeting in the HTML content, this node operation enables that without creating a new broadcast from scratch.
Properties
| Name | Meaning |
|---|---|
| Broadcast ID | The unique identifier of the broadcast you want to update (e.g., bc_123456). |
| Broadcast Content | A collection of fields to update the broadcast's details: |
| - Audience ID | The ID of the audience to send the broadcast to (only for update operation). |
| - From | Sender email address, optionally including a friendly name (e.g., "Your Name <sender@domain.com>"). |
| - HTML Content | The HTML version of the email message. Supports variables like `{{{FIRST_NAME |
| - Name | Internal friendly name for the broadcast, used only for reference within the system. |
| - Reply To | Reply-to email address(es), comma-separated if multiple. |
| - Subject | The subject line of the email broadcast. |
| - Text Content | The plain text version of the email message. |
Output
The node outputs JSON data representing the updated broadcast object returned by the Resend API. This typically includes all the broadcast's properties after the update, such as its ID, audience, content fields, status, timestamps, and other metadata.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node makes HTTP requests to the Resend API endpoints.
- Ensure the API key has permissions to update broadcasts.
- No additional environment variables are required beyond the API key credential.
Troubleshooting
- Invalid Broadcast ID: If the provided broadcast ID does not exist or is malformed, the API will return an error. Verify the ID format and existence.
- Permission Denied: Insufficient API key permissions will cause authorization errors. Confirm the API key has rights to update broadcasts.
- Malformed Content: Invalid HTML or unsupported variables in the content fields may cause the API to reject the update. Validate your HTML and placeholders.
- Network Issues: Connectivity problems can cause request failures. Check network access and API endpoint availability.
- Partial Updates: Only provide fields you want to change; omitting others leaves them unchanged. Sending empty strings may clear those fields unintentionally.
If the node throws an error, enabling "Continue On Fail" allows processing subsequent items while logging the error message in the output JSON under an error property.
Links and References
- Resend API Documentation - Broadcasts
- Resend API Authentication
- n8n HTTP Request Node Documentation (for understanding underlying HTTP calls)