Actions25
Overview
This node integrates with the Resend API to manage and send email broadcasts, among other email-related resources. Specifically, the Broadcast - Send operation triggers sending a previously created broadcast email campaign to its designated audience.
Use cases include:
- Sending newsletters or promotional emails to a large audience.
- Triggering scheduled or immediate broadcast campaigns.
- Automating email marketing workflows by integrating broadcast sends into larger automation sequences.
For example, after creating and customizing a broadcast campaign in Resend, you can use this node to programmatically send that broadcast to all subscribers in the specified audience.
Properties
| Name | Meaning |
|---|---|
| Broadcast ID | The unique identifier of the broadcast you want to send (e.g., bc_123456). |
Output
The node outputs the JSON response returned by the Resend API when sending a broadcast. This typically includes details about the broadcast send request status, such as confirmation that the broadcast was queued or sent successfully.
The output is structured as:
{
"json": {
// Response object from Resend API for sending a broadcast
},
"pairedItem": {
"item": <index_of_input_item>
}
}
No binary data is produced by this operation.
Dependencies
- Requires an active API key credential for the Resend service.
- The node makes HTTP requests to the Resend API endpoints.
- Ensure the API key has permissions to send 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 in your Resend account.
- Authentication Errors: Missing or invalid API key will cause authentication failures. Confirm the API key is correctly configured and has necessary permissions.
- Network Issues: Connectivity problems may cause request failures. Check network access and Resend API availability.
- API Rate Limits: Excessive requests might be throttled. Review Resend API rate limits and adjust usage accordingly.
- Empty or Missing Broadcast Content: If the broadcast was not properly created or lacks content, sending may fail. Ensure the broadcast is fully set up before sending.
If errors occur, the node returns the error message in the output JSON under an error field if "Continue On Fail" is enabled.
Links and References
- Resend API Documentation
- Resend Broadcasts API Reference
- n8n Documentation on Creating Custom Nodes