Automate Workflows: KlickTipp Integration in n8n

Your benefits with KlickTipp and n8n

• Ideal for technically-minded users: Great freedom when designing automations.
• Complex processes possible: loops, conditions, JavaScript logic.
• Real-time processing: React immediately to user actions and external triggers.
• No need for your own server: n8n takes care of hosting and maintenance.

Step-by-Step Instructions

Prerequisites

• KlickTipp account with API access: Make sure you have a Premium subscription or higher so that you have access to the API.
• n8n access: Make sure you have either created an account in the n8n or set up your own self-hosted instance.

Connect KlickTipp with n8n

• Log in to your n8n account.
• Create a new workflow and add a KlickTipp node.
• Open the KlickTipp node and select → Create New Credential.
• Enter your username and password for KlickTipp.
• Test the connection to check if the API is successfully connected.

Create KlickTipp Triggers via Webhook

• Create a workflow
  • Open n8n and create a new workflow.
  • Add the KlickTipp node as the first step.
• Configure the KlickTipp node
  • Click in the node under Triggers on → On new KlickTipp Event.
  • Select your access data under → Credential to connect with.
  • Copy the test URL of the webhook to paste it into KlickTipp later.
• Set up webhook in KlickTipp
  • Log in to your KlickTipp account and create an outbound.
  • Select an activation tag, for example → SmartLink clicked.
  • Select the appropriate KlickTipp element and enter the webhook URL.
• Test the workflow
  • Save the workflow so that your settings are retained.
  • Start a test run. Click on → Listen for test event   in the webhook node in n8n and then on → Save & test connection  in the KlickTipp outbound.
  • Check whether the data has been correctly transmitted to the webhook and the automation in n8n starts as desired.

Create KlickTipp Action

• Create workflow
  • If you do not yet have an n8n scenario, create a new one and add a trigger. Click on → Add first step... . The first step could be, for example, adding a new entry in a Google spreadsheet.
• Add and configure a KlickTipp node
  • As a second step, add a new KlickTipp node in the editor.
  • Select → Add or Update Contact from the available actions.
  • Assign the data from your trigger (e.g. name, email address) to the appropriate fields in the KlickTipp node.
  • Optionally, you can add a tag to identify the source of the contact, for example → Google Form.
• Test the workflow
  • Save the workflow so that your settings are retained.
  • Start a test run. In the first node, click on → Listen for test and insert a new row in your Google Sheet, for example. You should then see the transferred data in the output of the node. Finally, open the KlickTipp node, click on → Test step and check whether the contact has been entered in KlickTipp.

KlickTipp Modules in n8n

Available Triggers

• On new KlickTipp Event: Monitors a webhook that is created in n8n and can be reached via an outbound in KlickTipp. This enables triggers for each update of the contact with regard to manual tags or smart tags.

The following events are available in KlickTipp:

• Campaign (Marketing Cockpit) started
• Campaign (Marketing Cockpit) ended
• E-mail (Marketing Cockpit) received
• E-mail (Marketing Cockpit) opened
• E-mail (Marketing Cockpit) clicked
• Email (marketing cockpit) viewed in browser
• Newsletter / follow-up e-mail received
• Newsletter / follow-up e-mail opened
• Newsletter / follow-up e-mail clicked
• Newsletter / follow-up e-mail viewed in browser
• SMS (Marketing Cockpit) received
• SMS (Marketing Cockpit) clicked
• Smart link
• Tagging pixel triggered
• Conversion pixel triggered
• Outbound triggered
• Kajabi membership activated
• Kajabi membership deactivated
• Referral program
• Registered via registration form
• Registered via Facebook button
• Registered via SMS registration
• Registered via API key
• Entered via Business Card Reader Pro (obsolete)
• Entered via KlickTipp Business Card Reader Event
• Entered via entry by e-mail
• DigiStore24 Affiliate
• Entered via landing page

Available actions

Contact

• Add or Update Contact: Creates a new contact. If a contact with the same e-mail already exists, it will be updated.
• Update Contact: Updates a contact.
• Delete Contact: Deletes a contact.
• Unsubscribe Contact: Unsubscribes a contact and prevents further communication.
• Get Contact: Returns the complete data of a contact.
• Get Contact ID: Returns the contact ID for the requested e-mail address.
• List Contacts: Lists the IDs of all active contacts.
• List Tagged Contacts: Lists the IDs and tagging times of all tagged contacts.

Contact Tagging

• Tag Contact: Links a contact with one or more tags.
• Untag Contact: Removes a tag from a contact.

Tags

• Create Tag: Creates a new manual tag.
• Update Tag: Updates a tag.
• Delete Tag: De letes a tag.
• Get Tag: Returns the name and description of a tag.
• List Tags: Lists the IDs and names of all tags.

Opt-In Process

• Get Opt-in Process: Returns the complete data of an opt-in process.
• List Opt-in Processes: Lists the IDs and names of all opt-in processes.
• Get Redirect URL: Returns the redirect URL for a specific opt-in process.

Data Fields

• Get Data Field: Returns the ID and name of a specific data field.
• List Data Fields: L ists the IDs and names of all data fields.

Troubleshooting

Common problems and solutions

• Invalid API access data
  • Make sure that the username and password have been entered correctly and that the user has the necessary authorizations.
• Module setting incomplete
  • Check whether all required fields have been filled in.
• Invalid input values
  • Make sure that the data is transmitted in the correct format and matches the format of the field in KlickTipp so that it can be accepted there.
  • Note: You will also see the following message next to the field with the invalid value → Issues: The value "Example123" is not supported.
• Error during address validation on entry
  • Check whether the email address passed in the API call has the correct format and is accessible.

Further Resources