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.