Aircall app
Call records, log activity, and build call workflows.
Available on all plans.
Admins can install the Aircall app.
Once installed, all members can use it.
Connect Attio with Aircall to make phone calls to your person records, automatically log call activity, and build workflows that trigger on calls and messages.
Connect Aircall with Attio
Note that you must be a workspace admin to set up the Aircall app. Follow these steps to integrate Attio with Aircall:
Click on your workspace name, select Workspace settings from the dropdown, then Apps in the sidebar.
Find the Aircall app and click Install.
Click + Connect, which will take you to Aircall.
4. Log in, and click Authorize to allow Attio to access your call information.
5. Click + Add numbers, select the phone number you want to use, then click Confirm and Add numbers.
6. Once done, you should see the new connection to Aircall is Connected.
Call a record in Attio
Once you've set up the app connection, you must have Aircall Workspace for Desktop downloaded and open to make a call. Follow these steps to make a call:
Open the person or company record page for the contact you want to call. Make sure a phone number has been added to the person record’s phone number attribute.
Click the Call button in the top-right corner. If you're calling from a company record, choose the team member you want to call.
3. If the Aircall app isn’t already open, you will be prompted to open it. The phone number from Attio will be pre-filled in Aircall.
4. Choose the line you want to call from, and click Call now in Aircall to start the call. Details like the person's job title and location will appear in Aircall.
Power dial from Attio
You can add people from Attio to an Aircall dialer campaign to automatically import their phone numbers into a dialing list, enabling efficient outbound calling:
From People or any list of people, select the checkboxes next to the people you want to power dial.
Click More, then Add to dialer campaign.
When you're ready, navigate to the Power Dialer from the Aircall app and Start session.
Automated notes for Aircall calls
Once Attio is connected to Aircall, a note will automatically be added to a person's record in Attio within a few minutes of any successful call made through Aircall, even if the call wasn't initiated from Attio. Notes are also created for inbound calls.
Note: For call notes to sync, the person record must already exist in Attio with the correct phone number. The integration won’t create new records, and calls made before a record was created will not be synced.
Notes created from Aircall will include:
The name of the team member who placed the call in the title
The date and time (in UTC time zone) that the call was placed
The length of the call
Whether or not the call was answered
Any notes taken within Aircall during the call
Use Aircall in workflows
You can use Aircall blocks in workflows to trigger automations when calls or messages end, send SMS messages, and add contacts to an agent's dialer queue.
Call ended (trigger)
The call ended trigger fires when an Aircall call ends. Use it to automate post-call actions like updating a deal stage after a sales call, or creating a task to follow up when a voicemail is left.
Inputs:
Number filter (optional): Limit the trigger to a specific Aircall number. If left empty, the trigger fires for all numbers.
Outcomes:
Answered: The call connected. Outputs include call identity (ID, direction), timing (started at, answered at, ended at, duration), Aircall number details, contact details, phone number and contact, the agent who handled the call, recording URL, voicemail URL, comments, and tags.
Missed: The call did not connect. Outputs include call identity (ID, direction), timing (started at, ended at), Aircall number details, contact details, phone number and contact, the agent, missed call reason (inbound only), voicemail URL if one was left, comments, and tags.
Note: Recording and voicemail URLs are generated asynchronously and may not be present when the trigger fires immediately after the call ends.
Message received (trigger)
The message received trigger fires when an inbound SMS, MMS, or WhatsApp message is delivered through Aircall. Use it to create follow-up tasks, update a deal stage, or alert your team on Slack when a message arrives.
Inputs:
Number filter (optional): Limit the trigger to a specific Aircall number. If left empty, the trigger fires for all inbound messages across your Aircall numbers.
Outcomes:
Received: An inbound message arrived. Outputs include message ID, channel (sms or whatsapp), timestamp, message body, media attachments (an array of file name, file type, and URL for each attachment, empty for plain text messages), sender phone number and contact, and Aircall number details.
Note: MMS messages are reported with a channel value of sms. To detect attachments, check whether the media output contains items.
Add to dialer campaign
The add to dialer campaign block queues a phone number into a specific Aircall agent's Power Dialer. Use it to route missed-call leads back to the agent who took the original call, or to add a newly qualified contact to a sales rep's call list when a deal reaches a certain stage.
Inputs:
Aircall user (required): The agent whose dialer queue the number should be added to. You can select a specific user or or use a variable from an earlier block in the workflow, for example the agent from a call ended trigger.
Phone number (required): The phone number to add to the queue.
Outcomes:
Added: Aircall accepted the number. Outputs include the Aircall user ID and the phone number that was queued. This outcome also covers cases where the number was already in the queue.
Send message
The send message block sends an outbound SMS through an Aircall number. Messages appear in the agent's Aircall inbox, so any inbound replies go directly to them. Use it to acknowledge a missed call, send a reminder when a deal hits a stage, or send a welcome message when a person is added to a list
Inputs:
Line (required): The Aircall number to send from. You can select a specific number or use a variable from an earlier block in the workflow, for example the line that received an inbound call.
Recipient (required): The phone number to send the message to.
Body (required): The message text. Supports variable bindings. Maximum 1,600 characters.
Sender (optional): The Aircall user to attribute the message to, so it appears in their outbound history.
Outcomes:
Sent: Aircall accepted the message. Outputs include message ID, direct link, status, sent timestamp, and the recipient, body, line, and sender are returned as outputs so you can use them in later blocks.
Rejected: Aircall was unable to send the message and won't retry, for example due to an unsupported line, or sender and recipient being the same number. Outputs include the line, recipient, and the reason returned by Aircall so the workflow can branch accordingly.