How to Create a Zapier Task for Every Aircall Missed Call

Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Create a Zapier Task for Every Aircall Missed Call.
Coding Liquids tutorial cover featuring Sagnik Bhattacharya for How to Create a Zapier Task for Every Aircall Missed Call.

Zapier has no ready-made "missed call" trigger for Aircall, so you assemble one: send Aircall's call.ended webhook to a Webhooks by Zapier Catch Hook, add a Filter that passes only inbound calls carrying a missed call reason, set a due time, then create the task in Todoist, Pipedrive or another task tool. It needs Zapier Professional or higher.

The Complete Excel Course with AI Integration

From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.

By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner

Buy now

The filter is what keeps the bill small. Every call that ends reaches the Zap, answered or not, outbound as well as inbound, but Zapier charges no tasks for the trigger or for Filter and Formatter steps. You pay one task for each missed call that gets through to the task step, and you choose which missed calls those are: a caller who hangs up within 10 seconds is logged as short_abandoned, and you may not want a callback task for every one of those.

What do you need before building the Aircall missed-call Zap?

Four things must be in place before the first test call. The third trips people up, because Zapier's Free plan looks as if it should cope with a small automation. It can't: Free has no webhooks, no Filter, no Formatter and no premium apps, and it only allows two-step Zaps, so the build below can't be published on it.

PieceWhy the Zap needs itList price (USD), checked 17 Nov 2026
Admin access to the Aircall DashboardThe Webhook app is installed under Integrations > Apps, which is the admin side of AircallIncluded with your Aircall plan
An Aircall planAircall lists APIs and webhooks on Essentials, Professional and EnterpriseEssentials $30 per licence a month billed annually, Professional $50, three-licence minimum
Zapier Professional or higherWebhooks, Filters, Paths and Formatter are paid featuresFrom $19.99 a month billed annually for 750 tasks, or $29.99 billed monthly
A task tool your team opens every dayThe task has to land where someone will see it before the caller rings a competitorTodoist, Pipedrive or similar, on whatever plan you already run

Allow about an hour for the build and another half hour for the test calls further down. Decide now who owns the Zap afterwards. A missed-call automation that quietly stops is worse than having none, because the team stops checking the call log the week it goes live.

How do you send Aircall's call.ended event to Zapier?

Create a webhook in Aircall for the call.ended event and point it at a Webhooks by Zapier Catch Hook, the route Aircall's own help article for missed-call alerts uses: one webhook, one event, and the filtering done in Zapier. A webhook is simply a message one app posts to another the moment something happens; here Aircall posts a small package of call details to a private Zapier address every time a call ends. The order of the clicks matters, because Aircall wants a URL that Zapier only gives you once the trigger exists.

  1. In Aircall, open the Dashboard and go to Integrations > Apps. Find Webhook and click Install app.
  2. Type a name in Customer webhook name. Make it descriptive, such as "Zapier missed-call tasks", so whoever audits your integrations next year knows what it feeds. Under Events, enable only call.ended. Leave URL empty for now.
  3. In Zapier, create a new Zap. Choose Webhooks by Zapier as the trigger app and Catch Hook as the trigger event.
  4. On the trigger's Test tab, copy Your webhook URL.
  5. Back in Aircall, paste it into the URL field and click Add webhook.
  6. Ring one of your Aircall numbers from a mobile and let it ring out unanswered, then run the trigger test in Zapier so the Zap has a real missed call to work with.

Why only call.ended? Aircall's developer documentation lists 19 call events, from call.created to call.comm_assets_generated, and every one you enable starts a Zap run. Runs the filter stops cost nothing, but your Zap history fills with noise and each extra event is another delivery that can fail. The call.ended event carries the whole call record at the moment its outcome is known, missed call reason included.

The package has five top-level parts: resource (here, call), event (call.ended), timestamp, token and data. The data part is the call itself, and these are the fields you'll map:

Field inside dataWhat it holdsUsed for
directioninbound or outboundThe filter
missed_call_reasonOne of six reasons, set only when an inbound call was missedThe filter and the due time
raw_digitsThe caller's number in international format, or the word anonymous for a withheld numberThe task title
started_atWhen the call began, as a Unix timestamp (seconds counted from 1 January 1970) in UTCA readable time in the note
number, then nameThe name you gave the Aircall line that was rung, such as Sales lineThe note, and a per-line filter
idAircall's unique ID for the callThe note, so duplicates are easy to spot
voicemailA link to the recording, only if a voicemail was leftUsually missing at this point; see the failure section

How do you filter missed calls from answered ones in Zapier?

Add a Filter by Zapier step straight after the trigger that passes only inbound calls carrying a missed call reason. Aircall's help article uses two rules. I'd add two more, because they stop pointless tasks before they cost anything. Filled in, the step looks like this:

Only continue if...
    data direction            (Text) Exactly matches          inbound
AND data missed_call_reason   Exists
AND data missed_call_reason   (Text) Is not in                short_abandoned
AND data raw_digits           (Text) Does not exactly match   anonymous

Zapier's text rules aren't case-sensitive, so inbound and Inbound both pass. The Is not in rule takes a comma-separated list, which makes it easy to drop another reason later without adding a rule: typing short_abandoned, abandoned_in_ivr would skip both.

The anonymous rule earns its place. Aircall writes the word anonymous into raw_digits when a caller withholds their number, and a task that says "Call back anonymous" wastes a few minutes while someone works out there is nothing to ring. The exception is a team whose withheld-number callers often leave voicemails with a number in them; if that's you, drop the rule and make sure voicemail email alerts are on, as covered in setting up Aircall voicemail greetings, transcripts and alerts.

Aircall's six missed call reasons, and which ones earn a task

Aircall's help pages define each reason precisely, and the definitions decide the filter. Here is a filled-in decision table for a team open on weekdays:

missed_call_reasonWhat Aircall means by itSuggested handling
out_of_opening_hoursThe call ended in the "At any other time" branch of a Time Rule without ringing anyoneTask, due at the next opening
agents_did_not_answerThe call lasted over 10 seconds, rang at least one person, and nobody picked up or everyone rejected itTask, due within two hours
no_available_agentThe call flow ended without ringing anyone, because nobody was free or reachableTask, due within two hours, and a rota warning
abandoned_in_ivrThe caller hung up during the phone menu or its intro messageTask, or skip if your menu is long and the volume is high
short_abandonedThe caller hung up in the first 10 seconds, or within 10 seconds of a phone starting to ringSkip; glance at the count weekly instead
abandonedThe catch-all: the caller hung up, or the flow ended without reaching a Ring To stepTask, normal priority

Two of these say more about your call flow than about the caller. A steady run of no_available_agent means calls reach a ringing step with nobody available, which is a rota or routing problem rather than a follow-up problem. A pile of abandoned_in_ivr can mean callers wait too long before the first option; time your own menu from a mobile. Either way the fix belongs in your opening hours and menu (see setting up an Aircall phone menu with opening hours), not in more tasks.

If you want help fitting missed-call follow-up into how your team actually handles callbacks, I offer one-to-one AI consultations for small businesses.

How do you turn the timestamp into a due time that follows opening hours?

Add a Formatter by Zapier step to turn Aircall's Unix timestamp into your office's local time, then a lookup table to set the due time from the missed call reason.

Turn the Unix timestamp into a local time

A note that says "missed at 1794906840" helps nobody. Add a Formatter by Zapier step: Action event Date / Time, Transform Format, Input the started_at field. Set To Format to a custom pattern such as ddd D MMM HH:mm, and set To Timezone to your office's time zone. Leave it blank and Zapier works in UTC, so a call at 09:14 on your office clock can show up an hour or more out, depending on your zone and the season.

Here is the same call before and after Stage 3, with illustrative values:

Raw from AircallWhat the task shows
started_at: 1794906840Tue 17 Nov 09:14 (when the office runs on UTC)
missed_call_reason: agents_did_not_answernobody answered
raw_digits: [caller number]Call back [caller number]
number name: Sales lineon Sales line

A lookup table that turns the reason into a due time

This is where the opening-hours logic lives, and it uses Formatter again, so it costs no tasks. Add a Formatter step with Action event Utilities and Transform Lookup Table. Set Lookup Key to the missed_call_reason field and fill in the table with due phrases Todoist understands in plain language:

Lookup Key:     data missed_call_reason

out_of_opening_hours      9am
agents_did_not_answer     in 2 hours
no_available_agent        in 2 hours
abandoned_in_ivr          in 2 hours
abandoned                 in 2 hours

Fallback Value:           today

The "9am" entry does the opening-hours work for you. Todoist reads a bare time as today if that time hasn't passed and tomorrow if it has, so a 7.30am call is due at 9am the same day and an 8pm call is due at 9am the next day. The lookup keys are case-sensitive, so type the reasons exactly as Aircall sends them, in lower case with underscores.

Weekends need one decision. A Friday-evening call gets a Saturday 9am due time. If you're closed on Saturdays, the simplest answer is to leave it: on Monday morning that task sits at the top of the overdue list, which is where you want it. If overdue tasks upset your team's reporting, add a Formatter step that turns started_at into the weekday (To Format dddd) and a Paths step that gives Friday-night and weekend calls a "Mon 9am" due time. Paths, like filters, cost no tasks.

A second lookup table (same Transform) can turn the raw reason into words for the task title: out_of_opening_hours becomes "out of hours", agents_did_not_answer becomes "nobody answered", and so on. It's free and saves your staff learning Aircall's internal codes.

How do you create the task in Todoist or Pipedrive?

Add Todoist's Create Task action with the caller's number first in the task name, or create a call activity on the right person in Pipedrive if your team works from a CRM.

Todoist: the field mapping, filled in

Add Todoist's Create Task action and map the fields like this. The example column shows the task the test call from Stage 1 should produce:

Todoist fieldMap it toExample output (illustrative)
Content (the task name)"Call back", raw_digits, then the reason in wordsCall back [caller number]: nobody answered
NoteThe formatted time, the line name and the call IDMissed Tue 17 Nov 09:14 on Sales line. Aircall call ID 1234567890. Check Aircall for a voicemail before ringing.
Due dateThe output of the due-time lookup tablein 2 hours
ProjectA shared Callbacks project everyone on the phones can seeCallbacks
LabelsA fixed labelmissed-call
AssigneeWhoever owns callbacks, or blank if the team shares the project(blank)

Put the number first in the task name. When the same caller rings three times in twenty minutes you get three tasks, and starting each with the number lets them sit together so whoever rings back can close all three.

Pipedrive: a call activity on the right person

If your team works from a CRM rather than a to-do list, put the callback where the client history already is. In Pipedrive, add a Find Persons search on the caller's number, then Create Activity with a subject ("Call back: nobody answered"), your call activity type, an owner and a note. If nobody matches, the Find or Create Person version of the search can add a person with that number so the activity has somewhere to sit. Budget for it: Zapier's task-usage page says a search set to carry on when nothing is found uses a task, so plan on up to two tasks per missed call rather than one.

If you run HubSpot, check what the native integration already does before adding a Zap. Aircall says its HubSpot integration logs calls and texts to contacts, deals and tickets, and lets admins choose a ticket pipeline and status per call type, as covered in syncing Aircall calls, voicemails and tasks to HubSpot. A Zap that duplicates it creates two records for every call.

Optional: close the loop inside Aircall

Aircall's Zapier app has an Add Comment to Call action. Put it after the task step with the call ID and a short note ("Callback task created in Todoist") and anyone who opens the call in Aircall sees it's being handled. Aircall allows five comments per call, so this leaves room for the agent's own notes. It costs one more task per missed call and needs the Aircall app connected in Zapier, which is the Zapier V4 integration described in the last section.

How do you test the missed-call Zap before switching it on?

Make five test calls from a mobile before you switch the Zap on, because publishing a Zap that passed one test proves very little. Check both the Zap history and the task list after each:

TestHow to make itWhat should happen
1. AnsweredRing the line and have a colleague pick upThe run stops at the filter. No task.
2. Quick hang-upRing and hang up after about 5 secondsStops at the filter as short_abandoned. No task.
3. Ring-out in hoursRing during opening hours and let it ring until the flow endsTask "Call back [your mobile]: nobody answered", due in 2 hours
4. Out of hoursRing while the Time Rule is closed, or briefly change the hours on a test numberTask due at 9am, with "out of hours" in the title
5. Withheld numberRing with caller ID hidden and let it ring outStops at the filter. No task.

Then make one outbound call from Aircall; it should stop at the filter too. Check the time in each task note against the call log in Aircall, which catches a wrong To Timezone before your staff do. If test 3 produced a task and test 4 didn't, the Time Rule probably routed your test call somewhere you didn't expect; look at the missed call reason the Zap received rather than assuming the filter is wrong.

One month at a five-negotiator estate agency, in tasks and dollars

Consider an illustrative estate agency with five negotiators on Aircall Essentials. Five licences at $30 a month billed annually is $150 a month for the phones. In a typical month in this illustration the team makes 900 outbound calls and receives 1,300 inbound calls, of which 160 are missed. Every one of those 2,200 calls reaches the Zap. Here is where they end up:

Calls reaching the ZapCountStopped by the filterTasks used
Outbound calls9009000
Answered inbound calls1,1401,1400
short_abandoned30300
out_of_opening_hours55055
agents_did_not_answer50050
no_available_agent15015
abandoned_in_ivr606
abandoned404
Total2,2002,070130

So 2,200 Zap runs cost 130 tasks. Adding the Aircall comment step doubles that to 260; the Pipedrive version with its search step uses up to 260 before any comment, 390 with one. All of these fit inside Zapier Professional's 750-task tier at $19.99 a month billed annually ($29.99 billed monthly), with room left for the agency's other Zaps. If this were the only Zap, each followed-up missed call would cost about 15 cents ($19.99 divided by 130).

The useful comparison isn't the 15 cents. Before the Zap, those 130 calls were rows in a call log that someone was supposed to scan between viewings. After it, the 55 out-of-hours callers are waiting in the Callbacks project at 9am with the line they rang, and the 15 no_available_agent calls show up as a cluster on the days the rota was thin. Price one recovered valuation against $20 a month and the decision makes itself.

Growth changes the maths slowly. If a second team doubles the missed calls, the plain Todoist version uses 260 tasks a month, still inside 750. Past 750, the next Professional tier is 1,500 tasks for $39 a month billed annually ($58.50 monthly). If you switch on Zapier's pay-per-task billing instead, extra tasks cost 1.25 times your plan's task rate on annual billing and 2.5 times on monthly billing, and usage stops at three times your subscription. Weighing that against a move up a plan is covered in Zapier Professional or Team for a growing business.

Aircall's own limits rarely matter at this size. A company can have up to 100 webhooks, which only bites if you build one per line; one webhook with a per-line filter rule is easier to look after. Aircall's public API allows 120 requests a minute per key, and 130 comments a month is nowhere near that.

If you review the missed-call numbers in a spreadsheet, try The Complete Excel Course with AI Integration on Coding Liquids.

Why do Aircall tasks stop appearing, double up or show the wrong time?

Missing tasks often trace back to a webhook that Aircall disabled while the Zap was switched off, and doubled tasks, a missing voicemail, times an hour out and a task step that fails unnoticed each have their own fix below.

The long weekend the webhook switched itself off

This failure catches people out because nothing looks broken. An office manager switches the Zap off on a Friday afternoon to reword the task title, then forgets about it until Tuesday. Once a Zap is off, Zapier answers its webhook address with a "not found" error. Aircall retries a failed event up to 50 times, then disables the webhook and shows a notice on the Dashboard. It keeps retrying the failed events for up to 12 hours and switches the webhook back on if one succeeds, but by Tuesday that window has long closed. Turning the Zap back on changes nothing. The first sign was an empty Callbacks project on Tuesday while the Aircall call log showed 14 missed calls since Friday, and a seller ringing again to ask why nobody had called back.

The fixes: get the webhook running again (deleting it under Dashboard > Integrations > Apps and adding it again with the same Zapier URL is the dependable route; Aircall's API can also re-activate it), and have an Aircall admin turn on the email notifications for disabled and re-enabled webhooks in User Settings, so the next one reaches someone's inbox. If you must switch the Zap off for more than a few hours, put "check the Aircall webhook" in your diary for when you switch it back on. Aircall also gives your endpoint only 5 seconds to reply, which Zapier's webhook address normally manages, but it is one more reason not to put anything between Aircall and Zapier.

Two tasks for one call

Aircall delivers each event at least once, which means occasionally twice. If two tasks carry the same call ID in the note, that's what happened; delete one. If it happens weekly, add Todoist's Find Task search before Create Task, looking for the call ID (put the ID in the task name if the search only matches names), plus a filter that continues only when nothing was found. That search costs a task of its own.

No voicemail in the task

Aircall's Zapier listing describes the voicemail as present about 30 seconds after a call ends, so the call.ended package can arrive before the recording exists. Even when it is there, the raw recording link expires after an hour (the short link after three), so a link pasted into a task dies before lunch. Tell staff to open the call in Aircall instead; that's why the example note says "Check Aircall for a voicemail before ringing".

Times an hour out

To Timezone was left blank, so Formatter used UTC. Set it to your office's zone and re-run test 3.

The task step fails and nobody notices

Connections to Todoist or Pipedrive can expire, and then every missed call errors at the task step. Don't rely on Zapier's automatic switch-off to warn you: it acts when a Zap errors 95% of the time and has run more than 20 times in the past 7 days, and most runs of this Zap stop harmlessly at the filter, so a broken task step may never reach that threshold. Put a weekly five-minute check in someone's diary: missed calls in Aircall against tasks created, which should match minus the reasons you skip. The routine is laid out in stopping Zapier automations from breaking silently.

Should you use Aircall's Zapier V4 trigger instead of a webhook?

You can use Aircall's native Zapier app, listed in the Dashboard under Integrations > Apps as Zapier V4, instead of a webhook, but pick one route per Zap. Install it there (Aircall says you need admin access), connect your Aircall account inside Zapier, and choose the lines it should report on under Select numbers. Its trigger list includes Call Ended, which can start the same Zap, and it adds Aircall actions such as Add Comment to Call. Aircall's help page notes that this integration is separate from Webhooks by Zapier.

Three things to know before you choose it. Only numbers linked to the integration send data, so a line you add next year stays silent until someone adds it under Select numbers. When a trigger stops firing, Aircall's troubleshooting steps are to check the Active toggle on the integration's General tab, check the Numbers list, then paste a recent call ID into the Calls section, which only searches the last 7 days. And before you rely on it, confirm that your first Call Ended sample includes the missed call reason field, because the filter in Stage 2 depends on it. The filter, Formatter and task steps are otherwise the same, and either route needs Zapier Professional because of the filter.

For most small teams I'd start with the webhook route, because it is the one Aircall documents for missed calls and it reports on every line without anyone remembering to tick a new number. Switch to Zapier V4 when you want several Aircall actions in the same Zap and you're happy to keep its number list current.

More questions about missed-call tasks from Aircall

Can the Zap close the task when we ring the caller back?

Not on its own. The Zap fires once, when the missed call ends, and nothing in it watches for your callback. The simplest option is to close the task by hand. You can build a second Zap that starts on outbound calls, searches Todoist for an open task containing that number and marks it complete, but test the search carefully: a loose match can close the wrong caller's task.

Will calls to every Aircall number create tasks?

Yes, unless you filter them out. The Aircall webhook reports calls from the numbers it covers, so a sales line and a lettings line can both feed the same Zap. To keep tasks to one line, add a filter rule on the number's name from the payload, for example Number Name exactly matches Sales line. One webhook with a rule per line is easier to maintain than a webhook per number.

Can I post missed calls to Slack as well as creating a task?

Yes. Aircall's own help article builds this exact webhook and filter to send a Slack message, so you can add a Slack step such as Send Channel Message after the task step. Each extra action uses one more Zapier task per missed call, so a Slack alert plus a task doubles the monthly task count for this Zap.

Do unanswered outbound calls count as missed calls?

No. Aircall only gives a missed call reason to inbound calls, and the filter's first rule drops every outbound call anyway. If you want a reminder to retry outbound calls that nobody answered, that is a different Zap with its own rules, and it is better handled in your CRM's call outcomes.

Does Zapier have a missed call trigger for Aircall?

No ready-made one, so you assemble it: send Aircall's call.ended webhook to a Webhooks by Zapier Catch Hook, filter for inbound calls carrying a missed call reason, then create the task. The build needs Zapier Professional or higher, because the Free plan has no webhooks or Filter step and allows only two-step Zaps.

Further reads

Sources: Aircall help pages on Slack notifications for missed calls with Zapier, missed call reasons in call flows, configuring the Zapier integration and its troubleshooting; Aircall developer documentation (call and number objects, webhook usage, best practices); Aircall pricing page; Zapier pricing page and help pages on task usage, filters, filter rules, Formatter date formats, lookup tables, webhooks and automatic Zap turn-off; Zapier app listings for Aircall, Todoist and Pipedrive; Todoist help on due dates. All checked 17 Nov 2026.

Have a specific process in mind?

Describe the job in your own words on a 1:1 call and I'll show you what AI you can use for it with the tools you already pay for.

Book a 1:1 call with me