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