Kommo
Manage Kommo leads, contacts and companies — the messenger-based sales CRM formerly known as amoCRM.
About
Kommo ships in the w6w first-party pack. It declares 12 actions, 2 health checks, and the host runs its code in a sandbox that never sees the credential.
- App id
io.w6w.kommo- Version
- 0.1.0
- Author
- w6w
- Licence
- MIT
- Categories
- Customer Relationship Management · Marketing
Overview
Kommo (rebranded from amoCRM in 2024) is a messenger-based sales CRM built around leads moving through a pipeline. This app puts the daily loop of running that pipeline behind a workflow: create and update leads, contacts and companies, and read them back by id or by a filtered, paginated list.
Every account gets its own address — <subdomain>.kommo.com, or <subdomain>.amocrm.com for accounts that predate the rebrand and never moved — so the account address is a connection field rather than a fixed host, the same posture this pack already uses for Zendesk.
Authentication is a Long-Lived Token, generated once from Settings -> API in the target account (Kommo’s own docs recommend it specifically for a private, single-account integration like a workflow, over the OAuth2 authorization-code flow that exists for public marketplace integrations). It carries the creating admin’s own rights, needs no redirect URL and no refresh cycle, and can be scoped to an expiry between 1 day and 5 years at generation time.
Deliberately out of scope: deleting a lead, contact or company (the v4 API documents no delete endpoint for any of the three — removal only happens from Kommo’s own UI, to trash, which the API cannot reach either), the pipeline/stage/custom-field administration surface, tasks, notes, tags administration, the Chats API, the Salesbot builder, and the catalogs/lists feature. Each is its own surface, and none of it is the record CRUD a workflow touches day to day.
Build with Kommo
Three routes to the same 12 actions. The Workflow tab is generated from Kommo's own manifest and carries its real ids, so it is copy-pasteable; the Code and CLI examples are the same call for any action on any app, so every app-specific value in them is a blank you fill in.
Create a Company
company-create Create a new company. Two calls with the same fields create two companies.
Update a Company
company-update Update fields on an existing company. Only the fields you set are changed.
Create a Contact
contact-create Create a new contact. Two calls with the same fields create two contacts.
Update a Contact
contact-update Update fields on an existing contact. Only the fields you set are changed.
A workflow step names the app and the action, and the editor fills in the
connection when you pick one. This is the Step shape from the
workflow spec, carrying Kommo's real ids.
{
"manifestVersion": "2",
"name": "kommo-example",
"steps": [
{
"id": "company-get",
"uses": {
"app": "io.w6w.kommo",
"action": "company-get",
"connection": "conn_YOUR_CONNECTION_ID"
},
"with": {
"id": "<id>"
}
}
]
}Here are some of the things you can do
-
Get a Company
readcompany-get -
Create a Company
performcompany-create -
List Companies
searchcompany-list -
Update a Company
performcompany-update -
Create a Contact
performcontact-create
+7 more actions available
Every app-specific value here is a blank you have to fill in. An
app action is reached through the connection that authenticates it, so the
address is a connection id, not the app id — and connections belong to your account,
so a public page cannot know yours. Create one for Kommo, then fill in
the three blanks: conn_YOUR_CONNECTION_ID, the action key, and the
parameters that action declares. The call itself is real — the shape is transcribed
from the studio's own snippet builder, which prints the same kind of blanks — but
nothing in it is specific to Kommo. The Workflow tab is where this app's
real ids are.
npm install @w6w/sdkyarn add @w6w/sdkpnpm add @w6w/sdkdeno add npm:@w6w/sdkimport { W6wClient, isActionRun } from "@w6w/sdk";
// Reads W6W_BASE_URL and W6W_TOKEN from the environment when omitted.
const client = new W6wClient();
const envelope = await client.run({
urn: "conn_YOUR_CONNECTION_ID",
action: "company-get",
payload: {
id: "<value>",
// withEmbed: "<value>",
},
});
if (isActionRun(envelope)) console.log(envelope.value);npm install -g @w6w/cliw6w run conn_YOUR_CONNECTION_ID --action company-get --payload '{"id":"<value>"}'Give an AI agent Kommo — without giving it Kommo's credentials. One MCP endpoint exposes every app, function and workflow the caller is entitled to, as tools it can discover and run. Access is granted per team while we onboard.
One tool call{
"name": "w6w_invoke",
"arguments": {
"ref": "app:io.w6w.kommo#company-get",
"input": {
"id": "<id>"
}
}
}
Every tool names its target with a single ref. The
app: form above doesn't name a connection at all — the
host resolves which of the caller's Kommo connections to sign
with, and refuses rather than guesses when the answer is ambiguous.
What the agent gets
Credentials it can't read
The token is attached host-side, at the moment of the call. It is never a tool argument, never in the model's context, and never in a transcript — so a prompt injection has nothing to exfiltrate.
A tool surface scoped to the caller
Tools are derived per end user from what that person has actually connected and is entitled to — not one shared bot identity carrying the union of everyone's access.
A durable workflow in one call
Multi-step work runs on the workflow engine and returns a run handle the agent can poll — retries, branching and state survive the conversation that started them.
Health-aware discovery
Kommo's declared health checks are on the surface too, so an agent can tell "the vendor is down" from "your credential expired" before it burns a retry on either.
The MCP surface is part of the hosted platform. Kommo itself is MIT, and the runtime that executes it is source-available (FSL).
Health checks
Kommo declares its own checks, so its health is a property of the app rather than something the host guesses at.
Account address reachable
Unauthenticated request to this connection's own Kommo account. A structured 401 passes — it proves the account is serving; credential validity is the auth:* check's job.