KlickTipp

KlickTipp is a German email marketing and marketing automation platform. Agents upsert and tag contacts, manage data fields and opt-in processes, start automations by tagging, and use the public sign-up routes of the Listbuilding API.

23 actions Session available

KlickTipp website Platform Documentation Capability data verified 2026-08-19

A prospect books a demo

Agent reads the booking, the contact, and the field values the sequence depends on

List Opt-in Processes resolves the process this flow should use rather than leaving the account default in play

Upsert Contact writes the person with that process named, so no unintended confirmation mail goes out

Tag Contact applies the tag that starts the pre-demo sequence

The enrollment posts to the sales channel with the tag named, so the rep knows what the prospect is about to receive

Before any tag is deleted in a cleanup pass, a person confirms which live automations depend on it

What This Integration Enables

In KlickTipp, tags are the language campaigns are written in. A tag is rarely a passive label: applying one is usually what starts something, and removing one can be what stops it. That changes what this integration is for. The interesting write is not updating a contact record, it is applying the tag that begins the sequence, at the moment the event that justifies it actually happened.

The second thing worth knowing is that this connector covers two of the vendor's APIs with different characters. The Management API acts on your own account and reads everything. The Listbuilding API is a deliberately narrow credential bound to one tag and one opt-in process, granting no read access at all, which is what makes it safe to call from a public sign-up route. FlowRunner agents upsert and tag contacts, manage tags and read data field definitions, resolve opt-in processes rather than inheriting whichever one the account defaults to, and use the public sign-up routes where a flow is standing in for a form. The operations that reach into live campaigns wait for a person, which is FlowRunner's human-in-the-loop default and the reason this connector is safe to point at a production account.

Without FlowRunner

Tags applied by hand Somebody remembers to tag the contact after the call, or the sequence never starts

Opt-in behavior left to defaults An import runs without naming a process, and everyone in the file gets a confirmation email

Tag list grows without pruning Nobody deletes an old tag because nobody can say what still depends on it

With FlowRunner

Tags applied by the event The booking, the payment, or the form submission applies the tag that starts the sequence

Opt-in behavior chosen per flow The process is named on every write, so the confirmation mail is a decision rather than a side effect

Pruning happens with evidence The cohort is sized, the dependencies are stated, and a person authorizes the removal

Use Case Scenarios

The booking that starts the sequence

An invitee books through Calendly. The agent resolves the person with Search Contact, calls Upsert Contact with the opt-in process named explicitly, and writes the field values the sequence uses, remembering that date fields on this platform take a timestamp rather than a formatted date and decimal fields take the value without a separator. Tag Contact then applies the tag that starts the pre-demo sequence. The enrollment posts to Slack naming the tag, so the rep taking the call knows exactly what the prospect has already been sent. When the meeting is cancelled, Untag Contact removes it, which is the whole intervention.
Payment state drives what people receive

A subscription succeeds or fails in Stripe. The agent applies the paying-customer tag and removes the trial tag, and a failed payment applies the dunning tag that starts the recovery sequence. Search Tagged Contacts reads back who currently carries each tag, with the two filters set explicitly rather than relying on defaults that exclude hard bounces and unsubscribed contacts, so a cohort that looks short is short for a reason the flow knows about. The result is that billing state and email state stop drifting apart between someone's monthly reconciliation.
A public sign-up route with a credential that cannot read anything

A landing page form built in Typeform posts to a flow that calls Sign In Contact using the Listbuilding key rather than the account session. That key is bound to a single tag and a single opt-in process and grants no read access, so the flow standing in for a public form holds no ability to enumerate the contact database. The response carries a redirect URL the platform generated but did not follow, and where it points depends on the key's configuration: a pending page when double opt-in applies, a thank-you page when it does not. The flow follows the URL it was given rather than always showing the same page, because half the audience has not confirmed anything yet.

Human-in-Loop Highlight

Delete Tag is the most consequential call on this connector and the least obviously so. It removes the tag from every contact carrying it, and in a platform where tags drive campaigns that has two effects at once, in opposite directions. Automations that start on the tag stop firing. And the mass untagging can itself set off automations that watch for a tag being removed, so a cleanup intended to quiet things down can start a sequence going out to thousands of people.

The agent cannot check this for itself. There is no operation on this connector that lists automations or reports what references a tag; that surface simply is not in the API. So the agent gathers what it can and hands the decision over. Search Tagged Contacts sizes the cohort, Get Tag returns the definition, and the flow posts: "Deleting tag Webinar-Mai-2025 removes it from 4,180 contacts. Any automation that starts on this tag stops, and any automation watching for its removal fires for all 4,180. I have no way to read which automations reference it. Confirm deletion, or archive by renaming instead?" A person who can open the automation editor answers. That single question is the difference between tidying up a tag list and mailing four thousand people by accident.

Agent processes routinely

Detects exception requiring judgment

Clear match Continues automatically

Ambiguous Routes to human via preferred channel

Human decides

Agent resumes with decision

Agent Capabilities

23 actions

Contacts

List Contacts Returns contact identifiers rather than contact records, filtered by subscription and bounce state. It is an index, so each record is read individually afterward.
Get Contact Reads one contact in full. Accepts either the numeric identifier or the alphanumeric key.
Search Contact Resolves an email address to a contact identifier. The lookup at the front of most flows.
Search Tagged Contacts Returns who carries a tag and since when. Its subscription and bounce filters default to a narrow view, so the flow sets them deliberately when it needs the full cohort.
Upsert Contact Creates or updates a contact. Leaving the opt-in process unset runs the account default, which emails the contact, so an import that omits it mails everyone in the file.
Update Contact Updates an existing contact. A new address goes in the dedicated field rather than replacing the identifier the record is found by.
Unsubscribe Contact Records an opt-out for the contact.
Delete Contact Removes the contact record from the account.

Tagging

Tag Contact Applies tags to a contact. In this platform that is usually what starts a campaign rather than what labels one, so flows treat it as a send. Takes a set of tags in one call.
Untag Contact Removes one tag from a contact. Takes a single tag rather than a set.

Data Fields

List Data Fields Returns the account's field definitions with the prefixed keys that writes have to use.
Get Data Field Reads one field's definition, including the type that dictates how its value has to be formatted.

Opt-in Processes

List Opt-in Processes Returns the account's opt-in processes. The entry with no name is the account default, which is the one that runs when a write does not name a process.
Get Opt-in Process Reads one process's configuration, so a flow knows whether writing a contact through it sends a confirmation email.
Get Opt-in Redirect URL Returns the page a contact should be sent to for a given process, on the account-session path.

Listbuilding

Sign In Contact Signs a contact up through the public, key-scoped route bound to one tag and one opt-in process. Returns a redirect URL the platform generated but did not follow, and where it points depends on whether double opt-in applies.
Sign Out Contact Removes the Listbuilding key's tag from the contact. The contact stays subscribed.
Sign Off Contact Unsubscribes the contact entirely. One letter apart from the operation above and a very different outcome, so flows name it deliberately.

Frequently Asked Questions

What can FlowRunner do with KlickTipp?

FlowRunner agents can run List Contacts, Get Contact, and Search Contact in KlickTipp, plus 20 more actions.

Does connecting KlickTipp to FlowRunner require OAuth?

No. KlickTipp connects to FlowRunner with session-based authentication, no OAuth flow required.

Can KlickTipp trigger a FlowRunner workflow automatically?

KlickTipp doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.

Start building with KlickTipp

Free plan, no card required. Connect in minutes.

Start Building Free Talk to us