Actions12
- Mail Actions
- Contact Actions
- Broadcast Actions
Overview
The node named "Resend" integrates with the Resend API and supports multiple resources, including Contacts. For the Contact resource, specifically the "Get Contacts" operation, it retrieves contact information from a specified audience. This node is useful for workflows that need to fetch and process contact lists, such as syncing contacts with other systems, segmenting audiences, or triggering follow-up actions based on contact data.
Practical examples:
- Fetch all contacts from a marketing audience to update a CRM.
- Retrieve contacts to send personalized email campaigns.
- Use contact data to trigger conditional workflow branches in n8n.
Properties
| Name | Meaning |
|---|---|
| Audience ID | The unique identifier of the audience from which to retrieve contacts. Example: "479e3145-dd38-476b-932c-529ceb705947". |
Output
The node outputs an array of JSON objects representing the contacts retrieved from the specified audience. Each object contains the contact details as provided by the Resend API. The exact structure depends on the API response but typically includes fields like contact identifiers, email addresses, names, and any custom attributes associated with the contacts.
No binary data output is indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node depends on the Resend service being accessible and the API key having permissions to read contact data.
- No additional environment variables are explicitly required beyond the API authentication setup.
Troubleshooting
Common issues:
- Invalid or missing Audience ID will result in no contacts being returned or an error.
- Authentication failures due to incorrect or expired API keys.
- Network connectivity problems preventing access to the Resend API.
Error messages and resolutions:
- "Unauthorized" or "Authentication failed": Verify the API key credential is correctly configured and has necessary permissions.
- "Audience not found": Check that the Audience ID is correct and exists in the Resend system.
- Timeouts or network errors: Ensure stable internet connection and that the Resend API endpoint is reachable.
Links and References
- Resend API Documentation (general reference for API endpoints and data structures)
- n8n documentation on Using API Credentials