Actions12
- Mail Actions
- Contact Actions
- Broadcast Actions
Overview
This node integrates with the Resend API to create a new contact in a specified audience. It is useful for marketing automation, customer relationship management, and email campaign tools where you want to programmatically add contacts to mailing lists or audiences.
Typical use cases include:
- Adding new subscribers collected from web forms into an email marketing audience.
- Syncing user data from other systems into Resend's contact lists.
- Automating contact creation as part of onboarding workflows.
For example, when a user signs up on your website, this node can automatically create a contact in your Resend audience with their email and optional details like first name, last name, and subscription status.
Properties
| Name | Meaning |
|---|---|
| The email address of the contact to be created. | |
| Audience ID | The unique identifier of the audience (mailing list) where the contact will be added. |
| Additional Fields | Optional extra information about the contact: |
| - First Name | Contact's first name. |
| - Last Name | Contact's last name. |
| - Subscribed | Boolean indicating whether the contact is subscribed or not. |
Output
The node outputs JSON data representing the newly created contact object returned by the Resend API. This typically includes fields such as the contact's ID, email, audience ID, subscription status, and any additional metadata stored.
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the Resend API.
- The node expects the "Audience ID" to be valid and existing in the Resend system.
- Network access to the Resend API endpoint is necessary.
Troubleshooting
- Invalid Audience ID: If the provided audience ID does not exist or is malformed, the API will return an error. Verify the audience ID is correct.
- Email format errors: Ensure the email address is properly formatted; otherwise, the API may reject the request.
- Authentication failures: Check that the API key credential is correctly configured and has sufficient permissions.
- Subscription flag issues: The "Subscribed" field must be boolean; passing invalid types might cause unexpected behavior.
- Missing required fields: Email and Audience ID are mandatory; omitting them will result in errors.