Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
This node is designed to tag a contact in a contact management or marketing system by associating one or more tags with the contact's email address. It is useful for organizing contacts into categories, segments, or groups based on their attributes or behavior. For example, you might use this node to add a "VIP" tag to a customer's profile after a purchase or to mark contacts who have subscribed to a newsletter.
Properties
| Name | Meaning |
|---|---|
| Email Address | The email address of the contact to be tagged. This is required to identify the contact. |
| Tag IDs | One or more tag identifiers to assign to the contact. You can select from a list or specify IDs using expressions. |
Output
The node outputs JSON data representing the result of the tagging operation. Typically, this includes confirmation that the specified tags were successfully applied to the contact identified by the email address. If the node supports binary data output, it would relate to any files or attachments associated with the contact tagging process, but no such binary output is indicated here.
Dependencies
- Requires an API key or authentication token to connect to the external contact management service.
- Depends on an external service that manages contacts and tags (e.g., a marketing automation platform).
- The node uses a method to dynamically load available tags (
getTagsWithoutPlaceholder), which implies connectivity to the external service to fetch tag options.
Troubleshooting
Common issues:
- Invalid or missing email address: Ensure the email address is correctly provided and formatted.
- Tag IDs not found or invalid: Verify that the tag IDs exist in the external system and are accessible.
- Authentication errors: Confirm that the API key or credentials are valid and have sufficient permissions.
- Network or API downtime: Check connectivity and service status of the external platform.
Error messages:
- Errors related to missing required fields (e.g., email) indicate input validation failures.
- Authorization errors suggest problems with the API key or permission scope.
- Tag-related errors may occur if the tag ID does not exist or cannot be assigned.
Resolving these typically involves verifying inputs, checking credentials, and ensuring the external service is operational.
Links and References
- n8n Expressions Documentation
- Relevant external service API documentation (not provided in source code) for managing contacts and tags.