Resources · Make integration

PhoneBurner Make integrationAutomate PhoneBurner with Make.

Tired of retyping leads into your dialer by hand? The PhoneBurner Make integration gives you 7 modules to create, update, find and delete contacts. This guide is for sales teams new to Make: link your account, then build a first scenario that feeds PhoneBurner for you.

Try the PhoneBurner integration on MakeSee the 7 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PhoneBurner Make integration do for you?

The PhoneBurner Make integration keeps your calling list in step with the rest of your tools. A scenario, the automation you build in Make, takes data from another app and writes it into PhoneBurner as contacts, without code. It offers 5 actions and 2 searches, and no trigger of its own.

Every new lead lands in the dialer. When a web form or your CRM records a prospect, Create a Contact adds that person to PhoneBurner, so reps start calling from a list that is already filled in.

Numbers stay correct. A customer changes phone number in your billing tool: Update a Contact Phone fixes it in PhoneBurner, and Update a Contact handles the other details, so nobody dials a dead line.

Your data flows back out. List Contacts and Get a Contact read what PhoneBurner holds, to copy it into a spreadsheet or check a record before another step acts on it.

What the integration does not do: it has no trigger, so PhoneBurner cannot start a scenario on its own. The scenario runs on a schedule you set, or starts from another app. For any API endpoint the listed modules skip, Make an API Call uses the same connection. If you are still choosing a tool, the Make review and the n8n vs Make comparison lay out the criteria, and Make pricing explains how operations are counted.

Connect

How do you connect PhoneBurner to Make?

  1. 01

    Register an app in PhoneBurner

    In your PhoneBurner account settings, open the developer applications section and register a new application. Enter the requested details and paste https://www.integromat.com/oauth/cb/phoneburner2 as the callback URI, then submit. Copy the Client ID and the Client secret shown on screen.

  2. 02

    Add a PhoneBurner module

    In Make, add any PhoneBurner module to your scenario and click Create a connection. A connection is your PhoneBurner account linked to Make once, then reused by every PhoneBurner module. You can fill Connection name so you recognize it later.

  3. 03

    Enter your credentials

    Paste the Client ID and Client secret you copied, or follow the on-screen instructions, and approve the access. The connection now appears in the module, and Make can read your PhoneBurner contacts while you set up the fields.

First scenario

Your first scenario: push new leads into PhoneBurner

GoalWhen a new lead appears in another app, Make creates the matching contact in PhoneBurner.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + to add the first module. Since PhoneBurner has no trigger, this first spot goes to the app where your leads arrive, such as a form tool or a CRM.

  2. 02

    Pick the source of your leads

    Search that app by name, choose the module that watches for new records and click Create a connection. Once linked, Make lists the forms or lists it can read, so you just pick the right one.

  3. 03

    Add Create a Contact

    Click the + on the right of the first module, search PhoneBurner and pick Create a Contact. Map the lead data coming from the previous module into its fields.

  4. 04

    Test with Run once

    Click Run once and submit a test lead in the source app. Each module then shows the bundles it received, a bundle being one item passed along, here one lead. Check that the contact shows up in PhoneBurner.

  5. 05

    Schedule and switch on

    Open the clock on the first module to set the schedule. A new scenario checks every 15 minutes by default. Then switch the scenario on, and new leads start reaching your calling list without anyone copying them.

Modules

The PhoneBurner modules in Make

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

PhoneBurner1

Create a Contact

Action

In Make“Creates a contact.”

Adds a fresh person to PhoneBurner, so a lead captured anywhere else becomes someone your reps can call right away from their list.

When to use it
after a web form, a booking tool or your CRM records a new prospect and you want the dialer fed without copy and paste.
Watch out
each bundle that reaches it becomes a new record, so check first with List Contacts if the person might already exist.
PhoneBurner2

Delete a Contact

Action

In Make“Deletes a contact.”

Removes a contact from PhoneBurner, which keeps your reps from calling people who asked to be left alone or who are no longer relevant.

When to use it
a prospect unsubscribes or a deal is marked lost in your CRM, and the record should leave the calling list.
Watch out
treat every deletion as final and test on a dummy contact with Run once before switching the scenario on.
PhoneBurner3

Get a Contact

Action

In Make“Gets a contact.”

Reads one PhoneBurner contact, giving later modules its details to reuse, for example to check a number before a call.

When to use it
you already know which contact you want, for example from an earlier step, and need its current data before acting.
Watch out
it targets a single known contact; to find people without knowing which one, List Contacts is the better fit.
PhoneBurner4

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the PhoneBurner API through the connection you already set up, which covers what the six other modules leave out.

When to use it
you need a PhoneBurner feature that has no dedicated module here and you are comfortable reading the vendor's API documentation.
Watch out
you build the request yourself, so a wrong path or body only shows up when you click Run once.
PhoneBurner5

Update a Contact

Action

In Make“Updates a contact.”

Changes an existing PhoneBurner contact, so the details your reps see match what the rest of your stack knows about that person.

When to use it
a customer edits their profile in your CRM or support tool and PhoneBurner should reflect the change before the next call.
Watch out
the module needs to know which contact to change, so place Get a Contact or List Contacts before it when that is unclear.
PhoneBurner6

List Contacts

Search

In Make“Gets a list contacts.”

Pulls a set of contacts out of PhoneBurner, handy when you want to export your calling list or check who is already in it.

When to use it
before creating a contact, to avoid duplicates, or to copy PhoneBurner records into a sheet for reporting.
Watch out
as a search, it can return zero, one or many bundles, and every module after it runs once per bundle, which uses operations.
PhoneBurner7

Update a Contact Phone

Search

In Make“Updates a contact phone.”

Fixes the phone number of a PhoneBurner contact without touching the rest of the record, so the dialer always rings the right line.

When to use it
a customer reports a new number in a form or your billing tool and only that number needs to change.
Watch out
for changes to the rest of the record, reach for Update a Contact instead.
Need help

Need help automating PhoneBurner with Make?

A person reads every message.

FAQ

PhoneBurner and Make: common questions

01Is the PhoneBurner Make integration free?
Yes, on the Make side. PhoneBurner is a standard app, available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run and files up to 5 MB. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Each module run on one bundle is an operation, and your plan counts those. You still need your own PhoneBurner subscription, which is priced by the vendor, not by Make.
02What do you need to connect PhoneBurner to Make?
An active PhoneBurner account, because Make signs in through OAuth. In your PhoneBurner account settings, register a new application in the developer applications section, enter the Make callback URI shown in the documentation, and copy the Client ID and Client secret it gives you. Then add a PhoneBurner module in Make, click Create a connection, name it if you like and enter those credentials. Every PhoneBurner module of every scenario can reuse that same connection afterwards.
03Does the PhoneBurner Make integration have a trigger?
No. PhoneBurner has no trigger module in Make, so it cannot start a scenario by itself. You have two ways around that. Put the trigger of another app first, such as a form or CRM that detects new leads, then add the PhoneBurner module. Or start the scenario on a schedule: open the clock on the first module and choose how often it runs, every 15 minutes by default, with 15 minutes as the minimum on the Free plan and 1 minute on paid plans.
04What if a PhoneBurner module is missing in Make?
Use Make an API Call. This module lets you call any endpoint of the PhoneBurner API from your scenario, with the same connection as the other modules, so you are not limited to creating, reading, updating, listing and deleting contacts. You write the request yourself, based on the PhoneBurner API documentation, and test it with Run once before going live. For questions about the vendor documentation itself, the Make docs point you to PhoneBurner directly.
05Should you use Make or n8n for PhoneBurner?
It depends on what you need. On Make, PhoneBurner comes with 7 ready modules: 5 actions and 2 searches, plus the API call module for anything else, and no trigger. Many apps also have an n8n node, so check whether PhoneBurner is covered there and which operations it offers before you decide. Compare the two on the modules available for your case and on how you like to build, rather than on general claims. The n8n vs Make comparison on this site sets out those criteria.
Same platform

Other docs you might need on this stack.

Browse all integrations