- Home
- Resources
- Integrations
- CallTrackingMetrics
CallTrackingMetrics Zapier integrationAutomate CallTrackingMetrics with Zapier.
The CallTrackingMetrics Zapier integration rests on a single event: a new call reaching your account. 1 trigger, 0 actions, 0 searches. Zapier can hear about your calls, but it cannot write anything back into CallTrackingMetrics.
Verified Trustpilot reviews · AI, automation & growth agency
What the CallTrackingMetrics Zapier integration actually gives you
It links your CallTrackingMetrics account to Zapier so a new call can kick off work in other apps. There is exactly one entry point, New Call, and it is instant: CallTrackingMetrics warns Zapier as soon as the call comes in. Everything else happens in the tools you connect after it.
Three things people usually build from that one trigger. A call log: every new call becomes a row in a spreadsheet, so marketing can read inbound volume without logging into the call platform. A team ping: the sales channel gets a short message per call, so nobody has to open the call platform to find out. A CRM touchpoint: the call is added to the contact record in the tool your reps already use. All three run on New Call and nothing else.
Now the honest part. Zapier offers no action and no search for CallTrackingMetrics. You cannot create a contact there, tag a call, update a tracking number or look something up from a Zap. The traffic goes one way, out of CallTrackingMetrics. If your plan needs to push data back in, Zapier is the wrong door for this app, and the CallTrackingMetrics Make integration is worth a look before you commit.
Still weighing the platforms themselves? Our Make vs Zapier page is the place to start.
Zapier vocabulary, in one minute
Seven words you will meet in the editor. Each one is explained once here, then used plainly.
- Zap
- Your automation on Zapier: a starting event, here a call, followed by one or more steps in other apps, every time.
- Trigger
- The event in an app that starts the Zap. Here it is a new call. Once the Zap is on, Zapier simply waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, in another app on this page.
- Task
- The unit Zapier bills. One action that completes successfully equals one task, and your plan counts those.
- Polling vs instant
- Polling means Zapier checks an app on a timer. Instant means the app calls Zapier itself. New Call is the instant kind.
- Filter
- A step that lets the Zap continue only when the incoming call matches a rule you set, and stops it otherwise.
- Connection
- Your CallTrackingMetrics account, linked to Zapier once, then reused by every Zap that needs it.
What a call costs you in Zapier tasks
Short version: the call itself is free, what you do with it is not.
- Trigger0 tasks
- Each successful action1 task
- Free plan100 tasks / month, 2-step Zaps
- Premium appNo
The trigger never costs a task, so a busy day of calls costs nothing until an action runs. Each action that succeeds counts once; a Zap that logs the call and also pings Slack spends two tasks per call. A failed action is not billed. The free plan gives 100 tasks a month and unlimited Zaps, but only two-step Zaps: one trigger, one action. Add a filter or a second action and you need a paid plan. CallTrackingMetrics is not a premium app, so it works on the free tier.
Connect CallTrackingMetrics to Zapier in 3 steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. A dialog opens with a search box; type CallTrackingMetrics and pick it from the results list.
- 02
Sign in to CallTrackingMetrics
Click Add connection. A new browser tab opens on CallTrackingMetrics. Log in with an account that can see the calls you want the Zap to pick up, including any you do not own yourself.
- 03
Grant access
Approve the access Zapier asks for. The connection then shows up on the Apps page, ready for every Zap you build with this app. You only do this once per account.
Your first Zap: log every new call and alert the team
GoalEach new call lands in a sheet, and only the calls that match your rule reach Slack.
- 01
Pick the trigger
Create a Zap, choose CallTrackingMetrics as the app that starts it, then New Call as the event. Select the connection you added earlier.
- 02
Test it on real calls
Run the test. Zapier brings back the three most recent calls of the connected account, so you map fields from a real call rather than a guess.
- 03
Add the filter
Click the plus icon, choose Filter, then set the field, the rule and the value. Pick a text rule for text and a number rule for numbers, or it never passes.
- 04
Add the two actions
Add the row in your sheet, then the Slack message, and drag the call fields into each one. Test each step once and read what came back before moving on.
- 05
Publish
Click Publish to switch the Zap on. With a filter and two actions this is a multi-step Zap, so it needs a paid plan; on the free plan keep the trigger and one action.
The CallTrackingMetrics trigger
1 event starts a Zap when something happens in CallTrackingMetrics, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Call
Instant triggerIn Zapier“Triggers when you receive a new call.”
Fires each time a call reaches your CallTrackingMetrics account and hands its details to the next steps of the Zap. It is the only way into Zapier for this app, so every scenario on this page starts here.
When the CallTrackingMetrics Zap breaks
Zapier ties no help article to this app, so there is no documented error list for it. What breaks is what breaks on any Zapier trigger.
Four cases come back again and again. None of them shows up as a red error at setup time, which is exactly why they are worth knowing before you publish. If one already bit you, the Zapier troubleshooting page walks through the fixes.
Old calls never show up
A Zap only reacts to calls received after it is switched on. Calls already sitting in your account stay there; moving that backlog is another job.The Zap runs in a loop
New Call alone cannot loop, since nothing writes into CallTrackingMetrics. A second Zap that watches your call sheet and writes back into it can, and burns tasks fast.A big batch gets held back
After a bulk import or a migration, a sudden flood of new items can trip Zapier's flood protection, which holds the trigger back instead of running the Zap for each item.The filter never lets anything through
A text rule on a number field, or the reverse, makes the condition fail every time. Match the rule type to the field you are checking.
Need help automating CallTrackingMetrics with Zapier?
A person reads every message.



