Skip to main content
OpenCX workflows authenticate to Aircall with an — an API ID and an API token used together as HTTP Basic auth. Store the pair as organization variables once, then reference them from every workflow node that touches Aircall.

​
Generate credentials

1

Open the Aircall API keys page

Sign in to your Aircall dashboard as an admin, open the Integrations & API page, and select API Keys in the upper-right corner.
2

Create an API key

Click Generate an API key, give the key a recognizable name, and 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. Copy both values before closing the popup: the API token is displayed only once at creation time and cannot be retrieved later.
3

Store both somewhere safe

Drop both into your password manager or secret store, then add them as OpenCX organization variables (next section) so workflows can reference them.

​
Store as organization variables

Instead of pasting the raw credentials into every workflow node, store them once as organization variables — values are encrypted at rest and decrypted per run:
1

Open the variables page

Go to Settings → Variables.
2

Add two variables

Create aircall_api_id with the API ID as its value, and aircall_api_token with the API token.
3

Reference them from workflows

In any workflow node with Aircall credential inputs (e.g. Post Call Context), set Aircall API ID to {{variables.aircall_api_id}} and Aircall API Token to {{variables.aircall_api_token}}.
Rotating the key becomes a one-place change: generate a new key in Aircall, update the two variable values, and every workflow referencing them picks up the new credentials on its next run — no workflow edits needed.
Organization variables are shared with AI action calls, where each key/value is sent as an HTTP header on outbound requests to your own action endpoints. Keep that in mind when naming and scoping the keys.

​
Verify the connection

Aircall exposes a ping endpoint that answers with {"ping": "pong"} when the credentials are valid. Aircall recommends sending the pair Base64-encoded in the Authorization header (not embedded in the URL):
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.