Resources · Make integration

Dialpad Make integrationAutomate Dialpad with Make.

Can your phone system update itself while your team is busy on calls? The Dialpad Make integration gives you 39 modules, one instant trigger on call events, and actions on contacts, users, rooms and numbers. This page shows how to connect your account and build a first scenario.

Try the Dialpad integration on MakeSee the 39 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Dialpad Make integration do for you?

The Dialpad Make integration links your Dialpad account to Make, a no-code tool where you build a scenario (the automation itself, a chain of modules). Each module is one brick: a trigger that starts the chain, an action that changes something, or a search that returns a list. Dialpad brings 39 of them.

React to calls as they happen. Watch Call Events is an instant trigger: Dialpad calls Make through a webhook when a call changes state. From there, Get a User or Get a Contact fetches the details you want to send to a spreadsheet, a CRM or a chat channel.

Onboard and offboard people from one place. When your HR tool adds someone, Create a User opens the Dialpad account and Assign a Number to a User gives them a line. When someone leaves, Delete a User closes the account. The admin console stays closed.

Keep the phone directory clean. Create a Contact, Update a Contact and List Contacts keep Dialpad in line with the list your sales team already maintains elsewhere. Add Blocked Numbers stops a nuisance caller for the whole company.

What the module list does not cover, Make an API Call can reach with the same connection. Keep in mind that Make labels its Dialpad documentation as AI-generated and possibly wrong in places, so test each module with real data before you trust it. If you hesitate between tools, the n8n vs Make comparison lays out the criteria, and the Make pricing page explains how operations are counted. Teams that prefer to learn step by step can start with the Make training.

Connect

How do you connect your Dialpad account to Make?

  1. 01

    Add a Dialpad module

    Log in to Make, open your scenario and add any Dialpad module. Click Create a connection. If the module carries the instant tag, like Watch Call Events, click Create a webhook first, then Create a connection.

  2. 02

    Name the connection

    The Connection name field is optional, but a clear name such as "Dialpad support team" helps later. A connection is your Dialpad account linked to Make once, then reused by every Dialpad module you add.

  3. 03

    Paste your credentials

    Enter the API key you copied from Dialpad, or follow the on-screen instructions to sign in. Your Dialpad account must be active, and the key has to come from an administrator. An OAuth token also works.

First scenario

Build your first Dialpad scenario

GoalWhen a call changes state in Dialpad, Make fetches the profile of the Dialpad user tied to that call.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the big + to add the first module. Search for Dialpad and pick Watch Call Events.

  2. 02

    Set up the webhook

    Because this trigger is instant, click Create a webhook, then Create a connection with your API key. Dialpad will now tell Make about each call event instead of waiting to be asked.

  3. 03

    Add Get a User

    Click the + to the right of the trigger and add Get a User. Map the user ID from the event bundle (a bundle is one item passed from a module to the next, here one call event).

  4. 04

    Test with Run once

    Click Run once, then place or receive a test call in Dialpad. Open the bubbles above each module to read the bundles they received and check that the user ID actually shows up in the event.

  5. 05

    Switch the scenario on

    Once the test looks right, add the module that uses the result (a sheet, a message, a CRM record) and switch the scenario on. From then on, every call event runs it and each module run counts as one operation.

Triggers

What starts a Dialpad scenario

1 module starts a scenario when something happens in Dialpad. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Dialpad as soon as it happens.

Dialpad1Watch Call Events

Watch Call Events

Instant trigger

In Make“Triggers when a call state changes.”

Starts your scenario every time a call changes state in Dialpad, so you can log it, alert someone or look up who was on the line. It is the only trigger of the app, and the entry point for anything call-related.

How it fires
instant. Dialpad calls Make through a webhook as soon as the change happens, which is why the module asks you to create a webhook before the connection.
When to use it
a support lead wants each missed or finished call to land in a shared sheet without anyone copying it by hand.
Watch out
a single call can move through several states, so expect several bundles per call and run a first test to see what arrives before you add costly steps.
Modules

Every Dialpad module, explained

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

Dialpad1

Add Blocked Numbers

Action

In Make“Blocks the specified numbers company-wide.”

Cuts off a nuisance caller for everyone at once, since Dialpad applies this block to the whole company rather than to one line or one user.

When to use it
an agent flags a spam number in a form, and Make blocks it without waiting for an admin.
Watch out
the block is company-wide, so a number that one sales rep still needs is blocked for that rep too.
Dialpad2

Assign a Number to a User

Action

In Make“Assigns a number to a user.”

Hands a Dialpad number to a teammate so they can take calls on it, with no trip to the admin console.

When to use it
right after Create a User in an onboarding scenario, so the new hire has a line from the start.
Watch out
run List Numbers beforehand to see which numbers your company owns, and pick one that nobody else relies on.
Dialpad3

Create a Contact

Action

In Make“Creates a new contact.”

Adds a person to your Dialpad contacts, so the next call with them starts from a known name instead of a string of digits.

When to use it
a lead submits a form in another app and sales will call them from Dialpad.
Watch out
this module creates, it does not look first. Sending the same person twice probably leaves you with two contacts, so check with List Contacts.
Dialpad4

Create a Room

Action

In Make“Creates a new room.”

Sets up a new room in Dialpad from your scenario, ready to receive desk phones and a place in an office.

When to use it
facilities opens a new meeting space in a planning tool, and Dialpad should get the matching room without a second entry.
Watch out
List Rooms tells you whether a room with that name already exists before you add another one.
Dialpad5

Create a User

Action

In Make“Creates a new user.”

Opens a Dialpad account for a new colleague straight from your scenario, which removes one step from every onboarding checklist.

When to use it
your HR tool marks a hire as confirmed and the phone account should follow automatically.
Watch out
the user has no number yet. Chain Assign a Number to a User right after, or the account cannot take calls on a line.
Dialpad6

Delete a Contact

Action

In Make“Deletes a contact by ID.”

Removes one contact from Dialpad using its ID, keeping your directory free of people you no longer work with.

When to use it
a customer asks to be forgotten, and the request form triggers the cleanup across your tools.
Watch out
a deletion cannot be undone from Make. Fetch the contact with Get a Contact first to be sure the ID points to the right person.
Dialpad7

Delete a Room

Action

In Make“Deletes a room by ID.”

Takes a room out of Dialpad by its ID once the space no longer exists, so nobody tries to reach a phone that has gone.

When to use it
your inventory sheet marks a meeting space as closed after an office move.
Watch out
check the desk phones still attached with List a Room's Desk Phones before you delete; this step is final.
Dialpad8

Delete a User

Action

In Make“Deletes a user by ID.”

Closes a Dialpad account by its ID, the last step of an offboarding that should not depend on someone remembering it.

When to use it
HR records a departure and every tool the person used gets cleaned up in the same scenario.
Watch out
nothing brings the account back from Make. Get a User on the same ID lets you confirm the name before the delete runs.
Dialpad9

Get a Call Center

Action

In Make“Gets a call center by ID.”

Returns the details of one Dialpad call center when you already hold its ID, so later modules can use its name and settings.

When to use it
your support report stores a call center ID and should show its readable name instead.
Watch out
without an ID, start with List Office Call Centers to find the one you want.
Dialpad10

Get a Company

Action

In Make“Retrieves the company information.”

Pulls the information Dialpad holds about your own company, handy when a scenario needs the account details as a reference.

When to use it
an audit document built in another app should open with the company data straight from Dialpad.
Watch out
it always returns the same single company, so place it once near the start rather than inside a loop.
Dialpad11

Get a Contact

Action

In Make“Gets a contact by ID.”

Fetches one Dialpad contact from its ID and hands you everything stored on that record for the next module.

When to use it
after a call event, you want the caller's full contact record copied into your CRM note.
Watch out
the ID has to come from somewhere, usually a call event or List Contacts, so check after Run once that the value you map is really there.
Dialpad12

Get a Department

Action

In Make“Gets a department by ID.”

Reads a single Dialpad department by its ID, which lets you turn a bare identifier into a name your team recognises.

When to use it
a dashboard in a spreadsheet groups calls by department and needs the label, not the number.
Watch out
department IDs come from List Office Departments, which needs an office first.
Dialpad13

Get a Device

Action

In Make“Gets a device by ID.”

Looks up one device by its ID, so you know which phone or app a user is really using before you act on it.

When to use it
an IT ticket names a device and the helpdesk wants its Dialpad details attached automatically.
Watch out
List a User's Devices is the easy way to collect the IDs this module expects.
Dialpad14

Get an Office

Action

In Make“Gets an office by ID.”

Returns one Dialpad office from its ID, giving later steps the office data they need to route, label or report.

When to use it
a company with several sites wants each call record tagged with the office it belongs to.
Watch out
if you only know the office name, List Offices returns them all and lets you pick the matching ID.
Dialpad15

Get a Number

Action

In Make“Returns information about a specified number.”

Tells you what Dialpad knows about one phone number you pass in, which is useful before assigning, blocking or reporting on it.

When to use it
a teammate asks for a line, and you want to check the number's current status before handing it over.
Watch out
this module works on one number at a time; List Numbers gives the whole set.
Dialpad16

Get a Plan

Action

In Make“Gets the plan for an office.”

Retrieves the Dialpad plan attached to an office, so a scenario can read which plan each site is on.

When to use it
finance keeps a sheet of sites and wants the plan column filled from Dialpad rather than typed.
Watch out
the plan belongs to an office, so feed it an office ID from List Offices or Get an Office.
Dialpad17

Get a Room

Action

In Make“Gets a room by ID.”

Brings back one room from its ID, the quickest route to its details when a previous module already gave you the identifier.

When to use it
before Update a Room, to compare what Dialpad holds with what your facilities sheet says.
Watch out
no ID in hand means List Rooms comes first, filtered by office if you have many.
Dialpad18

Get a User

Action

In Make“Gets a user by ID.”

Returns the full profile of one Dialpad user from its ID, the natural partner of Watch Call Events when you want to know who handled a call.

When to use it
each call event should post the agent's name to your support channel.
Watch out
check after a Run once that the event bundle really contains a user ID before you map it.
Dialpad19

Get Statistics Results

Action

In Make“Retrieves the status and results of a specified statistics request.”

Collects the status and the output of a statistics request you started earlier, so your reporting ends with actual figures.

When to use it
as the second half of a reporting scenario, right after Process Statistics.
Watch out
processing is asynchronous. If the status says the request is still running, the results are not there yet, so plan a later check.
Dialpad20

Initiate an Outbound Call

Action

In Make“Initiates an outbound call to ring all devices (or a single specified device).”

Makes Dialpad ring a user's devices to place an outbound call, either all of them or one device you choose.

When to use it
a hot lead books a callback in a form, and the rep's phone rings to start the call.
Watch out
leave the device empty and every device of the user rings at once, so name one device when the rep only wants a single phone to ring.
Dialpad21

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Reaches any endpoint of the Dialpad API from your scenario with the same connection, for the cases no listed module covers.

When to use it
you need a Dialpad feature the 39 modules leave out and you have its API reference open.
Watch out
you write the request yourself, so a wrong path or scope only shows up when you click Run once.
Dialpad22

Process Statistics

Action

In Make“Begins processing statistics asynchronously, returning a request ID to get the status and result of the result.”

Starts a statistics job in Dialpad and gives you back a request ID, the key you need to pick up the results later.

When to use it
a manager wants call stats pushed into a spreadsheet without logging in to export them.
Watch out
this module only launches the job. Pair it with Get Statistics Results, which reads the output once it is ready.
Dialpad23

Remove Blocked Numbers

Action

In Make“Unblocks the specified numbers company-wide.”

Lifts a company-wide block so the numbers can reach your team again, the undo button of Add Blocked Numbers.

When to use it
a caller blocked by mistake turns out to be a customer, and support asks to restore the number.
Watch out
List Blocked Numbers shows what is currently blocked through the API, so you can confirm before unblocking.
Dialpad24

Update a Contact

Action

In Make“Updates the provided fields for an existing contact.”

Changes only the fields you fill in on an existing Dialpad contact and leaves the rest of the record as it was.

When to use it
a customer changes company in your CRM, and Dialpad should show the new details too.
Watch out
you need the contact's ID; List Contacts or Get a Contact provide it.
Dialpad25

Update a Room

Action

In Make“Updates room details by ID.”

Edits the details of a room by its ID, so a renamed or reorganised space shows the right information in Dialpad.

When to use it
your facilities sheet renames a meeting space and the change should spread to the phone system.
Watch out
map only the values you want to change, and double-check the room ID with Get a Room.
Dialpad26

Update a User

Action

In Make“Updates the provided fields for an existing user.”

Edits an existing Dialpad user and touches only the fields you provide, which keeps job changes in sync without retyping a profile.

When to use it
someone moves team in your HR tool and their Dialpad profile should follow.
Watch out
map only the fields that changed, and test with Run once on a colleague who agreed to it before you run it on everyone.
Dialpad27

List a Room's Desk Phones

Search

In Make“Returns a list of desk phones for a specified room.”

Returns the desk phones attached to one room, one bundle per phone, so you can see what hardware sits in that space.

When to use it
before closing a meeting space, IT wants the list of phones to collect.
Watch out
a search can return zero, one or many bundles; every following module then runs once per phone.
Dialpad28

List a User's Desk Phones

Search

In Make“Returns a list of desk phones for a specified user.”

Gives you the desk phones registered to one user, and only those, so you know which physical handsets sit on that person's desk.

When to use it
during offboarding, IT needs to know which physical phone to pick up from the departing person.
Watch out
this list stops at desk phones; List a User's Devices returns every device linked to the user.
Dialpad29

List a User's Devices

Search

In Make“Returns a list of devices for a specific user.”

Lists every device linked to one user, handy to understand where a call will ring before you trigger one.

When to use it
ahead of Initiate an Outbound Call, to pick the single device that should ring.
Watch out
each device arrives as its own bundle, so a user with several devices multiplies the operations of the next steps.
Dialpad30

List Blocked Numbers

Search

In Make“Lists all numbers that have been blocked via the API.”

Shows the numbers that were blocked through the API, which makes a scenario-driven block list easy to audit.

When to use it
a support lead wants a shared sheet listing every number your automations have blocked.
Watch out
the listing covers blocks made via the API, so numbers blocked by hand in Dialpad may not appear.
Dialpad31

List Contacts

Search

In Make“Returns a list of contacts, or a user's local contacts if the owner ID is provided.”

Returns your Dialpad contacts, or the local contacts of one user when you give an owner ID, to search before you create or update.

When to use it
checking whether a lead is already in Dialpad before Create a Contact runs.
Watch out
with the owner ID set, you only see that user's local contacts, not the shared ones.
Dialpad32

List Numbers

Search

In Make“Returns a list of numbers in your company.”

Brings back the numbers your company owns in Dialpad, one bundle each, to build an inventory or pick a free line.

When to use it
a telecom manager keeps a sheet of every line and who holds it.
Watch out
the list can be long; send it through an aggregator or straight to a sheet rather than a module that emails each row.
Dialpad33

List Office Call Centers

Search

In Make“Returns a list of call centers for a specified office.”

Lists the call centers that belong to one office, a good starting point when you manage several support queues.

When to use it
a report per queue needs the full list for a given site before fetching details with Get a Call Center.
Watch out
the module expects an office, so List Offices usually comes first.
Dialpad34

List Office Departments

Search

In Make“Returns a list of departments for a specified office.”

Returns the departments of one office, so you can loop over teams when you build a report or sync groups with another tool.

When to use it
your org chart in an HR app should match the departments set up in Dialpad for each site.
Watch out
run it per office; a company with many sites repeats it through List Offices.
Dialpad35

List Offices

Search

In Make“Returns a list of offices.”

Lists every office in your Dialpad company, the entry point for any scenario that works site by site.

When to use it
as the first search of a reporting chain that then reads plans, departments or call centers per office.
Watch out
each office becomes a bundle, so the modules after it run once per office and consume operations accordingly.
Dialpad36

List Operators

Search

In Make“Returns a list of operators for the selected place of registration.”

Returns the operators for the place you select in the module, so you know who answers calls there.

When to use it
a front desk rota in a spreadsheet should list the people Dialpad treats as operators for that site.
Watch out
pick the right place in the module settings first; the list depends entirely on that choice.
Dialpad37

List Rooms

Search

In Make“Returns a list of rooms, optionally filtered by office.”

Gives you the rooms in Dialpad, all of them or only those of one office if you set the filter.

When to use it
a facilities team compares its list of meeting spaces with what Dialpad knows.
Watch out
without the office filter, a company with many sites gets every room at once, and each one costs an operation downstream.
Dialpad38

List Users

Search

In Make“Returns a list of users, optionally filtered by email.”

Returns Dialpad users, all of them or the one matching an email address, which is the simplest way to find a user ID.

When to use it
your HR tool only knows people by email, and Update a User needs the Dialpad ID.
Watch out
filter by email whenever you can; the unfiltered list returns every user of the company.
Need help

Need help automating Dialpad with Make?

A person reads every message.

FAQ

Dialpad and Make: common questions

01Is the Dialpad Make integration free?
Yes, Dialpad is a standard app in Make, so it works on the Free plan. That plan has limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) lift the interval to 1 minute and remove the cap on active scenarios. Make counts usage in operations, one per module run on one bundle. Your Dialpad subscription is separate and not covered here.
02What do you need to connect Dialpad to Make?
You need an active Dialpad account and either an API key created by an administrator or an OAuth token. The key lives in the Dialpad admin settings, on the API Keys page of the Authentication section: add a key, name it, set its expiration, choose the scopes and save. In Make, add a Dialpad module, click Create a connection and paste the key. For Watch Call Events, which is instant, you click Create a webhook before creating the connection.
03Does the Dialpad trigger in Make work in real time?
Yes. Watch Call Events is an instant trigger: Dialpad sends each call state change to Make through a webhook as soon as it happens, without waiting for a schedule. This is the only trigger of the Dialpad app. Everything else, like reading statistics or listing users, starts from another trigger or from the scenario schedule, which is every 15 minutes by default on a new scenario and never shorter than 15 minutes on the Free plan.
04What if a Dialpad module is missing in Make?
It depends on what you need, but the Dialpad app includes Make an API Call. That module calls any endpoint of the Dialpad API with the connection you already set up, so a feature missing from the 39 modules is usually still within reach if you can read the API reference. Also note that Make flags its Dialpad documentation as AI-generated and possibly inaccurate, so test each module with Run once on real data before relying on it.
05Should you use Make or n8n for Dialpad?
It depends on where the rest of your automations live. On Make, Dialpad comes with 39 modules, an instant trigger on call events and Make an API Call for the gaps, all described on this page. The same app often has an n8n node as well, so check that side if your team already builds there. Compare what each tool offers for the exact actions you need, and pick the one your team will actually maintain.
Same platform

Other docs you might need on this stack.

Browse all integrations