Actions12
- Mail Actions
- Contact Actions
- Broadcast Actions
Overview
This node integrates with the Resend API to update contact information within a specified audience. It allows users to modify details such as the contact's first name, last name, and subscription status by identifying the contact either by their ID or email address. This is particularly useful for marketing automation workflows where maintaining up-to-date contact records is essential for targeted communications.
Practical examples include:
- Updating a subscriber’s name after they submit a form.
- Changing a contact’s subscription status based on user preferences.
- Correcting contact information in bulk via automated workflows.
Properties
| Name | Meaning |
|---|---|
| Audience ID | The unique identifier of the audience (list) where the contact exists. |
| Identifier | The contact's unique ID or email address used to locate the contact to update. |
| First Name | The new first name to assign to the contact. |
| Last Name | The new last name to assign to the contact. |
| Subscribed | Boolean flag indicating whether the contact is subscribed (true) or unsubscribed (false). |
Output
The node outputs an array of JSON objects representing the updated contact(s). Each object typically contains the updated fields reflecting the changes made, such as the contact's ID, updated names, subscription status, and possibly metadata returned from the Resend API confirming the update.
If the node supports binary data output, it would generally relate to attachments or files associated with contacts, but this operation focuses solely on JSON data updates.
Dependencies
- Requires an active connection to the Resend API using an API key credential configured in n8n.
- The node depends on the Resend service being available and the provided Audience ID and contact identifiers being valid.
- Proper permissions on the API key to perform contact updates are necessary.
Troubleshooting
- Invalid Audience ID or Contact Identifier: If the node cannot find the specified audience or contact, it will likely throw an error. Verify that the Audience ID and contact identifier (ID or email) are correct.
- Authentication Errors: Ensure the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Connectivity problems can cause timeouts or failures; check network access to the Resend API endpoint.
- Field Validation Errors: Providing invalid data types (e.g., non-boolean for the subscribed field) may result in errors. Confirm input types match expected formats.
Links and References
- Resend API Documentation (for detailed API usage and contact management)
- n8n Documentation on Creating Custom Nodes