Actions25
Overview
This node integrates with the Resend API to manage email-related resources, including audiences. Specifically, for the Audience resource and the Delete operation, it allows users to delete an existing audience by its unique ID. This is useful when you want to remove an entire group of contacts or subscribers from your email marketing or communication platform.
Common scenarios:
- Cleaning up outdated or unused audiences.
- Removing test or temporary audiences after campaigns.
- Automating audience lifecycle management in workflows.
Practical example:
You have a workflow that automatically deletes an audience once a campaign ends or if the audience is no longer relevant. By providing the Audience ID, this node will call the Resend API to delete that audience.
Properties
| Name | Meaning |
|---|---|
| Audience ID | The unique identifier of the audience to delete (e.g., aud_123456). This is required to specify which audience should be removed. |
Output
The node outputs a JSON object representing the response from the Resend API after attempting to delete the audience. Typically, this will confirm successful deletion or provide error details if the operation failed.
- The output JSON structure corresponds directly to the API's response.
- No binary data is produced by this operation.
Example output JSON might look like:
{
"id": "aud_123456",
"deleted": true
}
or, in case of error:
{
"error": "Audience not found"
}
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node makes HTTP requests to
https://api.resend.com/audiences/{audienceId}using the DELETE method. - Ensure the API key has sufficient permissions to delete audiences.
- No additional environment variables are needed beyond the API key configuration.
Troubleshooting
Common issues:
- Invalid or missing Audience ID: The node requires a valid audience ID; otherwise, the API will return an error.
- Insufficient permissions: If the API key lacks delete permissions, the request will fail.
- Network or connectivity problems: The node depends on external API availability.
Common error messages:
"Audience not found": The provided Audience ID does not exist. Verify the ID is correct."Unauthorized"or"Forbidden": The API key is invalid or lacks permission. Check credentials."Rate limit exceeded": Too many requests sent in a short time. Implement retry logic or reduce frequency.
How to resolve:
- Double-check the Audience ID input.
- Confirm the API key is valid and has appropriate permissions.
- Ensure network connectivity and API endpoint accessibility.
- Use the node’s "Continue On Fail" option to handle errors gracefully in workflows.