Skip to main content
OpenCX workflows authenticate to Aircall with an — an API ID and an API token used together. Both travel into the workflow action as inputs — there is no org-level connect screen today.

​
Generate credentials

1

Open the Aircall API keys page

Sign in to your Aircall dashboard as an admin and open Integrations → API Keys.
2

Create an API key

Click Add an API key. Aircall shows you two values: the API ID and the API token.
Anyone with the pair can read and write your Aircall data — calls, contacts, users. Treat it like a password, and note that Aircall shows the token only once at creation time.
3

Store both somewhere safe

Drop both into your password manager or secret store. Every workflow node that touches Aircall expects them as inputs, so you will reuse them across flows.
OpenCX does not persist Aircall credentials at the organization level yet. Each workflow action reads the API ID and token from its own configuration — rotating the key means updating every workflow that uses it.

​
Verify the connection

Aircall exposes a ping endpoint that answers with {"ping": "pong"} when the credentials are valid: 
curl https://YOUR_API_ID:[email protected]/v1/ping
A 403 Forbidden response means the ID/token pair is wrong or was revoked — regenerate the key from the API Keys page.

Post Call Context Action

Full reference for the workflow action.

Overview

What the Aircall integration does at a glance.

Troubleshooting

Credentials rejected, call not found, comment limits.

AI Phone agent configuration

Set up the transfer destination that forwards to Aircall.