Create contacts in Autopilot Journeys from new schedules in Novocall.
When new schedules are created in Novocall, create or update contacts in Autopilot Journeys.
See all Autopilot Journeys + Novocall 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.
Autopilot Journeys Explore Autopilot Journeys →
TriggersFires when a new lead or contact is captured in Autopilot Journeys.
Fires when a contact enters an automation in Autopilot Journeys.
Fires when a field on a contact changes in Autopilot Journeys.
Fires when a contact unsubscribes in Autopilot Journeys.
Creates or updates a contact in Autopilot Journeys.
Adds a contact to a workflow or campaign in Autopilot Journeys.
Sends an email or message to a contact via Autopilot Journeys.
Changes a contact's tags in Autopilot Journeys.
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 “Create contacts in Autopilot Journeys from new schedules in Novocall.” between Autopilot Journeys and Novocall?
Yes — describe it in the box above and Knit's Integrations Agent researches Autopilot Journeys 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.