Skip to main content

KlickTipp tag manager: convert tag names to IDs

Workflow preview

Workflow preview
100%
KlickTipp tag manager: convert tag names to IDs preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

Community Node Disclaimer This workflow uses KlickTipp community nodes , available for self hosted n8n instances only . Introduction This workflo...

Best for

  • CRM automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.merge, n8n-nodes-base.splitout, n8n-nodes-base.set, n8n-nodes-klicktipp.klicktipp, n8n-nodes-base.aggregate, n8n-nodes-base.stickynote, n8n-nodes-base.executeworkflowtrigger

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by KlickTipp.

Original n8n.io source

1.1 Workflow description

Title
KlickTipp tag manager: convert tag names to IDs
Workflow name
KlickTipp tag manager: convert tag names to IDs

Community Node Disclaimer

This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only.


Introduction

This workflow receives an array of tag names, checks which tags already exist in KlickTipp, creates the missing ones, and returns a unified array of tag IDs — so you can reuse the same "get or create tags" logic across multiple automations.

How it works

  • Accepts input tagNames[] (array of tag names).
  • Splits the array into individual items and maps each name into a value field for matching.
  • Loads your full KlickTipp tag list and matches by tag name.
  • Creates tags that don’t exist yet.
  • Combines existing + newly created tags and returns a single aggregated array of IDs.

Setup Instructions

  1. Credentials

    • Configure your KlickTipp credentials in the KlickTipp nodes.
  2. How to call this sub-workflow

    • From a parent workflow, use an Execute Sub-workflow node and pass:
{ "tagNames": ["Tag A", "Tag B", "Tag C"] }

Output

Returns aggregated tag IDs:

{ "tagIds": [123456789, 98765431, 999999999] }

Testing

  • Test with a mix of existing and new tag names.
  • Confirm new tags appear in KlickTipp and the output contains all expected IDs.
  • Use tagIds[] in your parent workflow (for example, when updating or tagging contacts).

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Find tags to create

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 2 - Find existing tags

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 3 - Combine existing & new tags

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 4 - Split tagNames into items

Type / Role
n8n-nodes-base.splitOut - splitOut
Config choices
Version 1

Block 5 - Map tagNames -> value

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 6 - Get tag list

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 7 - Create new tag

Type / Role
n8n-nodes-klicktipp.klicktipp - klicktipp
Config choices
Version 3

Block 8 - Aggregate tag IDs

Type / Role
n8n-nodes-base.aggregate - aggregate
Config choices
Version 1

Block 9 - Extract only tag IDs

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 10 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 11 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 12 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 13 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 14 - Sticky Note4

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 15 - Sticky Note5

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 16 - Input: Tag names

Type / Role
n8n-nodes-base.executeWorkflowTrigger - executeWorkflowTrigger
Config choices
Version 1.1

3. Summary Table

Workflow KlickTipp tag manager: convert tag names to IDs
Complexity advanced
Nodes 16
Categories CRM
Author KlickTipp
Published 18 Dec 2025

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/11923/11923.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does KlickTipp tag manager: convert tag names to IDs do?

Community Node Disclaimer This workflow uses KlickTipp community nodes , available for self hosted n8n instances only . Introduction This workflo...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your CRM use case.