FullFunnel Tags

Gerenciar tags de contatos na FullFunnel (GoHighLevel)

Actions5

Contact Tags → Bulk Remove Tags

AI-generated

Overview

This node manages contact tags within the FullFunnel (GoHighLevel) platform, specifically focusing on bulk removal of tags from multiple contacts. It allows users to specify a list of contact IDs and tags to be removed in one operation, streamlining tag management for large contact sets.

Common scenarios include:

  • Cleaning up outdated or irrelevant tags from many contacts at once.
  • Removing promotional or campaign-specific tags after a marketing event.
  • Bulk updating contact segmentation by removing certain tags efficiently.

For example, a user can input a comma-separated list of contact IDs and tags like "newsletter, promocao" to remove these tags from all specified contacts in a single execution.

Properties

Name Meaning
Contact IDs Comma-separated list of contact IDs from which tags will be removed (e.g., "id1, id2, id3")
Tags Comma-separated list of tags to remove from the specified contacts (e.g., "newsletter, promocao")
Options Collection of optional settings:
- Case Sensitive: Whether tag matching is case sensitive (true/false)
- Create Missing Tags: Whether to create tags that don't exist yet (true/false)
- Normalize Tags: Whether to normalize tags by trimming spaces and converting to lowercase (true/false)

Output

The output JSON contains an overview of the bulk removal operation with the following structure:

  • operation: The operation performed, here it will be "bulkRemove".
  • totalContacts: Total number of contact IDs processed.
  • successful: Number of contacts from which tags were successfully removed.
  • failed: Number of contacts where the operation failed.
  • results: An array of objects, each representing the result per contact:
    • contactId: The ID of the contact.
    • success: Boolean indicating if the removal succeeded for this contact.
    • tagsRemoved: List of tags that were removed (present if success is true).
    • error: Error message if the removal failed for this contact.

No binary data is output by this node.

Example output snippet:

{
  "operation": "bulkRemove",
  "totalContacts": 3,
  "successful": 2,
  "failed": 1,
  "results": [
    {
      "contactId": "id1",
      "success": true,
      "tagsRemoved": ["newsletter", "promocao"]
    },
    {
      "contactId": "id2",
      "success": true,
      "tagsRemoved": ["newsletter", "promocao"]
    },
    {
      "contactId": "id3",
      "success": false,
      "error": "Contact not found"
    }
  ]
}

Dependencies

  • Requires an API key credential for FullFunnel (GoHighLevel) to authenticate requests.
  • Uses FullFunnel REST API v2 endpoints to manage contact tags.
  • The node expects the API key to have permissions to modify contact tags.
  • No additional environment variables are required beyond the API credential.

Troubleshooting

  • Common Issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect contact IDs may lead to errors such as "Contact not found".
    • Network issues or API rate limits can cause request failures.
    • Improperly formatted tag or contact ID strings (e.g., extra spaces, empty values) might affect processing.

  • Error Messages:

    • "Contact not found": Verify that the contact IDs exist in FullFunnel.
    • Authentication errors: Check that the API key is valid and has necessary permissions.
    • "No additional details": Indicates the error response did not include further info; check network connectivity and API status.

  • Resolution Tips:

    • Ensure contact IDs and tags are correctly formatted and separated by commas.
    • Use the "Normalize Tags" option to automatically trim and lowercase tags to avoid mismatches.
    • Enable "Continue On Fail" in n8n to process all contacts even if some fail, allowing partial success.
    • Review API quota and limits if encountering rate limit errors.

Links and References

Discussion