AlloKommo logo

Kommo phone integration

Kommo logs calls as notes and matches callers on the last 8 digits, or the last 7, depending on which endpoint you use. Here is how Allo handles that.

How it connects

Allo connects to Kommo through Zapier today.

Licensed operator

Registered telecom operator in France (ARCEP).

Its own network

Allo runs its own VoIP infrastructure, not resold.

GDPR compliant

Your call data stays yours, handled to GDPR.

In the Claude directory

Allo's MCP server is in the Claude connectors directory.

Endpoints

Connect Allo to Kommo

Because Kommo has a public API, Allo connects over that API and webhooks. These are the API surfaces you point at Kommo: a small, focused REST API, JSON in and JSON out, with webhooks for real-time events.

CallsREAD

Search your call history. Every record includes transcripts, AI summaries, recording URLs, IVR selections and transfer chains.

GET/v1/api/calls
ContactsREAD & WRITE

Full CRUD on your contact database. Create, fetch by ID, update and search, with engagement data baked into every response.

GET/v1/api/contacts
POST/v1/api/contacts
PUT/v1/api/contacts/:id
SMSSEND

Send SMS programmatically from any of your Allo numbers. Dedicated endpoints for US and France, both in E.164 format.

POST/v1/api/sms
POST/v1/api/sms/fr
WebhooksREAL-TIME

Subscribe a URL to call, SMS and contact events. Full envelope payloads, no secondary fetch to enrich the data.

GET/v1/api/webhooks
POST/v1/api/webhooks
DEL/v1/api/webhooks/:id
ConversationsREAD

Pull the whole thread for a contact: calls and SMS stitched together, in order, with pagination built in from day one.

GET/v1/api/conversations
Phone NumbersREAD

List every Allo number on your account. Use it to route, filter or match a number to an owner without hardcoding.

GET/v1/api/phone-numbers

Native or Zapier

The honest version: here is exactly how the connection is made today, and what is not built yet.

Native Allo integration

Not built yet for Kommo

Zapier

11 triggers, 12 actions published

Allo and Kommo, answered

Not a standalone one. Calls are logged as notes and events on the entity card through POST /api/v4/calls. The endpoint does the phone matching and the attaching in the same request.

The call record is still created, but it is linked to nothing. Kommo's docs are explicit about this. If you want the call to be visible you have to create an incoming lead for that number yourself, which is what Allo does.

Because Kommo has two lookups with different rules. The Call event uses the last 8 digits and prefers contacts. Get contacts by phone uses the last 7 digits and prefers companies. Pick one path and use it everywhere, or you will get inconsistent attribution.

No. Kommo matches on trailing digits, so the country prefix is effectively ignored. That is convenient for matching and risky for anything else, because two numbers in different countries can share the last 8 digits.

Seven requests per second, enforced per IP address. Repeated violations return 403 for that IP rather than 429, so a badly behaved backfill can lock out everything else running from the same host.

Yes. Refresh tokens last three months, and an integration that goes unused for that long loses access and needs reauthorising. Low volume accounts are the ones that get caught.

Request a formal Kommo integration

Tell us about your team and we'll build the Kommo integration and get you early access. The more teams that ask, the sooner it ships.

  • Native calling, texting and AI call notes inside Kommo
  • Every call logged to the right record, automatically
  • We build it for your team and give you early access

Prefer to talk it through? Book a call