Resend icon

Resend

Interact with Resend API for emails, domains, API keys, broadcasts, audiences, and contacts

Actions25

Overview

This node integrates with the Resend API to manage email-related resources such as audiences, broadcasts, contacts, domains, API keys, and emails. Specifically, for the Audience - Get operation, it retrieves detailed information about a specific audience by its unique ID.

Common scenarios where this node is beneficial include:

  • Fetching audience details to verify or display subscriber lists.
  • Integrating audience data into workflows for targeted email campaigns.
  • Automating audience management tasks within larger marketing automation processes.

For example, you might use this node to get the details of an audience before sending a broadcast email campaign to ensure the correct group is targeted.

Properties

Name Meaning
Audience ID The unique identifier of the audience to retrieve (e.g., aud_123456). This is required to specify which audience's details to fetch.

Output

The node outputs a JSON object representing the audience details returned from the Resend API. This typically includes fields such as the audience's ID, name, creation date, and possibly other metadata related to the audience.

Example output structure (simplified):

{
  "id": "aud_123456",
  "name": "Newsletter Subscribers",
  "created_at": "2024-01-01T12:00:00Z",
  // ... other audience properties
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating requests to the Resend API.
  • The node makes HTTP requests to https://api.resend.com/audiences/{audienceId} endpoint.
  • Ensure the API key has permissions to access audience data in the Resend service.

Troubleshooting

  • Invalid Audience ID: If the provided Audience ID does not exist or is malformed, the API will return an error. Verify the ID format and existence.
  • Authentication Errors: Missing or invalid API key credentials will cause authentication failures. Confirm that the API key is correctly configured and active.
  • Network Issues: Connectivity problems can prevent successful API calls. Check network settings and Resend API status.
  • Rate Limits: Excessive requests may trigger rate limiting by the API. Implement retry logic or reduce request frequency if needed.

Error messages from the node will typically include the API response message. Use these messages to diagnose issues, such as permission errors or resource not found.

Links and References

Discussion