PhoneTrack Zapier integrationAutomate PhoneTrack with Zapier.
The PhoneTrack Zapier integration has 1 trigger and no action, and that trigger is instant: the moment a tracked call ends, PhoneTrack tells Zapier. Here is what it does, what it costs, how to connect it and where a Zap built on it can go wrong.
Verified Trustpilot reviews · AI, automation & growth agency
What the PhoneTrack Zapier integration does
PhoneTrack is a call tracking platform used by sales, service and marketing teams. Its Zapier integration does one thing: each time a call it tracks comes to an end, it starts a Zap, so what happened on that call reaches your other tools without anyone copying it over.
Three results people build on Call Ended. A CRM that knows about every call: each finished call becomes an activity on the matching record in your sales tool. A team alert while it still matters: a message in your chat channel tells the right person a call just ended, so the follow-up starts while the caller still remembers it. A marketing log you can sort: each finished call lands as a row in a spreadsheet, where the marketing team can sort and count them.
The good news first: this trigger is instant. PhoneTrack calls Zapier itself when the call ends, so the Zap starts right away even on the free plan, and the polling interval of your plan does not apply. The limits next. PhoneTrack only starts Zaps: there is no action and no search, so nothing can be written back into PhoneTrack from Zapier. And calls that ended before you switch the Zap on are never picked up.
To see how Zapier compares with other tools, the Zapier review and n8n vs Zapier pages are close at hand.
Zapier words, in plain terms
Seven Zapier words come up across this page. Each gets one line here, then they are used without reminders.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap. With PhoneTrack, it is a tracked call that ends; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something. With PhoneTrack, it always runs in another app.
- Task
- What Zapier bills: one action your Zap completes successfully. Your plan's allowance counts those, never the trigger.
- Instant vs polling
- An instant trigger is reported by the app the moment it happens. A polling one is checked by Zapier on a timer that depends on the plan.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there every other time.
- Connection
- Your PhoneTrack account linked to Zapier once, then reused by every Zap that starts from PhoneTrack.
What a PhoneTrack Zap costs
Zapier bills tasks, one per action that works. The PhoneTrack trigger itself never costs a task, whatever the number of calls it reports.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on freeTwo steps: one trigger, one action
- Call EndedInstant on every plan, the grid does not apply
- Premium appNo, PhoneTrack works on the free plan
A Zap that logs each ended call in one other app costs one task per call. Add a chat alert as a second action and each call costs two. An action that fails is not counted. PhoneTrack is not a premium app, so it works on the free plan, which only builds two-step Zaps: one trigger, one action. A filter or a second action turns the Zap into a multi-step one, which needs a paid plan. The interval grid below does not apply here: Call Ended is instant on every plan.
Connect your PhoneTrack account to Zapier
- 01
Open your app connections
In Zapier, open the Apps page of your account and click + Add connection. You link PhoneTrack here once, and every Zap that starts from a PhoneTrack call reuses that link.
- 02
Pick PhoneTrack
Type PhoneTrack in the dialog's search box, select it, then click Add connection. You need an existing PhoneTrack account: Zapier does not open one for you.
- 03
Sign in and grant access
A tab opens on PhoneTrack. Sign in, then let Zapier into the account. If the tracked numbers belong to a colleague's account, make sure you have access to them before you build the Zap.
Your first PhoneTrack Zap
GoalEach tracked call that meets your condition is logged in your CRM as soon as it ends.
- 01
Create the Zap, choose the trigger
Start a new Zap, pick PhoneTrack as the app and Call Ended as the event, then select your PhoneTrack connection. The editor shows a lightning bolt: the Zap is instant.
- 02
Test with real calls
Run the test. Zapier brings back the three most recent calls of the connected account, so the next steps are mapped on a real call rather than on placeholders.
- 03
Add a filter if needed
Click the plus icon, choose Filter, then set the field, the rule and the value. Use text rules on text, number rules on numbers. This step makes the Zap multi-step and needs a paid plan.
- 04
Add the action in your other app
Choose the app that should receive the call and its action, then map what PhoneTrack brought back into its fields. Test it and check the result in that app.
- 05
Publish
When the test reads right, click Publish to switch the Zap on. From then on, every tracked call that ends starts it straight away.
The PhoneTrack trigger
1 event starts a Zap when something happens in PhoneTrack, and one of them is instant: the app calls Zapier straight away, whatever your plan.
Call Ended
Instant triggerIn Zapier“Triggers when a call has ended.”
Starts the Zap when a call tracked by PhoneTrack comes to an end, so whatever follows works on a finished call rather than one still in progress. It is the only PhoneTrack operation in Zapier.
When a PhoneTrack Zap breaks
Zapier attaches no help article and no specific limit to PhoneTrack. What can go wrong comes from how Zapier works in general, in four cases.
Read these before you rely on the Zap for reporting. If a run still fails, the Zapier troubleshooting page is the place to start.
Past calls never come through
A Zap only reacts to what happens after you switch it on. Calls that ended before stay in PhoneTrack; moving that history is a separate job.A sudden wave gets held back
If the trigger suddenly sends a huge batch, after a migration for example, Zapier's flood protection can hold it back instead of running everything.A filter that never passes
Filter rules are typed: a text rule only works on text, a number rule only on numbers. Pick the wrong one and no call ever goes past the filter.Two steps on the free plan
The free plan stops at one trigger and one action. A filter or a second action makes the Zap multi-step, and it then needs a paid plan to run.
Need help automating PhoneTrack with Zapier?
A person reads every message.
