Actions12
- Mail Actions
- Contact Actions
- Broadcast Actions
Overview
The node implements an "Update Broadcast" operation within a broadcast messaging system. It allows users to update the details of an existing broadcast message by specifying its unique ID and modifying various fields such as audience, sender email, subject, message content, reply-to addresses, and internal name.
This node is beneficial in scenarios where you need to modify or correct broadcast messages after their initial creation but before sending or for managing ongoing campaigns. For example, if you want to change the subject line or update the message content of a scheduled broadcast, this node provides that capability.
Practical examples:
- Updating the subject and message content of a promotional email broadcast.
- Changing the sender email address or reply-to list for a customer notification broadcast.
- Modifying the target audience of a broadcast campaign.
Properties
| Name | Meaning |
|---|---|
| Broadcast ID | The unique identifier of the broadcast you want to update. |
| Audience ID | The ID of the audience segment to which the broadcast will be sent. |
| From Email | The sender's email address that appears in the broadcast email. |
| Subject | The subject line of the broadcast email. |
| Message | The main content of the broadcast message; supports plain text or HTML format. |
| Reply To | One or more reply-to email addresses separated by semicolons (;) for responses. |
| Name | A friendly internal name for the broadcast used for reference purposes only. |
Output
The node outputs JSON data representing the result of the update operation on the broadcast. This typically includes confirmation details such as the updated broadcast's ID, status, and any relevant metadata returned by the API.
There is no indication that the node outputs binary data.
Dependencies
- Requires an API key credential for authenticating with the external broadcast service.
- The node depends on the external Resend API service to perform broadcast updates.
- Proper configuration of the API authentication token in n8n credentials is necessary.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Broadcast ID will likely cause errors.
- Missing required fields or incorrect formatting in email addresses (From Email, Reply To) can lead to validation failures.
- Network or authentication errors if the API key is missing, expired, or incorrect.
Error messages and resolutions:
- "Broadcast not found": Verify the Broadcast ID is correct and exists.
- "Invalid email address": Check the formatting of From Email and Reply To fields.
- "Authentication failed": Ensure the API key credential is properly set up and valid.
- "Missing required parameters": Confirm all mandatory fields are provided.
Links and References
- Resend API Documentation (for detailed API usage and broadcast management)
- n8n documentation on creating custom nodes