Why can't my n8n agent send replies to Kommo chats?

An n8n agent can read and write Kommo CRM data (leads, contacts, fields), but sending a message into a chat goes through a different system — amojo, Kommo's chat transport. Posting to amojo requires a registered channel (a scope_id plus a secret key), and Kommo's official n8n integration covers CRM data only, not chat messaging. Without a registered channel your reply never reaches WhatsApp, Instagram or Telegram.

What is amojo, a registered channel, and a scope_id?

amojo is Kommo's chat-message transport. To post a message you call amojo.kommo.com/v2/origin/custom/{scope_id} with an X-Signature header (SHA1 of the request body signed with the channel secret). You only obtain a scope_id and secret after registering a chat channel with Kommo.

Does AnyLinga generate the AI replies?

No. AnyLinga Connect is the transport and bridge with a registered channel — your own n8n, OpenAI or custom agent generates the replies, using your model and your prompts. AnyLinga can optionally translate the customer's message and your agent's reply in the same pipeline.

AnyLinga Connect — Connect your own AI agent to Kommo chats

Q: Do I need to register a Kommo chat channel myself?

No. Channel registration is now handled through a request to Kommo technical support (a 1–3 business-day review) — it is no longer self-serve. AnyLinga already holds a registered amojo channel, so with AnyLinga Connect you plug in your own AI agent without running the registration gauntlet yourself.

Q: Which AI agents can I connect?

Any HTTP-reachable agent — an n8n workflow, an OpenAI Assistant, or your own custom backend. AnyLinga POSTs the inbound message to your webhook and sends the reply_text you return back into the Kommo chat through its registered amojo channel. Your model, prompts and tools stay yours; optional translation runs in the same pipe.

Q: What Kommo plan do I need for AnyLinga Connect?

A Kommo Advanced plan or higher — that tier unlocks the custom widget and WebSDK that AnyLinga Connect uses inside the Salesbot flow (Free and Basic plans don't expose them). AnyLinga itself costs $21 per connected channel per month, on top of your Kommo subscription.

The problem

Your n8n agent reads the lead — but the reply never reaches the chat

An n8n agent can read and update Kommo CRM data all day — leads, contacts, custom fields. But sending a message into a chat is a different system: it has to go through amojo, Kommo's chat transport. And posting to amojo requires a registered channel (a scope_id + secret) — which is now gated behind a Kommo support request, no longer self-serve.

That's why public “connect AI to Kommo” n8n templates read data fine but for new builders the reply send fails with an error: they assume a channel you can no longer just create. Most DIY setups stall right here.

In short: An n8n agent reads Kommo CRM data, but sending a chat reply must go through amojo — Kommo's chat transport — which needs a registered channel (scope_id + secret) obtained via a support request. AnyLinga already holds a registered amojo channel, so your own agent can reply without registering one.

Read the full explanation (with Kommo's own docs)

How AnyLinga Connect works

Your AI does the thinking. Our registered channel does the chat-facing part.

Your n8n never touches Kommo or amojo — AnyLinga's registered channel does the chat-facing part.

1

Install the widget

Add AnyLinga from the Kommo Marketplace (Advanced plan+). One-click OAuth, no channel registration on your side.

2

Connect Kommo & your messengers

Make sure your Kommo account is connected and add the messenger(s) (WhatsApp/IG/TG) customers use, then paste your n8n webhook URL + secret, pick sync or async, optionally enable translation.

3

Build n8n from the template

Start from the AnyLinga Connect n8n template: webhook in → your agent → reply out. Test with a real WhatsApp message — the reply lands.

The gateway contract

n8n only does “receive → think → return text.” It never registers a channel, never calls amojo.

AnyLinga → your n8n

message_text, translated_text?, lead_id / contact_id, lang, conversation_id, correlation_id, callback_url (HMAC-signed)

your n8n → AnyLinga

reply_text, handoff_to_human?, set_status? — sync (Respond to Webhook) or async (callback)

Start trial

A compliant bridge, not another AI bot

AnyLinga is the transport. The intelligence stays yours.

Bring your own AI

n8n, OpenAI, or any custom HTTP-reachable agent. Your model, your prompts, your tools — AnyLinga never decides what to say.

Pre-registered amojo channel

No support-request gauntlet, no scope_id to manage. AnyLinga holds a registered channel so your replies actually reach the chat.

Translation in the same pipe

Optional: translate the customer's message for your agent and translate the reply back — 50+ languages, no extra integration.

Sync & async

Fast-path (Respond to Webhook) for light agents; async callback for heavy ones. Works inside Kommo's reply window.

Multi-channel

WhatsApp, Instagram, Telegram, Facebook and more — every channel connected to Kommo flows through one bridge.

Compliant by design

The sanctioned Salesbot + registered-channel route. AnyLinga is a transport, not an autonomous bot — clean with Kommo's terms.

Simple, transparent pricing

7-day free trial on every plan. No credit card required.

Requires a Kommo Advanced plan or higher (custom widget / WebSDK)

Channel connections

$21 per channel / month

Registered amojo channel
Bring your own AI (webhook)
All messaging channels
3,000 translations a month with the first channel, +1,000 for each extra one
Unlimited employees
Sync & async modes, 30-day logs

Start trial

A channel = one connection: a WhatsApp number, a Telegram bot, an Instagram account. Employees do not change the price. Need more translations? Add a bonus pack: 2,000 for $15, 10,000 for $60, 50,000 for $250.

Questions builders actually ask

The amojo gate, the bridge, and what stays in your hands.

An n8n agent can read and write Kommo CRM data, but sending a message into a chat goes through a different system — amojo, Kommo's chat transport. Posting to amojo needs a registered channel (a scope_id + secret), and Kommo's official n8n integration covers CRM data only, not chat messaging. Without a registered channel, your reply never leaves n8n. Full explanation →

amojo is Kommo's chat-message transport. To post a message you call amojo.kommo.com/v2/origin/custom/{scope_id} with an X-Signature header (SHA1 of the body, signed with the channel secret). You only get a scope_id + secret after registering a chat channel with Kommo.

No. Channel registration now goes through a request to Kommo technical support (a 1–3 business-day review) — it's no longer self-serve. AnyLinga already holds a registered amojo channel, so you plug in your own agent without running that gauntlet.

No. AnyLinga Connect is the transport and bridge with a registered channel. Your own agent generates the replies — your model, your prompts, your tools. AnyLinga can optionally translate the customer's message and your reply in the same pipe.

Any HTTP-reachable agent — an n8n workflow, an OpenAI Assistant, or your own custom backend. AnyLinga POSTs the inbound message to your webhook and sends the reply_text you return back into the Kommo chat through its registered amojo channel. Your model, prompts and tools stay yours; optional translation runs in the same pipe.

A Kommo Advanced plan or higher — that tier unlocks the custom widget and WebSDK that AnyLinga Connect uses inside the Salesbot flow (Free and Basic plans don't expose them). AnyLinga itself costs $21 per connected channel per month, on top of your Kommo subscription.

Plug your AI into Kommo chats — the compliant way

Skip the amojo registration gauntlet. Start your 7-day free trial — no credit card required.

Start trial Read why DIY breaks

Connect your own AI agent to Kommo chats — AnyLinga Connect