Resources · Zapier integration

Phone.com Zapier integrationAutomate Phone.com with Zapier.

The Phone.com Zapier integration has 8 triggers, 3 actions and 2 searches. All 8 triggers are instant: a call, a text, a recording or a voicemail reaches Zapier without waiting on any plan interval. Below, what each operation does, costs and breaks.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Phone.com Zapier integration does for you

Phone.com is a business phone service: numbers, extensions, calls, texts and voicemail in one account. The Zapier integration turns what happens on those lines into starting points for other tools, and lets other tools place a call, send a text or add a contact on Phone.com without anyone touching a handset.

Three results teams build first. A CRM that knows about every conversation: Call Completed or New Call Log Record writes the call into your customer record, so nobody retypes who called and when. Messages that never sit unread: New Inbound SMS and New Voicemail post into the channel where your team actually works. Click-to-call from a lead form: a new lead in another tool runs Make Call (Click to Call), which connects your rep's extension with the prospect's number.

Every Phone.com trigger is instant. On the free plan, a trigger Zapier has to check on a timer can wait up to 15 minutes; these do not wait at all, which matters when the event is a customer on the line.

What Zapier does not do with Phone.com: it cannot pick up calls placed before the Zap was on, it cannot edit or delete a contact (there is no action for that), and the searches only cover call data and contacts. Number and extension management stays in Phone.com.

If you are comparing platforms before you build, see Make vs Zapier and n8n vs Zapier.

Vocabulary

The Zapier terms this page uses

Eight words, defined once. After this they come back without explanation.

Zap
An automation you set up in Zapier: one trigger followed by one or more actions, run every time the trigger event occurs.
Trigger
The Phone.com event that starts a Zap: a call, a text, a recording, a voicemail. With the Zap on, Zapier waits for it.
Action
The step that does the work once the Zap is running: send a text, place a call, create a contact.
Task
The unit on your Zapier bill. Each action that completes successfully is one task; that count is your plan's allowance.
Instant trigger
A trigger the app reports itself when the event happens. A polling trigger, by contrast, is checked by Zapier on a timer.
Filter
A step that only lets the Zap continue when the incoming data meets your condition. Otherwise the run stops there.
Search step
A step that looks up something already in Phone.com, such as a contact, so the next steps can use what it found.
Multi-step Zap
A Zap beyond one trigger and one action. A filter, a search or a second action makes one, and it needs a paid plan.
Cost

What Phone.com automation costs in Zapier

Phone.com is not a premium app on Zapier, so it runs on the free plan. You pay in tasks, and tasks come from completed actions only.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Triggers8 instant, never billed
  • Search or filterMakes the Zap multi-step (paid)

A trigger never uses a task. A call that ends and starts a Zap is free until an action runs. Every action that succeeds counts once, a failed one does not, and a Zap with three actions uses three times what a one-action Zap uses. The free plan includes 100 tasks a month and unlimited Zaps, each capped at one trigger and one action. Add a filter, a search step or a second action and the Zap becomes multi-step, which is paid. The interval grid only concerns polling triggers; all 8 Phone.com triggers are instant.

Connect

Connect Phone.com to Zapier

  1. 01

    Add a new connection

    On the Apps page of your Zapier account, click + Add connection. In the dialog that appears, search for Phone.com and select it from the list of results.

  2. 02

    Sign in to Phone.com

    Click Add connection. Phone.com opens in a new tab: sign in with the account that owns the numbers and extensions your Zaps will use, not a user who only sees one line.

  3. 03

    Grant access

    Allow Zapier to use the account. The connection lands on your Apps page, and every Phone.com step in every Zap reuses it from then on. One connection per account.

First Zap

Your first Phone.com Zap

GoalSend a follow-up text after each completed call, but only for the calls that match your rule.

  1. 01

    Build: set the trigger

    Create a Zap, choose Phone.com and Call Completed as the event, then pick your Phone.com connection. It covers inbound and outbound calls alike.

  2. 02

    Test on real calls

    Run the test: Zapier brings back the three most recent completed calls on the account. No call yet? Make a short one first, so you map fields on real data.

  3. 03

    Add the filter

    Click the plus icon, pick Filter and set the field, the rule and the value, for example to keep only inbound calls. Use a text rule on text. This step makes the Zap multi-step, so paid.

  4. 04

    Add Send SMS

    Add Phone.com with Send SMS. Fill From with your business number, map To from the call, and write the Text. All three are required.

  5. 05

    Test and publish

    Test the action on your own phone first, then click Publish. Each text sent from now on costs one task, so keep an eye on volume.

Triggers

The 8 Phone.com triggers

8 events start a Zap when something happens in Phone.com, and 8 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Call Completed

Instant trigger

In Zapier“Triggers when an inbound or outbound call is terminated on your Phone.com account.”

Fires when a call on your account ends, whether your team answered it or dialed out. At that point the conversation is over, so it is the natural moment to log it or follow up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
send a thank-you text after a sales call, or add a line to the customer record once the call is done.
Watch out
it covers both directions; if only inbound calls matter, a filter is needed, and that makes the Zap multi-step.
2

New Call Log Record

Instant trigger

In Zapier“Triggers when a new log entry is created for a call. Note: Multiple log entries can be created for each call.”

Runs each time Phone.com writes a log entry for a call. It is the trigger for people who want the call history itself in another tool, entry by entry.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you keep a call history in a spreadsheet or a reporting tool and want every logged call there without exports.
Watch out
one call can produce several log entries, so the Zap may run more than once per call and spend a task each time.
3

New Call

Instant trigger

In Zapier“Triggers when a new inbound or outbound call is initiated on your Phone.com account.”

Starts the Zap the moment a call begins on your account, in either direction. Zapier highlights it on the Phone.com page, and it is the earliest signal you can get.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
alert a team channel when a key account calls, while the conversation is still going on.
Watch out
the call has not ended yet, so anything that depends on its outcome belongs on Call Completed instead.
4

Call Status Updated

Instant trigger

In Zapier“Triggers when an inbound or outbound call's status was updated.”

Reacts each time the status of a call changes, inbound or outbound. Where New Call and Call Completed mark the two ends, this one follows the steps in between.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a dashboard or a wallboard should show calls moving through their states as they happen.
Watch out
a single call can change status several times, so this trigger can run often; a filter on the state you care about helps, but makes the Zap multi-step.
5

New Call Recording

Instant trigger

In Zapier“Triggers when a new call recording is created on your Phone.com account.”

As soon as Phone.com creates a recording of a call on your account, this one starts the Zap. Zapier highlights it on the app page, and the recording becomes material for the next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
file each recording in a shared drive, or hand it to a transcription tool, so quality reviews do not start with a hunt.
Watch out
it only concerns calls that produce a recording; a call without one never starts this Zap.
6

New Inbound SMS

Instant trigger

In Zapier“Triggers when a new SMS was received.”

Triggers on every text message received on your Phone.com numbers. One of the triggers Zapier puts forward, and the simplest way to make sure texts are seen by the right person.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
a customer replies to an appointment reminder and the message should land in your helpdesk or team chat.
Watch out
a Zap that answers with Send SMS is fine, but never let the reply flow back into a Zap that replies again.
7

New Outbound SMS

Instant trigger

In Zapier“Triggers when a new SMS was sent.”

Fires on each text sent from your Phone.com account. Useful as a record of what your team told customers, wherever the text was typed.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
keep an archive of outgoing messages in your CRM, next to the contact they went to.
Watch out
texts sent by a Zap through Send SMS are outbound too; a Zap that sends a text from this trigger feeds itself and burns tasks.
8

New Voicemail

Instant trigger

In Zapier“Triggers when a new voicemail is created on your Phone.com account.”

A voicemail left on your Phone.com account starts this Zap. A missed call becomes an item someone can act on, instead of a blinking light.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
create a ticket or a task for each voicemail, so callbacks are tracked and no caller is forgotten.
Watch out
only voicemails left after you publish are sent; the ones already in the box stay there.
Actions

The 3 Phone.com actions

Phone.com gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Make Call (Click to Call)

Action

In Zapier“Creates a two-legged call and connect the two call legs to one another. Make Call lets you select your outbound caller ID on the call legs.”

Places a two-leg call: Phone.com rings one side, then connects it to the other. Leg A Phone Number and Extension are required; the Extension serves as the second leg when no other number is given.

When to use it
a new web lead triggers a call that puts your rep's extension and the prospect on the same line.
Watch out
you can choose the outbound caller ID, so pick the number the prospect will recognize.
2

Create Contact

Action

In Zapier“Creates contact in address book.”

Adds a contact to the Phone.com address book of the Extension you choose, which is the one required box.

When to use it
new customers signed up in another tool should show up by name when they call your team.
Watch out
there is no update or delete action, so a contact created with a typo has to be fixed in Phone.com.
3

Send SMS

Action

In Zapier“Sends an SMS via your Phone.com phone number.”

Sends a text from your Phone.com number. From, To and Text are required, and To accepts several numbers separated by commas.

When to use it
appointment reminders, delivery notices or a short message after a call, sent from the number customers already know.
Watch out
each text sent shows up on New Outbound SMS; keep the two in separate Zaps that do not feed each other.
Searches

The 2 Phone.com searches

2 search steps look for data that already exists in Phone.com, so a later step can use it.

A search step looks up something that already exists in Phone.com and passes it on. In the editor, the searches sit at the bottom of the Action event list, under SEARCH. Phone.com offers no find-or-create variant. Three settings decide what happens when the lookup does not go as planned.

1

Find Call Data

Search

In Zapier“Find a call log record from a Call UUID.”

Pulls a call log record from its call identifier, the unique ID a call carries. It brings back details a trigger step may not have.

When to use it
a Zap started by a recording or a status change needs the full record of the same call before writing it to your CRM.
Watch out
it needs the call's ID from an earlier step; it does not search by number or by date.
2

Find Contact

Search

In Zapier“Find a contact”

Looks up a contact in Phone.com within the Extension you set, a required box, so the following steps can use what it found.

When to use it
check whether a caller already exists before running Create Contact, so the address book does not fill with duplicates.
Watch out
whether the match must be exact is decided by Phone.com, so test it with a real contact first.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switched on, the Zap carries on with nothing found.
  2. Create X if it doesn't exist yet?
    Ticked, this box turns a search into a find-or-create. Phone.com does not expose such a variant on Zapier, so its searches only look things up.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or pass all of them on to the next steps.
When it breaks

When a Phone.com Zap misbehaves

Zapier attaches no help article to Phone.com. The failures below are the general ones, and with a phone system some of them hit harder.

Phone events come in fast and in series: a call creates a start, status changes, an end, logs. That rhythm is what turns small design mistakes into big task counts. The general method is on Zapier troubleshooting.

  • The SMS loop

    A Zap on New Outbound SMS that sends a text with Send SMS triggers itself again. Each turn costs a task until the Zap is switched off.

  • One call, many runs

    New Call Log Record can fire several times per call, and Call Status Updated once per state. Pick Call Completed when you want one run per call.

  • No history before publishing

    A Zap only sees calls, texts and voicemails that happen after it goes live. Past calls stay in Phone.com; moving them is a separate job.

  • The flood after a busy hour

    A sudden burst of events, for example after a campaign or a migration, can be held back by Zapier's flood protection.
Need help

Need help automating Phone.com with Zapier?

A person reads every message.

FAQ

Phone.com Zapier integration: frequent questions

01Is the Phone.com Zapier integration free?
Yes, on Zapier's free plan, as long as each Zap stays at two steps. Phone.com is not a premium app, and the free plan includes 100 tasks a month and unlimited Zaps. The constraint is the size of the Zap: one trigger, one action. A follow-up text after each call fits. Filtering out outbound calls, or looking up a contact first with Find Contact, adds a step and needs a paid plan. Your Phone.com subscription itself is a separate matter, outside Zapier.
02How many tasks does a Phone.com Zap use?
One per successful action; the trigger is free. A Zap that sends a text after each completed call uses one task per call. The trap with Phone.com is the trigger you choose: New Call Log Record can fire several times for one call, and Call Status Updated fires on each state change. On those, the same call can cost several tasks. When you want one run per conversation, Call Completed is the safer choice.
03Do Phone.com calls and texts reach Zapier instantly?
Yes. All 8 Phone.com triggers are instant: Phone.com tells Zapier itself when a call starts, ends, changes status, when a text or a voicemail arrives, and the Zap runs right away. The plan interval grid (15 minutes on Free, 2 on Professional, 1 on Team and Enterprise) only applies to polling triggers. So the free plan gets the same speed here as Enterprise. In the editor, these Zaps show a lightning bolt.
04What does it take to connect Phone.com to Zapier?
A Phone.com account with access to the numbers and extensions you want to automate. The gestures: Apps page in Zapier, + Add connection, search Phone.com, Add connection, sign in in the new tab, grant access. The part that blocks people comes later: Make Call, Create Contact and Find Contact require an Extension, and Send SMS requires a From number. If the connected user cannot see them, the dropdowns stay empty and the step cannot be set up.
05Why would a Phone.com Zap send texts in a loop?
Because a Zap that writes where its trigger watches starts itself again. With Phone.com the classic case is New Outbound SMS feeding Send SMS: every text the Zap sends is a new outbound text, which starts the Zap again. Each turn costs a task. Build texting Zaps on other triggers, such as Call Completed or New Inbound SMS, and switch off any Zap that shows runs piling up with no human behind them.
06What if the Phone.com operation you need is not there?
Then the Zapier app does not offer it and no setting will add it. The catalog is 8 triggers, 3 actions and 2 searches. There is no action to update or delete a contact, and nothing to manage numbers or extensions. Before concluding, check the neighbours: Find Call Data fills in details a trigger lacks, and Make Call can ring an extension when no second number is given. If nothing fits, the gap is real.
07Zapier, Make or n8n for Phone.com?
Choose on criteria, not on a ranking. On Zapier, Phone.com has 8 instant triggers, 3 actions and 2 searches, and works on the free plan. If one event leads to one action, that costs nothing. If you need filters, searches or several actions, you move to a paid plan billed per successful action, and chatty triggers like call logs weigh on that bill. Before choosing another tool, check that it offers the Phone.com events you rely on, then compare how each counts usage.
Same platform

Other docs you might need on this stack.

Browse all integrations