This scenario takes an array of tag names and ensures that every one of them exists in your KlickTipp account. It automatically compares the provided names with your existing tags and creates any missing tags when needed — returning a clean, unified list of resolved tag names with no duplicates or manual work.
To support structured tagging conventions, the scenario also includes an optional Prefix setting. If a prefix is provided (for example "Zoho | "), it will be applied to every incoming tag name before the lookup and creation step. This makes it easy to keep tags namespaced by tool or source (e.g. Zoho | Webinar, Zoho | Newsletter) while still sending simple base names from your integrations.
Perfect for marketers, automation builders, and CRM managers who want to maintain consistent tagging structures across their automations. Whether you’re syncing data from e-commerce platforms, webinar tools, forms, or external APIs, this scenario guarantees that every tag referenced in your workflows exists in KlickTipp.
All resolved tag names — both existing and newly created — are then aggregated into a single array, which you can directly pass into downstream scenarios or modules for tagging logic, filtering, or further processing.
With this automated flow, your workflows stay clean, reliable, and fully synchronized with your KlickTipp tagging conventions — without ever needing to manually manage tag creation.
Similar templates for inspiration
Looking to get more out of your apps? With Make, you can visually integrate any app into any workflow to save time and resources - no coding required. Try any of these templates in just a few clicks.
Create custom workflows by choosing triggers, actions, and searches. A trigger is an event that launches the workflow, an action is the event.
Adds a new contact. If a contact with the same email already exists, it will be updated.
Combines multiple bundles into a single array. This is the opposite of an Iterator.
Calls another scenario from the scenario flow, and lets you pass scenario inputs and outputs between the two.
Creates a new manual tag
Define a custom run name so you can easily identify and search for records.
Deletes a contact
Deletes a tag and removes it from all contacts
Returns the complete data of a contact
Gets the ID and the name of a data field
Start by registering for Make. As a new Make user, you’ll automatically be assigned a free account. Once your account is set up, you can start creating your first scenarios. We recommend starting with our step-by-step video tutorial.
A scenario represents a workflow or a project of your own creation, and it is made up of a series of modules that automate apps and services. Creating a scenario allows you to transfer and transform data between apps and services via these modules to automate anything and improve the way you work.
Modules are the main building blocks of automation in Make. Modules represent actions that Make performs with an app, like creating, updating, or deleting data.
Mapping links the modules in your scenario. When you map an item, you connect the data retrieved by one module to another module to perform the desired action. For example, you can map email addresses and subject lines to create a spreadsheet using this data.
Traditional no-code iPaaS platforms are linear and non-intuitive. Make allows you to visually create, build, and automate without limits.