Actions5
- Contact Tags Actions
Overview
This node manages tags for contacts in the FullFunnel (GoHighLevel) platform. It allows users to add, remove, or replace tags on individual contacts, as well as perform bulk tag additions or removals across multiple contacts. This functionality is useful for segmenting contacts, organizing marketing campaigns, or managing customer statuses dynamically.
Practical examples:
- Adding a "VIP" tag to a specific contact after a purchase.
- Removing outdated tags like "lead" when a contact becomes a customer.
- Replacing all tags of a contact to update their status comprehensively.
- Bulk adding a "newsletter" tag to a list of contacts who subscribed recently.
Properties
| Name | Meaning |
|---|---|
| Contact ID | The unique identifier of the contact to modify tags for. |
| Tags | Comma-separated list of tags to add, remove, or replace on the contact (e.g., "vip, lead"). |
| Options | Collection of optional settings: |
| Case Sensitive | Whether tag matching should consider case differences (true/false). |
| Create Missing Tags | Whether to create tags that do not already exist in the system (true/false). |
| Normalize Tags | Whether to normalize tags by trimming spaces and converting to lowercase (true/false). |
Output
The node outputs JSON objects containing the results of the tag operations:
For Add Tags:
{ "success": true, "contactId": "<contact-id>", "tagsAdded": ["tag1", "tag2"], ...additional API response data }For Remove Tags:
{ "success": true, "contactId": "<contact-id>", "tagsRemoved": ["tag1", "tag2"], ...additional API response data }For Replace Tags:
{ "success": true, "contactId": "<contact-id>", "previousTags": ["oldTag1", "oldTag2"], "newTags": ["newTag1", "newTag2"], ...additional API response data }For Bulk Add/Remove Tags:
{ "operation": "bulkAdd" | "bulkRemove", "totalContacts": <number>, "successful": <number>, "failed": <number>, "results": [ { "contactId": "<contact-id>", "success": true | false, "tagsAdded" | "tagsRemoved": ["tag1", "tag2"], // if success "error": "<error message>" // if failed }, ... ] }
No binary data output is produced by this node.
Dependencies
- Requires an API key credential for authenticating with the FullFunnel (GoHighLevel) REST API.
- The node uses the FullFunnel API base URL
https://rest.gohighlevel.com/v2. - The API requests require a location ID obtained from the credentials.
- n8n must be configured with the appropriate API authentication token for FullFunnel.
Troubleshooting
Common issues:
- Invalid or missing contact IDs can cause API errors.
- Incorrectly formatted tags (e.g., empty strings or improper commas) may result in unexpected behavior.
- Insufficient permissions or invalid API keys will cause authentication failures.
- Network connectivity problems can prevent successful API calls.
Error messages:
- Errors returned from the FullFunnel API are captured and included in the output under the
errorfield during bulk operations. - If the node encounters an error and "Continue On Fail" is disabled, it will throw an operation error halting execution.
- To resolve errors, verify the contact IDs, tags format, API credentials, and network access.
- Errors returned from the FullFunnel API are captured and included in the output under the