Resources · Zapier integration

Phone.do Zapier integrationAutomate Phone.do with Zapier.

The Phone.do Zapier integration has 1 trigger and no action. It does one job: each new lead created in Phone.do can start a Zap that copies it into your CRM, a sheet or a team chat. It polls, so the delay depends on your plan. Cost, setup and pitfalls below.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Phone.do Zapier integration really covers

Phone.do is a call center platform that its makers describe as a way to connect calls with other tools and lift service and sales results. On Zapier, that connection comes down to a single event: a new lead created in Phone.do, which can then start a chain of actions in any other app Zapier supports.

One trigger still opens several useful paths. A lead list that fills itself: New Lead sends each fresh lead to a spreadsheet, so whoever follows up works from one place. A CRM record without retyping: the same trigger can create the matching contact in your CRM, with the details mapped once in the editor. A heads-up for the team: a message in your team chat each time a lead lands, so nobody has to refresh Phone.do to notice it.

Now the limits, because they are clear. Zapier offers no action and no search for Phone.do: nothing can be written into Phone.do from a Zap, and no step can look up an existing lead. Phone.do's own description talks about sending call summaries, but no such event is offered on Zapier today. Only New Lead is.

The trigger also polls rather than reporting instantly, so a lead reaches the next app after a delay set by your plan. If you are still choosing an automation platform, Make vs Zapier and n8n vs Zapier are worth a read.

Vocabulary

Zapier terms, explained once

Seven words you will meet below. One line each, no jargon.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the starting event happens.
Trigger
The event in an app that starts the Zap. For Phone.do, it is a new lead. 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 for you, here always in another app.
Task
The unit Zapier bills. Each action that completes successfully is one task, and your plan's allowance counts those.
Polling vs instant trigger
Polling: Zapier checks the app on a timer and keeps only what is new. Instant: the app warns Zapier itself. New Lead is a polling trigger.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it there otherwise.
Connection
Your Phone.do account linked to Zapier once, then picked from a list by every Zap that starts on Phone.do.
Cost

What a Phone.do Zap costs

New Lead itself is free. Zapier can check Phone.do for new leads as often as your plan allows without spending a single task. What you pay for is the work done after it: each action that succeeds in the other app costs one task, and an action that fails is not counted.

  • New Lead trigger0 tasks
  • Each successful action1 task
  • Free plan100 tasks a month, two-step Zaps
  • Filter or second actionMulti-step Zap, paid plan

Phone.do is not reserved for paid plans, so it works on the free plan: 100 tasks a month and unlimited Zaps, each limited to two steps, one trigger and one action. New Lead plus one action fits that exactly. Add a filter or a second action, such as a chat alert next to the sheet row, and the Zap turns multi-step, which needs a paid plan. How often New Lead is checked depends on the plan, as below:

Connect

Connect your Phone.do account to Zapier

  1. 01

    Open Apps and add a connection

    In Zapier, go to Apps and click + Add connection. In the dialog that opens, type Phone.do in the search box and pick it from the results, checking the name carefully.

  2. 02

    Sign in to Phone.do

    Click Add connection. A new tab opens on Phone.do: sign in with the account whose leads you want the Zap to see. An existing Phone.do account is required for this step.

  3. 03

    Grant Zapier access

    Allow Zapier into the account to finish. The connection is saved once, then offered in a list whenever a Zap starts on Phone.do, so you never sign in again for each Zap.

First Zap

Your first Zap: new Phone.do leads straight into a sheet

GoalEvery new Phone.do lead that meets your condition gets a row in a shared spreadsheet.

  1. 01

    Build: choose New Lead

    Start a new Zap, pick Phone.do as the starting app and New Lead as the event, then select your Phone.do connection from the list.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent leads of the connected account, so the next steps are mapped on a real lead and not on a made-up one.

  3. 03

    Add a filter if needed

    Click the plus icon, choose Filter, then in Configure & test set the field, the rule and the value. Pick a text rule for text and a number rule for numbers.

  4. 04

    Add the sheet action

    Add the spreadsheet app as the action, choose the sheet, and map the lead details from the trigger into the columns. Test this step once and look at the new row.

  5. 05

    Publish

    Click Publish to switch the Zap on. With the filter it has three steps and needs a paid plan; without it, the free plan is enough.

Triggers

The Phone.do trigger Zapier offers

1 event starts a Zap when something happens in Phone.do. Zapier checks for them at the interval your plan allows.

1

New Lead

Polling trigger

In Zapier“Triggers when a new lead is created.”

Picks up each lead newly created in Phone.do and hands it to the rest of the Zap. It is the only Phone.do event available on Zapier, so every Phone.do automation starts here.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
a call center manager who wants each new lead copied into the CRM the sales reps live in, without anyone exporting lists.
Watch out
leads created before the Zap goes live are never sent; only new ones count from that point on.
When it breaks

When a Phone.do Zap breaks

Zapier attaches no help article to Phone.do and no limit specific to it is documented. What can go wrong comes from Zapier's general rules.

  • No catching up on old leads

    The Zap only reacts to leads created after it is switched on. Leads already in Phone.do stay there; moving that backlog is a separate job.

  • Each lead counts once

    Zapier remembers which leads it has already seen on a polling trigger, so the same lead does not start the Zap twice. You do not need to guard against repeats yourself.

  • A bulk import can be held back

    If a big batch of leads appears at once, after an import or a migration, Zapier's flood protection can hold the trigger back instead of running all of them.
Need help

Need help automating Phone.do with Zapier?

A person reads every message.

FAQ

Phone.do and Zapier: questions people ask

01Is the Phone.do Zapier integration free?
Yes, on the Zapier side. Phone.do is not one of the apps Zapier keeps for paid plans, so it runs on the free plan. That plan gives 100 tasks a month and unlimited Zaps, each built from one trigger and one action. New Lead followed by one action in another app fits it exactly. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. You also need your own Phone.do account to connect.
02How many tasks does a Phone.do Zap use?
Only the actions that follow New Lead cost anything. The trigger never uses a task, and Zapier checking Phone.do for new leads is free however often it looks. Each action that succeeds in the other app costs one task, so a Zap with one action spends one task per lead, and a Zap with two actions spends two. An action that fails is not counted against your plan. A few apps and actions on Zapier take more than one task, so check the app you send leads to.
03Is Phone.do on Zapier real time?
No. New Lead is a polling trigger: Zapier checks Phone.do at regular intervals, and the interval depends on your plan. It is 15 minutes on the free plan, 2 on Professional, and 1 on Team and Enterprise. On paid plans you can also change how often the check runs, and launch one by hand from the editor. The trigger type comes from the app itself, so it cannot be switched to instant from Zapier.
04What do you need to connect Phone.do to Zapier?
An existing Phone.do account and a few clicks. In Zapier, open Apps, click + Add connection, search for Phone.do and pick it, then click Add connection. Sign in to Phone.do in the tab that opens and grant Zapier access. If some leads belong to colleagues, the account you connect needs read access on them. Once saved, the connection is offered in a list each time a Zap starts on Phone.do. You only go through this once.
05Why does a Phone.do Zap not send leads that already existed?
Because a Zap only reacts to what happens after it is switched on. Leads that already existed in Phone.do before publishing are never picked up, by design. The trigger test does bring back the three most recent leads, but only so you can map the fields on a real one. Moving older leads into your CRM is a separate job, done outside the Zap. Switch the Zap on before the leads you care about arrive.
06What if the Phone.do step you need is not on Zapier?
Then this integration cannot do it. On Zapier, Phone.do offers a single trigger, New Lead, and no action or search. You cannot create or update anything in Phone.do from a Zap, or look up an existing lead. Call summaries, mentioned in Phone.do's own description, are not offered as a Zapier event either. The workaround is to start from New Lead and do the rest in other apps; adding new steps is up to Phone.do.
07Zapier, Make or n8n for Phone.do?
Choose on criteria, not on reputation. On Zapier, Phone.do gives you exactly one polling trigger, New Lead, which is enough if the goal is to push new leads somewhere else. If you need to write into Phone.do or react to calls, check first whether the other tool offers those Phone.do operations. Also weigh the polling delay of each Zapier plan against how fast a lead should reach your team, and the two-step limit of the free plan.
Same platform

Other docs you might need on this stack.

Browse all integrations