Actions12
- Mail Actions
- Contact Actions
- Broadcast Actions
Overview
The node provides integration with a service that manages email broadcasts, contacts, and mail sending. Specifically, for the Delete Broadcast operation under the Broadcast resource, it allows users to delete an existing broadcast by specifying its unique broadcast ID. This is useful in scenarios where a scheduled or previously sent broadcast needs to be canceled or removed from the system.
Practical examples include:
- Removing a mistakenly created broadcast before it is sent.
- Cleaning up old or test broadcasts from the system.
- Managing broadcast lifecycle programmatically within an automation workflow.
Properties
| Name | Meaning |
|---|---|
| Broadcast ID | The unique identifier of the broadcast to be deleted. It must be provided as a string (e.g., UUID format). |
Output
The output of this operation typically contains JSON data indicating the result of the deletion request. This may include confirmation of successful deletion or error details if the broadcast could not be found or deleted. The exact structure depends on the underlying API response but generally confirms whether the broadcast was successfully removed.
No binary data output is expected for this operation.
Dependencies
- Requires an API key credential for authenticating with the external Resend service.
- The node depends on the Resend API endpoints related to broadcast management.
- Proper configuration of the API authentication credentials in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an invalid or non-existent Broadcast ID will likely result in an error indicating the broadcast was not found.
- Missing or incorrect API credentials will cause authentication failures.
- Network connectivity issues can prevent communication with the external API.
Error messages and resolutions:
- "Broadcast not found": Verify the Broadcast ID is correct and exists.
- "Authentication failed": Check that the API key credential is correctly configured and valid.
- Timeout or network errors: Ensure stable internet connection and that the API endpoint is reachable.
Links and References
- Resend API Documentation (general reference for API capabilities)
- n8n documentation on creating custom nodes