When reschedule appointment in Novocall, sync it to lemlist.
When an appointment is rescheduled in Novocall, update outreach campaign state in lemlist.
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.
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.
lemlist Explore lemlist →
TriggersFires when a new subscriber is added in lemlist.
Fires when a contact unsubscribes in lemlist.
Fires when a subscriber opens or clicks a campaign in lemlist.
Creates or updates a subscriber in lemlist.
Unsubscribes a contact in lemlist.
Adds a subscriber to a list or segment in lemlist.
Sends a one-off transactional email via lemlist.
Common questions
Can Knit build “When reschedule appointment in Novocall, sync it to lemlist.” between Novocall and lemlist?
Yes — describe it in the box above and Knit's Integrations Agent researches Novocall and lemlist'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.