When new schedule in Novocall, sync it to Toky.
When a new call schedule is created in Novocall, sync scheduling data to Toky.
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.
Toky Explore Toky →
TriggersFires when a new text message is received in Toky.
Fires when a new call comes in or out through Toky.
Fires when a call is missed in Toky.
Fires when a call recording finishes processing in Toky.
Sends a text message through Toky.
Starts an outbound call via Toky.
Creates or updates a contact in Toky.
Sends a recorded voice message via Toky.
Novocall Explore Novocall →
TriggersFires when a new inbound call is tracked in Novocall.
Fires when a tracked call in Novocall goes unanswered.
Fires when a caller leaves a voicemail in Novocall.
Creates or updates a caller's contact record in Novocall.
Adds a tag or disposition to a call record in Novocall.
Sends a text message via Novocall.
Common questions
Can Knit build “When new schedule in Novocall, sync it to Toky.” between Toky and Novocall?
Yes — describe it in the box above and Knit's Integrations Agent researches Toky and Novocall'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.