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