Pipedrive CRM
Connect Pipedrive from Settings → CRM, authorize Kasbly, then enable the sync you need. Kasbly creates its custom fields during the OAuth connect flow, so a newly connected company is ready to sync without manual setup.
Contact matching in two-way sync
Section titled “Contact matching in two-way sync”Kasbly matches a returning Pipedrive person by its Pipedrive ID first, then phone, then email. This keeps the same Kasbly customer when a phone number changes. New contacts still need a phone number because Kasbly conversations use a messaging address. An email-only person is imported only when its email matches an existing Kasbly customer; otherwise Sync History explains how to fix it.
Inbound webhooks
Section titled “Inbound webhooks”To receive changes immediately, create a webhook in Pipedrive → Tools and apps → Webhooks after connecting Pipedrive in Kasbly:
- Paste the Pipedrive Inbound Webhook URL from Settings → CRM as the subscription URL.
- Set the HTTP Auth username to
kasbly. - Select Generate webhook secret in Kasbly and paste the generated value as the HTTP Auth password. Copy it before leaving the page because it is shown only once.
Pipedrive uses HTTP Basic authentication for these deliveries; it does not send
an x-pipedrive-signature HMAC header for regular webhooks.
Fields used by Kasbly
Section titled “Fields used by Kasbly”Kasbly creates and owns these Pipedrive fields:
- Deals —
kasbly_conversation_id: text. It is the stable identifier Kasbly uses to create or update the same deal for a conversation. - People —
kasbly_lead_score: numeric. It stores Kasbly’s lead score when available. - People —
kasbly_tags: text. It stores Kasbly tags as a comma-separated value when available.
If Pipedrive does not let Kasbly create these fields, reconnect using a Pipedrive administrator account. An administrator can also create the fields manually with the exact names above, then reconnect Kasbly before enabling a full or deals sync.
Reconnecting an existing company
Section titled “Reconnecting an existing company”Reconnecting is safe. Kasbly resolves fields that already exist and does not create duplicates. If deal sync reports that the conversation ID field is missing, reconnect Pipedrive to retry setup before running a full sync again.