Manage large sets of Tags

This guide is aimed at integrators who want to manage large tag sets in KlickTipp without building complex router logic in every workflow.

KlickTipp integrations often need to:

• Create tags dynamically from segment names from a source system such as a CRM, payment tool, or form tool.
• Keep only the currently relevant prefixed tags.
• Add and remove tags on contacts based on the final desired state.

To make that easier, KlickTipp provides three reusable tag-management template types. Each template type is available for both Make and n8n.

Use these templates when your integration receives tag or segment information from a CRM, payment tool, form tool, or another external system and you want to:

• Reuse the same tag logic across multiple parent workflows.
• Keep tag naming consistent with prefixes such as Zoho | or Pipedrive | .
• Remove outdated prefixed tags automatically.
• Update contact tags by name instead of hardcoding tag IDs.

These templates are especially useful when segmentation changes often and an external system should remain the source of truth for the current tag state.

In many integrations, the three template types are used together:

1. Resolve and create the desired tag names.
2. Find which existing prefixed tags should be removed.
3. Update the contact by adding the desired tags and removing the outdated tags.

This gives you a predictable final tag state instead of accumulating stale source-system tags over time.

Use this template when your parent workflow receives tag names such as Qualified, Newsletter, or Webinar and you want KlickTipp-ready tag names, optionally under a prefix such as Zoho | .

This template:

• Accepts an array of tag names.
• Optionally prepends a namespace prefix.
• Loads the existing KlickTipp tag list.
• Reuses matching tags that already exist.
• Creates missing tags automatically.
• Returns a unified array of resolved tag names.

This is the "get or create tags" building block for dynamic segmentation.

• tagNames[]: array of base tag names
• prefix: optional string such as Zoho | or Pipedrive |

• tags[]: resolved final tag names, including the prefix if one is used

• Creating segment tags dynamically.
• Preparing tags for downstream contact-tagging steps.
• Enforcing consistent prefix-based naming across integrations.

• Make: Resolve and create KlickTipp tags from names with optional prefixes
• n8n: Resolve and create KlickTipp tags from names with optional prefixes

• Pass a test array such as ["Qualified", "Support"].
• Optionally pass a prefix such as Zoho | .
• Confirm the workflow returns tags[] with the expected final tag names.
• Confirm missing tags are created in KlickTipp and existing tags are reused.

Use this template when your integration already knows which prefixed tags should remain on the contact and you need to calculate which outdated prefixed tags should be removed.

This template:

• Accepts the managed prefix scope.
• Accepts the list of tag names that should remain assigned.
• Loads existing KlickTipp tags in the same prefix namespace.
• Compares the current prefixed tags with the desired prefixed tags.
• Returns the outdated tag names that should be removed.

This template calculates the cleanup list only. It does not remove tags by itself.

• prefix: the managed prefix scope, for example Zoho |
• setTags[]: the base tag names that should remain assigned

• tagNamesToRemove[]: prefixed tag names that should be unassigned

• Cleaning up old stage, product, status, or segment tags from a source system.
• Removing outdated list or segment tags inside one namespace.
• Calculating the removal list before calling the contact-tagging template.

• Make: Find KlickTipp tags to remove by prefix
• n8n: Find KlickTipp tags to remove by prefix

• Use a prefix such as Zoho | .
• Pass a keep list such as ["Webinar", "Newsletter"].
• Confirm that only outdated tags inside the same prefix scope are returned.
• Confirm that tags outside the managed namespace are not included.

Use this template when you already know which tags should be added and which tags should be removed for one contact.

This template:

• Accepts a contact email.
• Accepts one array of tag names to add.
• Accepts one array of tag names to remove.
• Loads the KlickTipp tag list.
• Resolves tag names to tag IDs.
• Tags and untags the contact accordingly.

This is the final execution step that applies the desired tag changes to the contact.

• email: the target contact email
• tagNamesToAdd[]: final tag names to add
• tagNamesToRemove[]: final tag names to remove

• Successful completion of the tag update flow

This template expects valid tag names. If your source system may produce tags that do not yet exist in KlickTipp, first call the "Resolve and Create Tags from Names" template and then pass its output into this template.

• Applying source-system-driven add/remove changes to one contact.
• Reusing one standard contact-tagging sub-flow across many parent automations.
• Keeping parent workflows simple by avoiding manual tag-ID resolution.

• Make: Update KlickTipp contact tags by tag names
• n8n: Update KlickTipp contact tags by tag names

• Use a real test contact that already exists in KlickTipp.
• Pass a small add list such as ["Zoho | Qualified"].
• Pass a small remove list such as ["Zoho | Old Stage"].
• Confirm the contact ends with the expected final tag state.

For many integrations, the most robust parent-workflow pattern is:

1. Receive the current segment values from the source system.
2. Normalize them into base tag names.
3. Call the resolve/create template to build the final namespaced tags.
4. Call the find-to-remove template to calculate outdated prefixed tags.
5. Call the contact-tagging template to add current tags and remove outdated ones.

This pattern helps you avoid:

• duplicated router logic
• hardcoded tag IDs
• stale prefixed tags
• inconsistent tag naming across workflows

Use a stable prefix for every managed tag namespace.

Examples:

• Zoho |
• Pipedrive |
• Salesforce |
• GoHighLevel |

This makes it much easier to:

• keep one source system's tags separate from another source system's tags
• remove outdated tags safely inside the correct scope
• understand where a tag came from during troubleshooting

The three logical templates are the same across both automation platforms, but the way you call them differs:

• In Make, they are typically used as sub-scenarios called from a parent scenario.
• In n8n, they are typically used as sub-workflows called from a parent workflow.

Use the platform version that matches your integration stack. The tag-management logic stays the same.

• Use prefixes for all integration-managed tags.
• Let the connected source system remain the source of truth for the desired segment state.
• Reuse the templates instead of rebuilding tag logic in every workflow.
• Resolve or create tags before trying to assign them to contacts.
• Calculate the removal list before untagging contacts.
• Test with both existing and newly created tags.
• Verify the final contact tag state in KlickTipp after each test run.

The tag-management templates give you a reusable building block set for dynamic segmentation in KlickTipp.

Use the resolve/create template to prepare the desired tag names, the find-to-remove template to identify outdated prefixed tags, and the contact-tagging template to apply the final add/remove changes to the contact.

Together, these templates make large integration-managed tag sets easier to manage, easier to maintain, and safer to scale across Make and n8n automations.