Resources · Make integration

Aircall Make integrationAutomate Aircall with Make.

What if every Aircall call updated your other tools on its own? The Aircall Make integration gives you 27 modules: 6 instant triggers, 18 actions and 3 searches. This guide shows you how to connect your account and build a first working scenario, no code involved.

Try the Aircall integration on MakeSee the 27 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the Aircall Make integration automate for your team?

The Aircall Make integration links your phone system to the other apps your team uses. In Make, you build a scenario, which is the automation itself: a chain of modules, each one a brick that watches Aircall, acts on a call or searches your data. Calls, recordings, messages, users and contacts can all take part.

A call history that files itself. Watch Calls starts the scenario when Aircall reports a call event. Add Tag a Call or Comment a Call, and each conversation carries the context your team would otherwise type by hand.

Context on screen while the phone rings. Display Insight Cards shows cards to the agent during an ongoing call. Fill them from your CRM, and the agent has the caller's account in view while the conversation is still going.

Texts that go out without an agent. Send a Message sends a text or multimedia message from a configured number, and Send a Message in Agent Conversation keeps the text inside the agent's thread so nobody loses track of it.

The Aircall documentation in Make gives no numeric limit for these modules. When you need an endpoint the list does not cover, Make an API Call reaches the Aircall API with the same connection. Aircall may also have a node in n8n; the n8n vs Make comparison helps you pick a tool, and Make training covers the editor from the start. If a run fails, Make troubleshooting lists the usual fixes.

Connect

How do you connect Aircall to Make?

  1. 01

    Add an Aircall module

    Open your scenario, add any Aircall module and click Create a connection. The connection is your Aircall account linked to Make once, then reused by every Aircall module. For an instant module, click Create a webhook first, then Create a connection.

  2. 02

    Name it and authorize

    Type a label in Connection name if you manage several accounts, then click Save. When the Aircall window opens, log in and confirm the access Make asks for. You need an existing Aircall account for this step.

  3. 03

    Pick your numbers

    Click Add numbers and select the Aircall number or numbers the connection should use. Only the numbers you choose here are available to the scenario, so take the lines your automation actually concerns.

First scenario

Your first scenario: create Aircall contacts from your lead source

GoalWhen a new lead arrives in your form or CRM tool, Make creates the matching contact in Aircall.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the + to add the first module. This first module decides when the scenario starts.

  2. 02

    Choose where leads come from

    Search the app that collects your leads, such as your form tool or CRM, pick its trigger module and click Create a connection to link that account.

  3. 03

    Add Create a Contact

    Click the + on the right of the first module, search Aircall and pick Create a Contact. Connect your Aircall account, then map the lead's details from the first module into the contact.

  4. 04

    Test with Run once

    Click Run once to execute the scenario one time. Each module shows the bundles it received, a bundle being one item passed along, here one lead. Check that the contact appears in Aircall.

  5. 05

    Schedule and switch on

    Set the schedule on the first module (every 15 minutes by default for a new scenario) and switch the scenario on. Each module run on a bundle counts as one operation on your Make plan.

Triggers

Aircall triggers: what starts your scenario

6 modules start a scenario when something happens in Aircall. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Aircall as soon as it happens.

Aircall1Watch Calls

Watch Calls

Instant trigger

In Make“Watches for events related to calls.”

Watch Calls starts your scenario as soon as Aircall reports an event on a call, so call data can reach your CRM, a sheet or a team channel without anyone copying it. Each event arrives as one bundle that the next modules can use.

How it fires
instant. Aircall calls Make through a webhook as soon as the event happens, which is why the module shows the lightning badge.
When to use it
when the call itself is the starting point, for example to log calls or pair it with Tag a Call.
Watch out
it covers call events in general. Click Run once and read the bundle before you add filters.
Aircall2Watch Numbers

Watch Numbers

Instant trigger

In Make“Watches for events related to numbers.”

Changes on your Aircall phone numbers become a starting point with Watch Numbers, so the tools that list your lines stay in step with Aircall. You no longer have to remember to update a directory after a number is touched.

How it fires
instant. Aircall sends the event to Make by webhook the moment it happens.
When to use it
when an internal directory, a sheet of lines or an admin channel should hear about number events.
Watch out
the documentation only says number events. Run the scenario once to see which ones reach Make.
Aircall3Watch Contacts

Watch Contacts

Instant trigger

In Make“Watches for events related to contacts.”

Your CRM hears about Aircall contacts through Watch Contacts, which starts the scenario on each contact event in Aircall. Agents can keep editing contacts in the phone app while the other tools follow.

How it fires
instant. Aircall calls Make through a webhook right when the contact event happens.
When to use it
when contacts created or edited by agents must also exist in your CRM or mailing tool.
Watch out
if another scenario creates contacts in Aircall with Create a Contact, this trigger can fire on them too; add a filter so the two scenarios do not feed each other.
Aircall4Watch Users

Watch Users

Instant trigger

In Make“Watches for events related to users.”

Team changes in Aircall reach your other tools through Watch Users, which reacts to events on Aircall users. It turns an admin action in Aircall into a signal for onboarding or offboarding elsewhere.

How it fires
instant. Aircall notifies Make by webhook as soon as a user event happens.
When to use it
when HR, IT or a manager should know that an Aircall seat changed, or when a user sheet must stay current.
Watch out
the bundle carries the user event; add Get a User after it if the next module needs more details on that person.
Aircall5Watch Conversation Intelligence Events

Watch Conversation Intelligence Events

Instant trigger

In Make“Watches for conversation intelligence events (call sentiment, summary, transcription, key topics).”

Call sentiment, summaries, transcriptions and key topics can travel to your other tools with Watch Conversation Intelligence Events. The scenario starts when Aircall produces one of these events for a call.

How it fires
instant. Aircall calls Make through a webhook once the event is ready.
When to use it
when a manager wants call summaries in a shared document, or a CRM record should keep the key topics of each conversation.
Watch out
each kind of event reaches Make separately. Use Run once to see which event came in, then filter on the type you want.
Aircall6Watch Messages

Watch Messages

Instant trigger

In Make“Watches for message events (sent, received, status update).”

Sent, received and status update events on Aircall messages start your scenario with Watch Messages. Text conversations can then land in your CRM or support tool next to the call history.

How it fires
instant. Aircall calls Make through a webhook as soon as the message event happens.
When to use it
when an incoming text should open a ticket, or when you want a trace of every message your team sends.
Watch out
three event kinds share this trigger, so one message can produce several runs. Filter on the event kind to avoid duplicates and wasted operations.
Modules

Aircall modules: what your scenario can do

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

Calls

10 modules
Aircall1

List Calls

Search

In Make“Fetch all calls associated to a company and their information.”

List Calls pulls all the calls tied to your Aircall company, with their information, so you can build a complete export or a report.

When to use it
when you need the whole history rather than one call, for example to fill a reporting sheet from scratch.
Watch out
it can return many bundles, and every module that runs after it on each bundle costs an operation.
Aircall2

Search Calls

Search

In Make“Searches for specific calls.”

Search Calls narrows the list down to the specific calls you are looking for, instead of loading everything.

When to use it
when a contact reaches out again and the scenario should check the previous calls before acting.
Watch out
a search returns zero, one or several bundles. Decide what the scenario does when nothing matches.
Aircall3

Get a Call

Action

In Make“Gets informations about a specific call.”

Get a Call gives the following modules the full information of one call you have already identified.

When to use it
after a trigger or a search handed you a call and the next step needs details the first bundle did not carry.
Watch out
map the call from an earlier module rather than typing it, or the scenario will read the same call every time.
Aircall4

Transfer a Call

Action

In Make“Transfers a call to another user, team or number.”

Transfer a Call hands a call to another user, a team or a number, following a rule set in your scenario instead of an agent's click.

When to use it
when data from another tool decides who should take the conversation, such as sending a key account to its account manager.
Watch out
it acts on real calls, so test it with a colleague before you switch the scenario on.
Aircall5

Comment a Call

Action

In Make“Adds a comment to a call.”

Comment a Call writes a comment on a call in Aircall, putting outside context where your agents already look.

When to use it
to push the deal stage from your CRM, or the result of a form, onto the call your team will review.
Watch out
each comment costs an operation. Filter upstream so only the calls that matter get one.
Aircall6

Tag a Call

Action

In Make“Relates a tag to a call.”

Tag a Call relates a tag to a call, which gives your team a simple way to sort and find conversations later.

When to use it
once the scenario has classified a call, for instance a caller flagged as a priority customer in your CRM.
Watch out
reuse the tags your team already works with in Aircall, so the automation does not scatter new labels everywhere.
Aircall7

Archive a Call

Action

In Make“Archives a call.”

Archive a Call archives a call in Aircall once your scenario has done what it needed to do with it.

When to use it
after the call has been logged in your CRM and nobody on the team needs to act on it.
Watch out
Unarchive a Call can bring it back, but a wrong filter can archive a batch at once; test on one call first.
Aircall8

Unarchive a Call

Action

In Make“Unarchives a call.”

Unarchive a Call restores a call you had archived, so it is back in view for the team.

When to use it
when a customer comes back about a matter you had closed and the earlier call matters again.
Watch out
find the right call first with Search Calls; a loose mapping restores a call nobody asked for.
Aircall9

Display Insight Cards

Action

In Make“Displays insight cards in an ongoing call.”

Display Insight Cards puts cards in front of the agent during an ongoing call, filled with context from your other tools.

When to use it
when an incoming caller matches an account in your CRM and the agent should see its details while talking.
Watch out
it targets a call in progress, so place it right after an instant trigger such as Watch Calls rather than behind a long chain.
Aircall10

Delete Voicemail

Action

In Make“Deletes call voicemail.”

Delete Voicemail removes the voicemail attached to a call, so you keep only what your policy allows.

When to use it
when voicemails must go once they have been handled, for example after they were saved in another tool.
Watch out
a deletion does not come back. Put a filter in front and test on a dummy call.

Recordings

3 modules
Aircall11

Pause Recording

Action

In Make“Pauses recording on a Call.”

Pause Recording stops the recording of a call for a while, driven by your scenario instead of an agent remembering to do it.

When to use it
when a sensitive part of the conversation, like payment details, should stay off the recording.
Watch out
plan Resume Recording in the same flow, or the rest of the call stays unrecorded.
Aircall12

Resume Recording

Action

In Make“Resumes recording on a call.”

Resume Recording turns recording back on for a call whose recording was paused.

When to use it
right after the sensitive step is over, as the natural partner of Pause Recording in the same scenario.
Watch out
map the exact call the pause targeted; pointing at another call does nothing useful for the one still paused.
Aircall13

Delete Recording

Action

In Make“Deletes call recording.”

Delete Recording erases the recording of a call from Aircall when you must not keep it.

When to use it
when a caller asks for their recording to be removed, or your retention policy says recordings go after a given event.
Watch out
a deleted recording is gone for good. Keep a filter in front and try it on a test call first.

Messages

2 modules
Aircall14

Send a Message

Action

In Make“Send a text or multimedia message from a configured number.”

Send a Message sends a text or a multimedia message from one of your configured Aircall numbers, with content built from earlier modules.

When to use it
to confirm an appointment or follow up after a call, without an agent typing the same text again.
Watch out
the message leaves from the number you pick, so choose the line your contacts already know.
Aircall15

Send a Message in Agent Conversation

Action

In Make“Send a text message from an Aircall SMS-capable number that will be stored and added in the agent conversation.”

Send a Message in Agent Conversation sends a text that Aircall stores in the agent's conversation, so the team sees it in context.

When to use it
when agents should find the automated text next to their own exchanges with the contact.
Watch out
it needs an Aircall number that can send SMS and it sends text only; for media, use Send a Message.

Configurations

2 modules
Aircall16

Create a Configuration

Action

In Make“Creates a new configuration.”

Create a Configuration adds a new configuration to your Aircall account from a scenario, instead of by hand in the Aircall interface.

When to use it
when an event in another tool should lead to a new configuration in Aircall.
Watch out
the documentation says little about this module, so test it with Run once on a test account and read what Make returns.
Aircall17

Delete a Configuration

Action

In Make“Deletes an existing configuration.”

Delete a Configuration removes an existing configuration from your Aircall account through your scenario.

When to use it
when a setup created by automation is no longer needed and should be cleaned up the same way.
Watch out
like any delete module, it cannot be undone from Make. Map the exact configuration and keep a filter in front.

Users

2 modules
Aircall18

Search Users

Search

In Make“Returns a lit of users filtered by creation time.”

Search Users returns the Aircall users of your account, filtered by their creation time.

When to use it
to spot the people added to Aircall since a given date, for example to set them up in your other tools.
Watch out
the filter is creation time only. To read one known person, Get a User with their user ID is the better fit.
Aircall19

Get a User

Action

In Make“Returns information about a specific user by their user ID.”

Get a User reads the information of one Aircall user from their user ID, so later modules know who handled a call.

When to use it
after Watch Users or a call event gave you a user and the next module needs more about that person.
Watch out
it expects the user ID, so map it from a previous module instead of typing it.

Contacts

1 module
Aircall20

Create a Contact

Action

In Make“Creates a contact.”

Create a Contact adds a contact to Aircall, so the person already exists there the next time your team deals with them.

When to use it
when a lead signs up through a form or lands in your CRM and should be known in Aircall too.
Watch out
its description mentions no duplicate check, so filter upstream when the same person may come back.

Other

1 module
Aircall21

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call reaches any endpoint of the Aircall API, using the same connection as the other Aircall modules.

When to use it
when none of the 27 listed modules covers the action or the data you need.
Watch out
you work with the raw API here, so keep the Aircall developer documentation open while you write the request.
Need help

Need help automating Aircall with Make?

A person reads every message.

FAQ

Aircall and Make: common questions

01Is the Aircall Make integration free?
Yes, Aircall is a standard app in Make, available from the Free plan. The Free plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the minimum interval down to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Usage is counted in credits each month: one operation for each module run on one bundle.
02What do you need to connect Aircall to Make?
You need an Aircall account. Add an Aircall module, click Create a connection, give it a name if you like, click Save, then log in to Aircall and confirm access. Make then asks you to click Add numbers and select the numbers the connection will use. For an instant module, click Create a webhook first. Teams that use their own Aircall client credentials enter them under Show advanced settings, with the redirect URI given in the Make documentation.
03Do Aircall triggers in Make fire instantly?
Yes. All 6 Aircall triggers in Make are instant: Aircall calls Make through a webhook as soon as an event happens on a call, a number, a contact, a user, a message or a conversation intelligence result. You do not wait for a polling interval, and the modules carry the lightning badge in the editor. The trigger still needs its webhook, created with Create a webhook when you add the module, and the scenario has to be switched on.
04What if an Aircall module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the Aircall API from your scenario with the same connection as the 27 listed modules, so an action or a piece of data missing from the list stays within reach. You write the request yourself, which means reading the Aircall developer documentation. The Aircall documentation in Make gives no numeric limit for the modules, so there is no published quota to plan around on the Make side.
05Should you use Make or n8n for Aircall?
It depends mostly on where your team already builds automations. On Make, Aircall comes with 27 ready modules, including 6 instant triggers, a guided connection and Make an API Call for the rest. Aircall may also have a node in n8n, so check its catalog if your workflows already live there. Compare the modules you actually need on each side and pick the tool your team will maintain. The n8n vs Make comparison on this site sets the two side by side.
Same platform

Other docs you might need on this stack.

Browse all integrations