Aircall

Aircall

Aircall is a cloud call center. Calls, contacts, and numbers are core; teams and users map to agents; webhooks push events.

Data Model

• Calls are call records. Fetch newest calls with descending order first, then drill into a specific call by id before summarizing or mutating it.
• Contacts are people/companies. Search by phone or email before creating a new contact, then update the existing contact when one matches.
• Company is the connected Aircall account singleton.
• Numbers are phone numbers. Review numbers before outbound-call or number-update actions.
• Teams and Users represent agents and routing groups. Review users and teams before membership changes.
• Tags categorize calls. Review available tags before tagging a call.
• Webhooks register callback URLs for event push from Aircall.

Gotchas

• Company record: The company read returns a singleton payload (your tenant), not a paginated collection.
• Combined reads: Aircall read tools use the get pattern. Omit the optional id to list; pass the id to retrieve one record.
• Create/update naming: Contact creation uses the contact upsert tool. There is no separate create-contact tool.
• Contact update split: Aircall updates contact name/company fields on /contacts/:id, but phone and email details use separate tools.
• User creation invites: Creating a user sends an Aircall invitation email.
• Call write actions: Calls are not directly upserted. Use comments, tags, archive/unarchive, and outbound-call actions for write workflows.
• Conversation Intelligence API access: Enrichment tools (transcription, summary, topics, sentiments, action items, playbook results, evaluations) require an Aircall admin API credential on an account with Conversation Intelligence enabled. A 403 Forbidden on those endpoints means the bound API key lacks CI access or the plan does not include the feature — create a new admin API key in Aircall (Integrations → API keys) or upgrade the Aircall plan; reconnecting the same key will not help.