When new deal in Kylas CRM, sync it to Zadarma.
When a new deal is created in Kylas CRM, initiate a call or record call logs via Zadarma.
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.
Kylas Explore Kylas →
TriggersFires when a new contact or lead is added to Kylas.
Fires when a field on a contact changes in Kylas.
Fires when a deal, case or record moves to a new stage in Kylas.
Fires when a deal is marked won in Kylas.
Creates or updates a contact in Kylas.
Creates a new deal in Kylas.
Moves a deal or record to a new stage in Kylas.
Logs a call, email, or note against a record in Kylas.
Zadarma Explore Zadarma →
TriggersFires when a new inbound call is tracked in Zadarma.
Fires when a tracked call in Zadarma goes unanswered.
Fires when a caller leaves a voicemail in Zadarma.
Creates or updates a caller's contact record in Zadarma.
Adds a tag or disposition to a call record in Zadarma.
Sends a text message via Zadarma.
Common questions
Can Knit build “When new deal in Kylas CRM, sync it to Zadarma.” between Kylas and Zadarma?
Yes — describe it in the box above and Knit's Integrations Agent researches Kylas and Zadarma'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.