Resources · Zapier integration

PhoneBurner Zapier integrationAutomate PhoneBurner with Zapier.

The PhoneBurner Zapier integration offers 2 triggers and 4 actions. Call data from your dial sessions and contact changes flow out, new and updated contacts flow in. Both triggers poll, so timing depends on your plan. Here is the cost, the setup and what breaks.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the PhoneBurner Zapier integration does for a calling team

PhoneBurner is a dialer built for outbound sales teams who spend their day on the phone. Linked to Zapier, the calls made in its dial sessions and the contact changes reps make can feed your other tools, and those tools can create, look up and update PhoneBurner contacts in return.

Three results justify the setup. A call log outside the dialer: Get All Dial Session Data hands over each call as its own item, so a sheet or a CRM can hold one line per call, for you and, if you are a team admin, for your reps too. Leads that arrive ready to dial: Create Contact drops a new contact into the PhoneBurner folder you choose, straight from a form or an ad platform. A CRM that hears about edits: Updated Contact in Folder notices contacts changed in one folder, so another tool can mirror the change.

Two actions work in pairs. Contact Search finds people by email or phone, and Get a Contact or Update Contact (Contact ID) then act on one precise record, since both need its PhoneBurner Contact ID.

What Zapier does not do here: nothing starts the instant something happens in PhoneBurner. Both triggers poll, which means a delay that depends on your plan. There is no step to start a dial session, delete a contact or move one between folders either. If you are comparing platforms, see Make vs Zapier or n8n vs Zapier.

Vocabulary

Zapier vocabulary, in plain words

Seven terms. Each one is explained here once, then used as is.

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, such as a contact edited in a PhoneBurner folder. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or fetches something for you in an 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 what it has not seen. Instant: the app warns Zapier itself. PhoneBurner's two triggers poll.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Connection
Your PhoneBurner account linked to Zapier once, then reused by every PhoneBurner step in all your Zaps.
Cost

What a PhoneBurner Zap costs in tasks

The trigger is free. Zapier checking PhoneBurner for new calls or edited contacts costs nothing, however often it looks. You pay one task for each action that succeeds, and a failed action is not counted.

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

Contact Search and Get a Contact sit among the actions on Zapier, so each successful run counts like any other action. PhoneBurner is not reserved for paid plans: the free plan gives 100 tasks a month and unlimited Zaps, but two steps each, one trigger and one action. A filter or a second action makes the Zap multi-step, which needs a paid plan. How often the triggers check depends on the plan, as the grid shows:

Connect

Connect your PhoneBurner account to Zapier

  1. 01

    Find PhoneBurner in Zapier

    Open Apps in your Zapier account, click + Add connection, type PhoneBurner in the search box of the dialog and select it. Check that it is PhoneBurner itself and not another dialer.

  2. 02

    Sign in on PhoneBurner

    Click Add connection. PhoneBurner opens in a new tab: sign in with the account whose calls and contacts the Zaps should reach. On a networked account, that should be the admin account.

  3. 03

    Grant access

    Allow Zapier into the account. The connection is then saved and reused by every PhoneBurner step, so a new Zap only asks you to pick it. Any later Zap reuses it without a new sign-in.

First Zap

Your first Zap: log every connected call in a sheet

GoalEach call made in a PhoneBurner dial session that reached someone becomes a row in a shared spreadsheet.

  1. 01

    Build: set the trigger

    Start a Zap, pick PhoneBurner as the starting app and Get All Dial Session Data as the event, then choose your connection. If you are a team admin, your reps' calls come in too.

  2. 02

    Test with real calls

    Run the test: Zapier brings back the three most recent calls of the connected account. Each call is its own item, so you map one call, not a whole session.

  3. 03

    Add a filter

    Click the plus icon and choose Filter. In Configure & test, set the field, the rule and the value that separate a real conversation from a no-answer. Use a text rule on text.

  4. 04

    Add the sheet action

    Add the spreadsheet app as the action, pick your sheet, and map the call details from the trigger into its columns. Test the step and check the new row.

  5. 05

    Publish

    Click Publish to switch the Zap on. With the filter it has three steps, so it needs a paid plan, where Zapier also checks PhoneBurner more often.

Triggers

PhoneBurner triggers: the 2 events Zapier watches

2 events start a Zap when something happens in PhoneBurner. Zapier checks for them at the interval your plan allows.

1

Get All Dial Session Data

Polling trigger

In Zapier“Use this trigger to fetch dial session call data from your PhoneBurner account. If you are a team admin, it can return call data for both you and your users. Each call is returned as a unique trigger item that can be used in later Zap steps. For larger teams, polling may become slow or time out. When possible, a webhook-based Zap is the more reliable option.”

Collects the calls placed in your PhoneBurner dial sessions and passes each one to the Zap as a separate item. As a team admin, you get your reps' calls along with your own, which turns one Zap into a team-wide call log.

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 sales manager who wants every dial from the floor in one sheet, to read call volume by rep without opening the dialer.
Watch out
on larger teams, PhoneBurner itself warns that this check can slow down or time out.
2

Updated Contact in Folder

Polling trigger

In Zapier“Triggers when a PB Contact is UPDATED in defined folder”

Spots PhoneBurner contacts that were edited inside the folder you choose. New contacts are not its job: it looks at changes to existing ones, and only in that folder.

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 rep corrects a phone number or adds a note in the folder you watch, and the matching record in your CRM is updated without anyone retyping it.
Watch out
if Update Contact (Contact ID) edits a contact that sits in the folder this trigger watches, the Zap restarts itself in a loop.
Actions

PhoneBurner actions: create, find and update contacts

PhoneBurner gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Contact

Action

In Zapier“Creates a new contact.”

Adds a brand-new contact to PhoneBurner, filed in the folder you name. Folder is required and must already exist in your account.

When to use it
every lead captured by a landing page form goes straight into the folder your reps dial.
Watch out
this step is built to create, not to update, so run Contact Search first when the person may already be in PhoneBurner.
3

Get a Contact

Action

In Zapier“Use this action to get a specific contact when you know the Contact ID”

Fetches one specific contact when you already hold its PhoneBurner Contact ID, which is required. Nothing is changed: the step only reads the record for later steps.

When to use it
a contact ID stored in your CRM points back to PhoneBurner, and the next step needs that person's current details.
Watch out
without the ID, this action has nothing to go on; it cannot look up a name.
4

Update Contact (Contact ID)

Action

In Zapier“This Action will update a specific contact within PhoneBurner based on the unique PhoneBurner contact/record ID. In order to use this Action, you must have the PhoneBurner contact ID. This will update the specific contact within your personal account or if you are the PhoneBurner admin it will update the contact if it is in your account or any one of your users accounts”

Edits a precise PhoneBurner contact, picked by its PhoneBurner Contact ID, which is required. An admin can update contacts in any of the team's accounts, not just their own.

When to use it
when a deal closes in the CRM, update the matching PhoneBurner contact so reps stop calling a customer who already signed.
Watch out
no ID, no update; place Contact Search before it when only an email or a phone number is known.
When it breaks

When a PhoneBurner Zap breaks

Zapier attaches no help article to PhoneBurner. Apart from the warning PhoneBurner gives on its call-data trigger, what breaks follows Zapier's general rules.

  • Big teams can make the call-data check stall

    PhoneBurner warns that on larger teams, Get All Dial Session Data can get slow or time out when Zapier checks it. Keep an eye on the first runs.

  • A contact Zap that feeds itself

    Updated Contact in Folder followed by Update Contact (Contact ID) on a contact of the watched folder: each update looks like a new edit, the Zap reruns and burns tasks.

  • Old calls are never picked up

    A Zap only sees what happens after you publish it. Past dial sessions and earlier contact edits stay where they are; moving that history is another job.

  • Bulk imports can be held back

    Import a huge list of contacts into a watched folder and the trigger may return a flood of items at once, which Zapier's flood protection can hold back.
Need help

Need help automating PhoneBurner with Zapier?

A person reads every message.

FAQ

PhoneBurner and Zapier: common questions

01Is the PhoneBurner Zapier integration free?
On the Zapier side, yes. PhoneBurner is not one of the apps kept for paid plans, so it works on the free plan: 100 tasks a month, unlimited Zaps, but each Zap limited to one trigger and one action. Adding a filter or a second action, such as Contact Search before Update Contact (Contact ID), makes it a multi-step Zap that needs a paid plan. You still need a PhoneBurner account of your own.
02How many tasks does a PhoneBurner Zap use?
One per action that succeeds, nothing else. The trigger never costs a task, and Zapier checking PhoneBurner for new calls is free however often it happens. Contact Search and Get a Contact are actions on Zapier, so each successful run counts as a task, just like Create Contact. A Zap that searches then updates spends two tasks per run. An action that fails is not counted. Watch the count when Contact Search runs on every call.
03Is PhoneBurner on Zapier real time?
No. Both PhoneBurner triggers are polling triggers: Zapier checks PhoneBurner at regular intervals, and the gap depends on the plan. That is 15 minutes on the free plan, 2 on Professional and 1 on Team and Enterprise. Paid plans can also change how often the check runs, and launch one by hand from the editor. The trigger type comes from the app and cannot be switched to instant. Plan your follow-ups with that delay in mind.
04What do you need to connect PhoneBurner to Zapier?
A PhoneBurner account and the right login. In Zapier, open Apps, click + Add connection, search for PhoneBurner, click Add connection, sign in on the tab that opens and grant access. On a networked account, sign in with the admin account, otherwise Create Contact may not list every folder. You also need read or write access on any contact you do not own and want the Zap to touch. The connection is then reused by every PhoneBurner step.
05Why can't Update Contact (Contact ID) find the contact?
Because it only works with the PhoneBurner Contact ID, which is required. An email or a phone number is not enough on its own. Place Contact Search first, which finds contacts by email or phone, then map the ID it returns into Update Contact. Get a Contact works the same way. If the person was deleted, check the Include Trashed option of Contact Search before concluding they are gone. Test the two steps together once before publishing.
06What if the PhoneBurner step you need is missing on Zapier?
Then this integration cannot do it today. On Zapier, PhoneBurner offers two triggers (dial session call data and contacts updated in a folder) and four contact actions: create, search, get and update. There is no step to start a dial session, delete a contact or move one between folders. The usual workaround is to do that part in PhoneBurner or in another app; adding steps is up to PhoneBurner. Check the PhoneBurner side for anything new.
07Zapier, Make or n8n for PhoneBurner?
Pick on criteria rather than reputation. On Zapier, PhoneBurner gives you two polling triggers and four contact actions, which covers logging calls and keeping contacts in sync. If timing matters, weigh the polling interval of each Zapier plan. If your team is large, PhoneBurner's own warning about the call-data check slowing down is worth testing first. Then check whether the other tool offers the PhoneBurner operations you would otherwise miss.
Same platform

Other docs you might need on this stack.

Browse all integrations