Actions25
Overview
This node integrates with the Resend API to manage email-related resources such as emails, domains, API keys, broadcasts, audiences, and contacts. Specifically for the Audience - Create operation, it allows users to create a new audience (a group of email recipients) by specifying an audience name.
Common scenarios where this node is beneficial include:
- Building segmented mailing lists for newsletters or marketing campaigns.
- Organizing contacts into distinct groups for targeted email broadcasts.
- Automating audience creation as part of larger email workflow automations.
For example, you might use this node to create an audience named "Newsletter Subscribers" to which you later add contacts and send broadcasts.
Properties
| Name | Meaning |
|---|---|
| Audience Name | The name of the audience to be created. |
Output
The output JSON contains the response from the Resend API after creating the audience. This typically includes details about the newly created audience such as its unique ID, name, creation timestamp, and other metadata provided by the API.
Example output structure (simplified):
{
"id": "aud_123456",
"name": "Newsletter Subscribers",
"created_at": "2024-06-01T12:00:00Z"
}
No binary data output is produced by this operation.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node makes HTTP requests to
https://api.resend.com/audiencesendpoint. - Ensure the API key has permissions to create audiences in the Resend service.
Troubleshooting
- Authentication errors: If the API key is invalid or missing, the node will fail to authenticate. Verify that the API key credential is correctly configured.
- Validation errors: If the audience name is missing or invalid, the API may return an error. Make sure the "Audience Name" property is provided and meets any naming requirements.
- API rate limits: Frequent calls may hit rate limits imposed by the Resend API. Implement retry logic or reduce request frequency if needed.
- Network issues: Connectivity problems can cause HTTP request failures. Check network access and proxy settings if applicable.