Actions12
- Mail Actions
- Contact Actions
- Broadcast Actions
Overview
The node implements integration with a service that supports multiple resources, including Broadcasts. Specifically for the Broadcast resource and the Send Broadcasts operation, it allows users to send broadcast messages (likely emails or similar mass communications) either immediately or scheduled for a later time.
This node is beneficial in scenarios where you want to automate sending marketing campaigns, announcements, or newsletters to a large audience. For example, you can use it to trigger a promotional email broadcast right after a new product launch or schedule a holiday greeting message to be sent at a specific future date and time.
Properties
| Name | Meaning |
|---|---|
| Broadcast ID | The unique identifier of the broadcast message to send. |
| Schedule At | Optional scheduling parameter to send the broadcast later. Accepts natural language (e.g., "in 1 min") or ISO 8601 datetime format (e.g., "2024-08-05T11:52:01.858Z"). |
Output
The node outputs an array of JSON objects representing the result of the broadcast send operation. Each object typically contains details about the broadcast status, such as confirmation of successful scheduling or sending, any errors encountered, and metadata related to the broadcast.
If the broadcast includes binary data (e.g., attachments), the node would handle this accordingly, but based on the provided code and properties, the primary output is JSON structured data confirming the broadcast action.
Dependencies
- Requires an API key credential for authenticating with the external broadcast/email service.
- The node depends on internal modules handling the broadcast resource logic (
broadcast.resource). - No additional environment variables are explicitly required beyond the API authentication token.
Troubleshooting
Common Issues:
- Invalid or missing Broadcast ID will cause the operation to fail.
- Incorrectly formatted scheduling date/time may lead to errors or immediate sending instead of scheduling.
- Network or authentication failures if the API key is invalid or expired.
Error Messages:
- Errors related to invalid Broadcast ID usually indicate the broadcast does not exist or the ID was mistyped.
- Scheduling errors often mention invalid date formats; ensure the date is either natural language parsable or ISO 8601 compliant.
- Authentication errors suggest checking the API key credentials configured in n8n.
Links and References
- Refer to the external broadcast/email service API documentation for detailed information on broadcast IDs and scheduling formats.
- n8n documentation on how to configure API credentials and use custom nodes.