Actions25
Overview
This node interacts with the Resend API to manage and retrieve information about email broadcasts. Specifically, the Broadcast - Get operation fetches details of a broadcast by its unique ID. This is useful when you want to obtain the current state or metadata of a specific broadcast, such as its content, audience, subject, sender, and other related information.
Common scenarios:
- Retrieving the details of a scheduled or sent broadcast for reporting or auditing.
- Fetching broadcast data to display in dashboards or logs.
- Verifying broadcast content before sending or updating.
Practical example:
You have a broadcast campaign identified by bc_123456 and want to check its status and content before triggering it or analyzing its performance. Using this node operation, you provide the broadcast ID and get back all relevant broadcast details from the Resend service.
Properties
| Name | Meaning |
|---|---|
| Broadcast ID | The unique identifier of the broadcast to retrieve (e.g., bc_123456). Required field. |
Output
The output is a JSON object containing the full details of the requested broadcast as returned by the Resend API. This typically includes fields such as:
id: The broadcast's unique ID.name: Internal name of the broadcast.audience_id: The ID of the audience targeted by the broadcast.from: Sender email address.subject: Subject line of the broadcast email.reply_to: Reply-to email address.html: HTML content of the broadcast message.text: Plain text content of the broadcast message.- Other metadata related to the broadcast status and configuration.
The node does not output binary data for this operation.
Dependencies
- Requires an active connection to the Resend API via an API key credential.
- The API key must have permissions to access broadcast resources.
- Network connectivity to
https://api.resend.comis required. - No additional environment variables are needed beyond the configured API key credential.
Troubleshooting
Common issues:
- Invalid or missing Broadcast ID will cause the API request to fail.
- Expired or incorrect API key credentials will result in authentication errors.
- Network issues may prevent successful communication with the Resend API.
Error messages:
"404 Not Found": The specified broadcast ID does not exist. Verify the ID is correct."401 Unauthorized": API key is invalid or lacks permission. Check your API key setup."400 Bad Request": Input parameters are malformed or missing. Ensure the Broadcast ID is provided.
Resolution tips:
- Double-check the Broadcast ID format and value.
- Confirm that the API key credential is correctly configured and has necessary permissions.
- Test network connectivity to the Resend API endpoint.
- Enable "Continue On Fail" in the node settings to handle errors gracefully during workflows.