Actions25
Overview
This node integrates with the Resend API to manage various email-related resources, including contacts, emails, domains, API keys, broadcasts, and audiences. Specifically, for the Contact - Get operation, it retrieves detailed information about a specific contact by its unique ID.
Common scenarios where this node is beneficial include:
- Fetching contact details from an email audience for personalization or verification.
- Integrating contact data retrieval into automated workflows for marketing or customer support.
- Synchronizing contact information between Resend and other systems.
Example use case:
- You have a contact ID from a previous step or external source and want to fetch the full contact record (email, name, subscription status) to decide on further actions like sending targeted emails or updating CRM records.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to retrieve. Example format: con_123456. This property is required for the "Get" and "Delete" operations on contacts. |
Output
The node outputs a JSON object representing the contact's data as returned by the Resend API. This typically includes fields such as:
id: The contact's unique ID.email: The contact's email address.first_name: The contact's first name (if available).last_name: The contact's last name (if available).unsubscribed: Boolean indicating if the contact has unsubscribed from emails.- Other metadata related to the contact within the Resend system.
The output is structured as an array of items, each containing a json field with the contact data corresponding to the input item.
The node does not output binary data.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node makes HTTP requests to
https://api.resend.com/contacts/{contactId}endpoint. - Ensure the API key has permissions to read contact data.
- No additional environment variables are needed beyond the configured API key credential.
Troubleshooting
Common issues:
- Invalid or missing Contact ID: The node requires a valid contact ID; ensure it is correctly provided.
- Authentication errors: Verify that the API key credential is set up properly and has sufficient permissions.
- Network or API downtime: Check connectivity and Resend API status if requests fail.
Error messages:
"404 Not Found": The specified contact ID does not exist. Confirm the ID is correct."401 Unauthorized"or"403 Forbidden": Authentication failed or insufficient permissions. Recheck API key credentials.- Timeout or network errors: Retry or check network settings.
To continue processing other items even if one fails, enable the "Continue On Fail" option in the node settings.
Links and References
- Resend API Documentation — Official API docs for managing contacts and other resources.
- n8n HTTP Request Node — For understanding how HTTP requests are made internally.
- n8n Error Handling — Guide on handling errors and using "Continue On Fail".