When a new phone call or lead activity is recorded in CallRail, create or update the contact in Regal.
When a new phone call or lead activity is recorded in CallRail, create or update the contact in Regal.
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.
Regal Explore Regal →
TriggersFires when a new message is posted to a channel in Regal.
Fires when a new channel is created in Regal.
Fires when your team or a keyword is mentioned in Regal.
Fires when a new file is shared in Regal.
Posts a message to a channel in Regal.
Sends a direct message to a specific person in Regal.
Reacts to a message in Regal.
Adds a user to a channel in Regal.
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 “When a new phone call or lead activity is recorded in CallRail, create or update the contact in Regal.” between Regal and CallRail?
Yes — describe it in the box above and Knit's Integrations Agent researches Regal 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.