Aircall + monday.com integration not working? Every error, fixed

This is the failure we see most, and Aircall's own prerequisites page confirms why: the install needs the Admin role in your monday.com account, or in the specific monday product you're installing into if you run more than one (Work Management and CRM count separately, and you need admin on each)¹.

Admin alone isn't enough. Board-creation permission has to be enabled in two places: at the account level (Administration, then Permissions, then the Admin role's Boards section, confirm "Create boards" is on) and at the workspace level (the target workspace's own Permissions tab)¹. The integration auto-creates its logging boards during install, so if it can't create boards, it can't install.

One more trap for multi-product accounts: an installed but unused monday product (commonly Work Management) can create permission complications during install. Aircall's docs note you can remove unused products under Administrator, then Billing, then Overview¹. And make sure the marketplace app itself ("Aircall: Call & SMS in your work OS") is on its latest version via Administration, then Apps¹.

If the error persists after all of that, use Aircall's documented workaround, which is the clean reinstall sequence in section 07¹.

There are two generations of this integration, and both sets of instructions are still on the internet. The legacy V1 flow worked through an "Aircall Calls" board template⁴. The current V2 integration works through the monday.com marketplace app "Aircall: Call & SMS in your work OS" plus a connection made from the Aircall Dashboard^2,5, and it's where the modern features live: SMS and WhatsApp logging, AI insights, insight cards, contact sync, and tag automations².

The tell: if your instructions talk about a board template, you're reading V1 docs. If they talk about the marketplace app and the Aircall Dashboard's "monday.com V2" entry, you're in the right place. Mixing the two flows is a reliable way to end up with a half-installed integration. Aircall publishes an upgrade guide for moving from V1 to V2³; our full setup guide walks the V2 path end to end.

The number one cause is the number-linking requirement: at least one Aircall number must be linked to the integration for any call or message activity to log². An install with zero linked numbers completes without complaint and then logs nothing. Number assignments can be updated anytime in the Aircall Dashboard.

For missing texts specifically: message logging for SMS and WhatsApp is disabled by default (call logging is enabled by default)². Flip the message logging toggle in the integration settings and texts will start landing on the Aircall Messages board.

Also verify the boards exist: a completed install auto-creates "Aircall Calls" and "Aircall Messages" boards suffixed with an integration ID². No boards means the install never finished, which usually points back to permissions.

This one generates support tickets that aren't bugs. Aircall documents the sync timing plainly: updates made in monday.com reflect in Aircall following the next call or message with that number². Edit a contact at 9am and the change shows up in Aircall when that contact next calls or texts, not at 9:01. Set that expectation with your team and this "failure" disappears.

If contacts aren't syncing at all, check the configuration instead: the contact or lead board must be linked in the integration settings with the name column and up to three phone columns mapped, and only Public and Shared boards appear in the picker, so a Private CRM board can't be linked until you change its visibility². One more tell: contacts arriving named "Aircall New Contact" means no contact board is configured, so Aircall is creating placeholders².