When new call in CallTrackingMetrics, sync it to Act!.
When a new call is received in CallTrackingMetrics, log call history in Act!.
See all Act! + CallTrackingMetrics 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.
Act! Explore Act! →
TriggersFires when a new contact or lead is added to Act!.
Fires when a field on a contact changes in Act!.
Fires when a deal, case or record moves to a new stage in Act!.
Fires when a deal is marked won in Act!.
Creates or updates a contact in Act!.
Creates a new deal in Act!.
Moves a deal or record to a new stage in Act!.
Logs a call, email, or note against a record in Act!.
CallTrackingMetrics Explore CallTrackingMetrics →
TriggersFires when a new inbound call is tracked in CallTrackingMetrics.
Fires when a tracked call in CallTrackingMetrics goes unanswered.
Fires when a caller leaves a voicemail in CallTrackingMetrics.
Creates or updates a caller's contact record in CallTrackingMetrics.
Adds a tag or disposition to a call record in CallTrackingMetrics.
Sends a text message via CallTrackingMetrics.
Common questions
Can Knit build “When new call in CallTrackingMetrics, sync it to Act!.” between Act! and CallTrackingMetrics?
Yes — describe it in the box above and Knit's Integrations Agent researches Act! and CallTrackingMetrics'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.