Ellipse Gradient for Header

Aircall Integration Guide

Connect Aircall call and contact data with enterprise systems through REST APIs, selected webhook notifications, and Martini workflows.

Aircall integration options at a glance

Aircall provides a REST API for Calls, Contacts, Users, Teams, Numbers, and Tags, with paginated collection responses for scheduled synchronization. It also provides webhook-style notifications for selected call, contact, user, number, and tagging events; coverage is event-specific rather than universal. Aircall API access uses Basic Authentication with an API ID and token, while OAuth 2.0 is available for applicable application scenarios. Martini can consume these APIs, receive supported notifications through an exposed API or workflow, transform payloads, reconcile webhook activity with scheduled API reads, and deliver normalized data to CRM, support, notification, storage, or database systems.

Integration pointSupported by Aircall?Common use casesHow Martini supports it
REST APIsYesRetrieve and manage Calls, Contacts, Users, Teams, Numbers, and Tags; support scheduled synchronization and enrichment.Martini can consume Aircall REST endpoints, paginate through collections, map responses, apply business rules, and expose controlled APIs over the resulting data.
Webhooks and outbound callbacksLimitedReceive selected call-created, answered, ended, voicemail, contact, user, number, and tagging notifications.Martini can expose an API endpoint or webhook-consuming workflow, validate notifications, invoke follow-up Aircall requests, and route events downstream.
AuthenticationYesAuthenticate API requests with an Aircall API ID and token using HTTP Basic Authentication; OAuth 2.0 may apply to supported application scenarios.Martini stores credentials and applicable OAuth configuration as protected environment secrets and applies them to API-consuming workflows.
Pagination and scheduled synchronizationYesProcess collection endpoints page by page and periodically reconcile changes that are not covered by webhooks.Martini scheduler-triggered workflows can persist cursors, timestamps, or last successful pages and resume incomplete synchronizations.
File and recording resourcesLimitedProcess recording-related information or URLs attached to eligible Calls when recordings are available and permitted.Martini can route recording metadata or retrieve permitted content, subject to access, retention, privacy, and URL requirements.
Bulk, asynchronous, or batch APIsNot confirmedNo general-purpose Aircall bulk or asynchronous resource API was confirmed; large transfers should use paginated REST requests.Martini can control pagination, concurrency, checkpoints, and retries rather than assuming a bulk endpoint.
GraphQL APIsNot confirmedNo official Aircall GraphQL API was confirmed.Martini can use the documented REST approach; it should not assume GraphQL access for Aircall.
SOAP APIsNot confirmedNo official Aircall SOAP API was confirmed.Martini should use Aircall REST APIs and selected webhook notifications rather than designing around SOAP.

How Aircall exposes data and business events

Aircall REST APIs

Aircall's REST API provides access to resources including Calls, Contacts, Users, Teams, Numbers, and Tags. Collection endpoints are paginated, making the API suitable for controlled retrieval, enrichment, and scheduled reconciliation.

Martini implementation pattern

Martini implementation pattern: a workflow authenticates with protected Aircall credentials, retrieves pages, validates responses, maps Aircall objects into a canonical model, and writes them to downstream systems. The workflow stores progress and distinguishes transient failures from authorization, permission, and missing-resource errors.

Implementation sequence

Authenticate with an Aircall API ID and token
Request the relevant Aircall resource page
Read pagination metadata and persist progress
Map the response into the target data model
Apply matching, filtering, and business rules
Write the result and store the checkpoint

Aircall Webhook Notifications

Aircall supports webhook-style notifications for selected events, including typical call creation, answering, ending, and voicemail activity, plus selected contact, user, number, and tagging events. Coverage depends on the configured event set.

Martini implementation pattern

Martini implementation pattern: an exposed API receives the notification, validates the request according to the configured Aircall security method, deduplicates the event, and retrieves the current Aircall resource when the payload is incomplete. The workflow then routes the normalized event to CRM, support, collaboration, or internal systems.

Implementation sequence

Receive the Aircall webhook notification
Validate the request and event payload
Check the event or object key for duplicates
Retrieve the current resource when enrichment is required
Apply routing and business rules
Deliver the result or persist it for retry

Aircall Scheduled Reconciliation

Because Aircall webhook coverage is selective, scheduled REST synchronization can reconcile Calls, Contacts, Users, and Numbers and identify activity missed by notifications. Large synchronizations should use pagination rather than assuming a bulk API.

Martini implementation pattern

Martini implementation pattern: a scheduler starts a checkpointed workflow, retrieves pages with controlled concurrency, filters by supported timestamps or synchronization criteria, and commits progress only after downstream writes succeed. Reconciliation can be combined with webhook processing to provide a more complete operational view.

Implementation sequence

Start the scheduled synchronization workflow
Load the last successful cursor or timestamp
Retrieve Aircall pages with controlled request volume
Transform and upsert each object idempotently
Record successful progress after downstream writes
Report failures for retry and reconciliation

Common Aircall integration patterns

Pattern 1: Synchronize Aircall calls to a CRM

When to use this pattern

Use this pattern when sales or support teams need Aircall activity associated with CRM contacts, accounts, leads, or cases. Webhook notifications provide timely processing for supported events, while scheduled REST reconciliation covers gaps.

Integration direction
Aircall
Martini
Salesforce
Example Mapping
Aircall FieldCanonical FieldTarget Field
call.idactivity.externalIdAircall_Call_ID__c
call.directionactivity.directionCallDirection
call.durationactivity.durationSecondsDurationInSeconds
call.started_atactivity.startedAtStartTime
Martini implementation pattern

Martini receives a selected event or retrieves Calls, normalizes participants and phone numbers, matches the caller to a CRM record, enriches the activity when necessary, and upserts it using the Aircall Call ID. Duplicate keys, ambiguous matches, rate limits, and CRM failures are routed to retry or reconciliation handling.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • business rules
  • error handling
  • scheduled synchronization

Pattern 2: Route call and voicemail notifications

When to use this pattern

Use this pattern when operations teams need near-real-time alerts for missed calls, voicemail activity, or selected call outcomes in collaboration or support channels.

Integration direction
Aircall
Martini
Slack
Example Mapping
Aircall FieldCanonical FieldTarget Field
call.idnotification.eventIddeduplicationKey
call.directionnotification.callDirectionmessage field
call.statusnotification.outcomemessage field
call.phone_numbernotification.aircallNumberchannel routing
Martini implementation pattern

Martini validates the Aircall notification, suppresses duplicate deliveries, applies routing rules based on Number, Team, status, or voicemail activity, formats the message, and sends it to the selected destination. Delivery failures are persisted for retry without losing the original event.

Martini capabilities used
  • API exposure
  • webhook consumption
  • workflow orchestration
  • data transformation
  • business rules
  • retry handling

Pattern 3: Export Aircall activity to a reporting store

When to use this pattern

Use this pattern for scheduled operational reporting when Calls, Contacts, Users, or Numbers need to be transformed into JSON, CSV, Excel, or database records.

Integration direction
Aircall
Martini
PostgreSQL
Example Mapping
Aircall FieldCanonical FieldTarget Field
call.idcall.externalIdaircall_call_id
call.statuscall.statusstatus
call.durationcall.durationSecondsduration_seconds
user.idagent.externalIdaircall_user_id
Martini implementation pattern

A Martini scheduler loads the last checkpoint, retrieves Aircall pages, transforms objects into the reporting schema, and commits records only after successful writes. The workflow controls request volume, handles partial runs, and resumes from the last durable checkpoint.

Martini capabilities used
  • scheduler triggers
  • API consumption
  • pagination orchestration
  • mapping and transformation
  • database connectivity
  • monitoring

Pattern 4: Govern Aircall call recordings

When to use this pattern

Use this pattern when approved recording metadata or content must be associated with CRM cases, compliance storage, or retention workflows. It requires account-level recording availability and careful privacy controls.

Integration direction
Aircall
Martini
ServiceNow
Example Mapping
Aircall FieldCanonical FieldTarget Field
call.idinteraction.externalIdu_aircall_call_id
call.recording_urlinteraction.recordingReferenceu_recording_reference
call.started_atinteraction.startedAtopened_at
call.contact_idinteraction.contactExternalIdcaller_reference
Martini implementation pattern

Martini validates that a recording reference is present and permitted, retrieves metadata or content according to policy, applies retention and access rules, and associates the result with the target interaction. The workflow avoids sensitive logging and routes inaccessible or expired resources for review.

Martini capabilities used
  • workflows
  • API consumption
  • data mapping
  • privacy business rules
  • secure secrets
  • error handling

Applications commonly integrated with Aircall

Aircall data can be orchestrated into customer, support, collaboration, and enterprise workflow applications. The exact object mappings and account permissions should be validated for each implementation.

Application Scenario Direction Martini Pattern
Salesforce Associate Aircall calls and contact activity with Leads, Contacts, Accounts, Cases, and Opportunities. Aircall → Martini → Salesforce Receive selected Aircall events or retrieve paginated Calls and Contacts, normalize phone numbers, match CRM records, and upsert activity with durable Aircall identifiers and retry handling.
HubSpot Synchronize call history and contact context with CRM engagement and customer records. Aircall → Martini → HubSpot Use Aircall webhooks for selected activity, enrich with REST API data when needed, map caller identifiers to HubSpot contacts, and route failed writes for retry or reconciliation.
Zendesk Link caller information and call outcomes to tickets and support histories. Aircall → Martini → Zendesk Process call events in a Martini workflow, match Contacts or phone numbers to Zendesk users, and create or update support activity while preserving event keys for idempotency.
Slack Notify operational teams about missed calls, voicemail activity, and selected call outcomes. Aircall → Martini → Slack Receive an Aircall notification, apply routing and severity rules, format a concise message, and send it to the appropriate Slack destination with duplicate suppression.
Microsoft Teams Coordinate telephony-related alerts and collaboration workflows across enterprise teams. Aircall → Martini → Microsoft Teams Transform selected Aircall events into collaboration notifications, route them by Team or Number, and retain delivery status for operational troubleshooting.
Intercom Connect call activity and customer identifiers with conversations and support context. Aircall → Martini → Intercom Normalize Aircall Contacts and call participants, match them to Intercom contacts, and write approved activity or context with fallback handling for ambiguous phone matches.
ServiceNow Create or update incidents, tasks, or customer-service records based on relevant call events. Aircall → Martini → ServiceNow Use a webhook or scheduled reconciliation workflow to validate Aircall activity, apply incident-creation rules, map call details into ServiceNow fields, and retry downstream failures.
NetSuite Transfer qualified call or customer activity into account and customer-service processes. Aircall → Martini → NetSuite Retrieve and filter Aircall Calls and Contacts, enrich them with matching business identifiers, and send approved activity to NetSuite through a controlled workflow or intermediary process.

How to build a Aircall integration in Martini

Objective

Configure Aircall authentication and protect credentials before any workflow calls the API.

Instructions in Martini

  • Store the Aircall API ID and token as protected Martini secrets
  • Use OAuth 2.0 only where the Aircall application and account configuration support it
  • Configure the Aircall base URL and environment-specific settings
  • Apply request and webhook security controls

Objective

Select event-driven processing, scheduled synchronization, or a combination based on Aircall event coverage and completeness requirements.

Instructions in Martini

  • Use a webhook-consuming API for supported Aircall events
  • Use a scheduler for pagination and reconciliation
  • Define the source-of-truth and checkpoint strategy
  • Plan for overlap between notifications and scheduled reads

Objective

Obtain Aircall data and enrich event payloads where the notification does not contain the complete resource.

Instructions in Martini

  • Validate incoming webhook requests and payloads
  • Retrieve Calls, Contacts, Users, Teams, Numbers, or Tags through the REST API
  • Process collection endpoints page by page
  • Persist progress only after successful downstream handling

Objective

Coordinate validation, enrichment, routing, transformation, and target writes in a maintainable Martini workflow.

Instructions in Martini

  • Separate notification intake from downstream processing when appropriate
  • Apply conditional routing by event, Team, Number, or status
  • Use reusable workflow logic for normalization and deduplication
  • Keep partial failures visible and recoverable

Objective

Convert Aircall objects into canonical and target-specific models without losing identifiers needed for reconciliation.

Instructions in Martini

  • Normalize phone numbers before matching
  • Map Aircall IDs and timestamps to durable target fields
  • Convert statuses, directions, Tags, and recording references explicitly
  • Preserve relevant unknown or optional fields where useful

Objective

Enforce operational, privacy, and data-quality decisions before writing to downstream systems.

Instructions in Martini

  • Reject incomplete or unauthenticated events
  • Define rules for ambiguous contact matches
  • Apply recording access, retention, and consent policies
  • Use idempotency keys based on object and event identifiers

Common Aircall data objects used in integrations

ObjectTypical UseCommon target systemsMartini handling
CallsSynchronize inbound and outbound activity, status, direction, participants, duration, timestamps, voicemail, and recording references.Salesforce, HubSpot, Zendesk, ServiceNow, data warehousesMartini receives event notifications or retrieves Calls through paginated REST requests, normalizes phone data, enriches details, and applies idempotent upserts.
ContactsMatch external callers to customer and support profiles.Salesforce, HubSpot, Zendesk, IntercomMartini maps contact identifiers and phone numbers, applies normalization and matching rules, and routes ambiguous matches for review.
UsersRepresent Aircall agents and associate calls with internal owners.CRM platforms, workforce reports, collaboration systemsMartini synchronizes user identifiers and statuses where needed and uses them in routing and ownership mappings.
TeamsGroup Aircall users for routing, reporting, and operational notifications.ServiceNow, Slack, Microsoft Teams, reporting storesMartini maps Teams to downstream ownership or notification rules and caches reference data when appropriate.
NumbersIdentify Aircall phone numbers used for inbound and outbound activity.CRM, support platforms, routing tables, analytics storesMartini uses Numbers to enrich Calls, select downstream destinations, and maintain normalized reference data.
TagsClassify Calls or Contacts for reporting, routing, and operational workflows.CRM, data warehouses, notification systemsMartini translates Tags into target classifications, validates allowed values, and preserves unmapped values for review.

Authentication and security considerations

Authentication

Aircall documents HTTP Basic Authentication using an API ID as the username and an API token as the password. OAuth 2.0 is also documented for applicable application and integration scenarios, subject to account and application configuration.

Credential protection

Store Aircall credentials, OAuth configuration, and any webhook security material as protected Martini secrets rather than embedding them in workflows or logs.

Webhook validation

Validate Aircall webhook requests according to the security method configured for the webhook. Treat identifiers and status values as untrusted until the request is validated and, where necessary, the current Aircall resource is retrieved.

Privacy

Calls, voicemails, and recordings may contain sensitive personal information. Apply least-privilege access, restricted logging, encryption, retention controls, and jurisdiction-specific recording and consent policies.

Operational considerations for Aircall integrations

Rate limits and pagination

Aircall requests are subject to account and API rate limits. Process collection endpoints page by page, control concurrency, monitor HTTP 429 responses and retry headers, and avoid unbounded loops.

Idempotency

Webhook deliveries and scheduled reads can overlap. Use an Aircall Call ID, Contact ID, event identifier, or object-and-event composite key to prevent duplicate downstream writes.

Retries and reconciliation

Retry transient failures with backoff, persist failed events, and reconcile periodically through the REST API because webhook coverage is selective. Do not mark a synchronization complete after only a partial run.

Schema and matching

Tolerate optional fields, validate required values, and test mappings when Aircall payloads evolve. Normalize country codes, extensions, and phone-number formats before matching Contacts to downstream records.

Recordings

Recording references are not a general attachment API. Confirm availability, permissions, retention, URL access, consent, and whether the workflow should transfer audio or only metadata.

Why use Martini instead of scripts or point-to-point integrations?

Reusable orchestration

Martini centralizes Aircall authentication, webhook intake, paginated retrieval, enrichment, transformations, routing, and target writes in maintainable workflows rather than scattering logic across scripts.

Reliable synchronization

Checkpointing, idempotency, controlled retries, validation, and reconciliation support dependable processing when Aircall rate limits, selective event coverage, or downstream outages affect a run.

Controlled enterprise APIs

Martini can expose a stable API façade over Aircall data, allowing internal consumers to use governed contracts without handling Aircall credentials, pagination, or provider-specific payloads.

Adaptable integration design

Mappings, business rules, custom transformations, and reusable workflow assets can evolve as CRM, support, reporting, and privacy requirements change without creating multiple point-to-point implementations.

Frequently asked questions

How can Aircall be integrated with enterprise systems?

Aircall can be integrated through its REST API, paginated resource endpoints, and webhook-style notifications for selected events. Enterprise workflows can retrieve Calls, Contacts, Users, Teams, Numbers, and Tags, reconcile activity on a schedule, and deliver normalized data to CRM, support, collaboration, reporting, or storage systems.

Can Martini integrate with Aircall?

Yes. Martini can consume Aircall REST APIs, receive supported Aircall webhook notifications through an exposed API or workflow, authenticate with protected credentials, transform Aircall data, and orchestrate writes to downstream systems. No native Martini Aircall connector is documented in the supplied sources.

Do I need a connector to integrate Aircall with Martini?

No. A dedicated Aircall connector is not required. Martini can integrate using Aircall's confirmed native mechanisms, including REST APIs, selected webhook notifications, Basic Authentication, and applicable OAuth 2.0 scenarios.

Is there any extra Lonti cost to integrate Aircall with Martini?

Lonti does not charge an additional per-connector or per-vendor fee to integrate Aircall. The integration is subject to the provisioned capacity of the Martini environment. Separate costs may apply from Aircall, cloud infrastructure, storage, or other third-party systems according to their subscription, usage, and deployment terms.

Which Aircall integration methods should an enterprise use?

Use the REST API for resource retrieval, management, scheduled synchronization, and reconciliation. Use webhook-style notifications for selected events that require timely processing, but do not assume that webhooks cover every object or field. Aircall GraphQL and SOAP APIs were not confirmed.

Are Aircall events and webhooks available?

Aircall provides webhook-style notifications for selected events, including typical call creation, answering, ending, and voicemail activity, plus selected contact, user, number, and tagging events. Coverage is event-specific, so complete synchronization should combine notifications with periodic REST API reconciliation.

How does Aircall data synchronization work with Martini?

Martini can process Aircall notifications in near real time and run scheduled, paginated REST API workflows for reconciliation. Checkpoints, timestamps, or last successfully processed object identifiers can be persisted so incomplete runs resume safely and overlapping webhook and scheduled activity remains idempotent.

Can Martini expose an API façade for Aircall?

Yes. Martini can expose a controlled REST API that retrieves or normalizes Aircall data through workflows. This can provide downstream applications with a stable enterprise-facing contract while keeping Aircall authentication, pagination, mapping, and business rules inside Martini.

Related Martini documentation

API Workflows

Data Processing

Security

Reliability

Build your Aircall integration with Martini

Use Martini to connect Aircall REST APIs and selected webhook events with the systems that run your customer, support, collaboration, and reporting processes.

EXPLORE MARTINI
BOOK A DEMO