Actions16
- Contact Actions
- Contact Tagging Actions
- Data Field Actions
- Opt-In Process Actions
- Tag Actions
Overview
The node provides functionality to manage contact tags within a system, specifically allowing the removal ("untagging") of a tag from a contact identified by their email address. This operation is useful in scenarios where contacts need to be dynamically categorized or filtered based on changing criteria, such as unsubscribing users from certain campaigns or updating segmentation lists.
For example, if a marketing automation workflow identifies that a contact no longer fits a particular segment, this node can remove the associated tag from that contact to keep the contact data accurate and up-to-date.
Properties
| Name | Meaning |
|---|---|
| Email Address | The email address of the contact from which the tag will be removed. This is a required string input. |
| Tag | The tag to remove from the contact. Users can select from a list of available tags or specify a tag ID using an expression. |
Output
The node outputs JSON data representing the result of the untagging operation. Typically, this includes confirmation that the tag was successfully removed from the specified contact. The exact structure depends on the underlying API response but generally contains status information and possibly the updated contact details.
No binary data output is indicated for this operation.
Dependencies
- Requires access to the external service managing contact tags (likely via an API).
- Needs an API authentication token or key configured in n8n credentials to authorize requests.
- The node uses a method to load available tags dynamically for selection.
Troubleshooting
Common issues:
- Providing an invalid or non-existent email address may cause the operation to fail.
- Specifying a tag that does not exist or is not associated with the contact could result in errors or no changes.
- Missing or incorrect API credentials will prevent successful communication with the external service.
Error messages:
- Errors related to authentication typically indicate missing or invalid API keys; verify credential setup.
- "Tag not found" or similar messages suggest the tag ID is incorrect or unavailable; check tag selection.
- Network or timeout errors imply connectivity issues; ensure the external service is reachable.
Links and References
- n8n Expressions Documentation — for guidance on specifying tag IDs dynamically.
- Relevant API documentation of the external contact/tag management service (not provided here).