Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
The node is designed to add or update a contact in a mailing or SMS list system. It allows users to subscribe a contact by providing either an email address or an SMS number. If a contact with the same email or SMS number already exists, the node updates that contact instead of creating a duplicate. This functionality is useful for managing subscriber lists where contacts may need to be updated with new information without losing their subscription status.
Common scenarios include:
- Adding new subscribers to a marketing campaign via email or SMS.
- Updating existing subscriber details when they change their contact information.
- Tagging subscribers and associating them with specific opt-in processes for targeted communication.
Practical example:
- A marketing team wants to add a new subscriber who signed up through a web form. They provide the subscriber's email, select the appropriate opt-in process, assign tags, and optionally set custom data fields like first name or preferences. If the subscriber already exists, their information is updated accordingly.
Properties
| Name | Meaning |
|---|---|
| If a contact with the same email address or SMS number already exists, it will be updated. | Notice informing that existing contacts identified by email or SMS number will be updated rather than duplicated. |
| Email Address | The email address of the contact to add or update. |
| SMS Number | The SMS phone number of the contact to add or update. |
| Opt-in Process | Select the opt-in process (list) to which the contact should be subscribed. Options are dynamically loaded from available opt-in processes. |
| Tag | Assign a tag to the contact for categorization or segmentation purposes. Options are dynamically loaded from available tags. |
| Data Fields | Optional additional data fields to set on the contact. Multiple fields can be added, each consisting of: - Field Name: Select from dynamically loaded fields. - Field Value: Enter the value for the selected field. |
Output
The node outputs JSON data representing the result of the add or update operation for each processed contact. This typically includes confirmation of the contact's subscription status, any assigned tags, and updated data fields. The exact structure depends on the underlying API response but generally contains identifiers and status information about the contact.
If binary data output is supported, it would represent related files or attachments associated with the contact, but this is not indicated in the provided code or properties.
Dependencies
- Requires connection to an external service managing contacts and subscriptions (e.g., a marketing automation platform).
- Needs an API key or authentication token configured in n8n credentials to authorize requests.
- Dynamically loads options for opt-in processes, tags, and data fields from the external service via methods defined elsewhere in the bundled source.
Troubleshooting
Issue: Contact not added or updated.
- Cause: Missing or invalid email/SMS number, or incorrect opt-in process selection.
- Resolution: Ensure at least one contact identifier (email or SMS) is provided and valid. Verify the opt-in process ID is correct.
Issue: No options loaded for opt-in processes, tags, or data fields.
- Cause: Authentication failure or connectivity issues with the external service.
- Resolution: Check API credentials and network connectivity. Confirm the external service is operational.
Error Messages: May include authorization errors, validation errors for missing required fields, or API rate limits.
- Review error details returned by the node execution and adjust input parameters or credentials accordingly.
Links and References
- n8n Expressions Documentation — For using expressions in property values.
- Relevant external service API documentation (not provided here) for detailed understanding of contact management endpoints.