Sync contacts, consent, and segments between KlickTipp and Pipedrive
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
Community nodes
These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
n8n-nodes-klicktipp(Delete contact, Update contact changes in KlickTipp, Create contact with DOI, Tag contact in KlickTipp2, Tag contact in KlickTipp3, Add Pipedrive Person ID to KlickTipp contact, Get contact data for tagging, Create contact with SOI, Tag contact for first transactional mail, Get subscription status)n8n-nodes-klicktipp(Contact tagged in KlickTipp, Contact deletion request triggered)
Nodes used (7)
- Klicktipp
n8n-nodes-klicktipp.klicktipp - Klicktipp Trigger
n8n-nodes-klicktipp.klicktippTrigger - Pipedrive
n8n-nodes-base.pipedrive - Switch
n8n-nodes-base.switch - Pipedrive Trigger
n8n-nodes-base.pipedriveTrigger - Filter
n8n-nodes-base.filter - HTTP Request
n8n-nodes-base.httpRequest
What it does
!Pipedrive to KlickTipp Integration.png(fileId:4435) Community Node Disclaimer This workflow uses KlickTipp community nodes, available for self-hosted n8n instances only. --- Who’s it for Sales and marketing teams using Pipedrive (Persons) and KlickTipp who want a reliable two-way sync for: - Contact profiles (name, email, phone, birthday) - Consent/marketing status (subscribed / no consent / unsubscribed) - Segmentation (KlickTipp Tags ↔ Pipedrive Labels) This workflow is ideal if you want to avoid CSV imports, prevent manual updates, and ensure that changes in either platform are reflected in the other — including deletes and consent changes. --- How it works This workflow creates a complete two-way synchronization between KlickTipp and Pipedrive (Persons). Whenever a Person is created, updated, unsubscribed, segmented, or deleted in either system, the workflow mirrors these changes across both platforms — so your CRM and email marketing database always stay aligned. It is designed for near real-time syncing of contact data, consent state, and segmentation (Tags ↔ Labels), without manual work. KlickTipp → Pipedrive Triggered by KlickTipp webhooks / activation tag events via “Contact tagged in KlickTipp”: 1. Fetch contact details in KlickTipp (Get contact data for tagging) to access tags and custom fields. 2. Route by contact state (Check subscription): - Person does not exist (no stored Pipedrive ID in KlickTipp) and contact is not Unsubscribed → Create a person in Pipedrive. - Person exists and contact is not Unsubscribed → Update a person in Pipedrive. - Person exists → unsubscribe → Update a person and set marketingstatus = unsubscribed. 3. Write the Pipedrive Person ID back to KlickTipp (Add Pipedrive Person ID to KlickTipp contact) to permanently link both records. 4. Sync consent status: - KlickTipp status = Subscribed → Pipedrive marketingstatus = subscribed - Otherwise → marketingstatus = noconsent 5. Sync birthday safely (timezone-aware): - KlickTipp birthday is stored as Unix seconds and converted to YYYY-MM-DD using Europe/Berlin timezone to avoid CET/CEST shifts. 6. Segmentation: KlickTipp Tags → Pipedrive Labels: - Reads KlickTipp tags (Check relevant segment) and assigns Pipedrive label IDs via PATCH: - Tag 14054258 → Label 14 (Customer) - Tag 14054294 → Label 27 (ABC) --- Pipedrive → KlickTipp Triggered by the Pipedrive Person webhook via “Changes in Pipedrive”: 1. Fetch the current marketing status (Get marketing status) to decide which consent action to apply in KlickTipp. 2. Route by sync scenario (Check subscription1): - Single Opt-In If no linked KlickTipp ID exists yet and status is not unsubscribed → create contact in KlickTipp via SOI (Create contact with SOI). - Form submission → DOI If changesource = api → create contact in KlickTipp via DOI (Create contact with DOI). - Update only If linked KlickTipp ID exists and status is not unsubscribed → update the existing KlickTipp subscriber (Update contact changes in KlickTipp). - Unsubscribe and update If linked KlickTipp ID exists and status is unsubscribed → unsubscribe the contact (Unsubscribe contact) and then update core fields (Update contact changes in KlickTipp1). - Contact deletion If action is delete → delete the KlickTipp contact using the previous email (Delete contact) to remain safe even if the email changed before deletion. 3. UI-only filtering for SOI path - Filter non UI events and deletions ensures the SOI create path processes only UI-driven events (changesource = app) and ignores deletions. 4. Sync birthday safely (no day shifting) - Reads Pipedrive birthday as YYYY-MM-DD from a custom field and converts it to Unix seconds using "T00:00:00Z" to prevent timezone-related day shifts. 5. Segmentation: Pipedrive Labels → KlickTipp Tags - Reads labelids from Pipedrive (supports array or comma-separated string), normalizes them, then applies tags in KlickTipp (Check relevant segment2): - Label 14 (Customer) → Tag 14054258 - Label 27 (ABC) → Ta