Create Pipedrive people from new Callback24 calls.
Create new person records in Pipedrive whenever a new call is completed in Callback24.
See all Callback24 + Pipedrive integrations or talk to a human
4.9/5 on G2·
Google for Startups Accelerator
How Knit builds this workflow
The Agent researches both APIs and wires the trigger on one side to the action on the other — no pre-built connector required. Here is the vocabulary it has to work with.
Callback24 Explore Callback24 →
TriggersFires when a new inbound call is tracked in Callback24.
Fires when a tracked call in Callback24 goes unanswered.
Fires when a caller leaves a voicemail in Callback24.
Creates or updates a caller's contact record in Callback24.
Adds a tag or disposition to a call record in Callback24.
Sends a text message via Callback24.
Pipedrive Explore Pipedrive →
TriggersFires when a new lead or contact is created in Pipedrive.
Fires when a deal moves to a new stage in Pipedrive.
Fires when a deal is marked won in Pipedrive.
Fires when a field on a contact changes in Pipedrive.
Creates or updates a contact in Pipedrive.
Creates a new deal in Pipedrive.
Moves a deal to a new stage in Pipedrive.
Logs a call, email, or note against a record in Pipedrive.
Common questions
Can Knit build “Create Pipedrive people from new Callback24 calls.” between Callback24 and Pipedrive?
Yes — describe it in the box above and Knit's Integrations Agent researches Callback24 and Pipedrive's public API docs (or your own uploaded docs) and builds a working workflow, whether or not either app already has a pre-built connector.
How long does it take to build?
Minutes to a first working version, not weeks — you test it against real data before it goes anywhere near production.