Actions25
Overview
This node interacts with the Resend API to update contact information within a specified audience. It allows updating a contact either by their unique Contact ID or by their email address. Users can modify fields such as the contact's first name, last name, and subscription status (whether unsubscribed from emails). This operation is useful for maintaining up-to-date contact records in email marketing or communication platforms, ensuring that personalized and accurate data is used for campaigns.
Practical examples:
- Updating a subscriber’s name after receiving updated information.
- Marking a contact as unsubscribed when they opt out of communications.
- Correcting an email address or other details linked to a contact record.
Properties
| Name | Meaning |
|---|---|
| Update By | Choose whether to update the contact by Contact ID or Email Address. |
| Contact ID | The unique identifier of the contact to update (required if "Update By" is set to Contact ID). |
| Contact Email | The email address of the contact to update (required if "Update By" is set to Email Address). |
| Audience ID | The unique identifier of the audience where the contact belongs (required). |
| Additional Fields | Optional fields to update on the contact: |
| - First Name | The contact's first name. |
| - Last Name | The contact's last name. |
| - Unsubscribed | Boolean flag indicating if the contact is unsubscribed from emails. |
Output
The node outputs a JSON object representing the updated contact as returned by the Resend API. This typically includes the contact's current details after the update, such as their ID, email, audience association, and any updated fields like first name, last name, and subscription status.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node makes HTTP requests to the Resend API endpoints.
- Proper configuration of the API key credential in n8n is necessary for successful execution.
Troubleshooting
Common issues:
- Providing an incorrect Contact ID or Email Address will result in failure to locate the contact.
- Missing required fields such as Audience ID or the identifier chosen in "Update By" will cause errors.
- Network or authentication errors if the API key is invalid or missing.
Error messages and resolutions:
- "Contact not found": Verify that the Contact ID or Email Address exists in the specified audience.
- "Unauthorized" or "Invalid API key": Check that the API key credential is correctly configured and has proper permissions.
- "Missing required parameters": Ensure all mandatory fields are filled according to the selected options.