Track the number of new CallRail phone calls over time in Cyfe.
When new calls are logged in CallRail, push call volume counts over time to a custom widget in Cyfe.
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.
Cyfe Explore Cyfe →
TriggersFires when a new report or dashboard is created in Cyfe.
Fires when a tracked metric in Cyfe crosses a set threshold.
Fires when a scheduled report finishes generating in Cyfe.
Creates or refreshes a dashboard in Cyfe.
Exports a report from Cyfe.
Sends an alert when a metric changes in Cyfe.
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 “Track the number of new CallRail phone calls over time in Cyfe.” between Cyfe and CallRail?
Yes — describe it in the box above and Knit's Integrations Agent researches Cyfe 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.