CRM & Sales · Integration
Kommo
Add Kommo to your product for your customers, and give your AI agents governed access to it.
Kommo, formerly amoCRM, serves its API from the account's own subdomain at https://{account}.kommo.com/api/v4, so kommo.com itself is not an API host and the subdomain must be captured when the customer connects. OAuth 2.0 is the supported path and the refresh token rotates on every use, so an integration that keeps reusing the original refresh token loses the connection permanently and the customer has to reauthorise. Leads sit in pipelines and statuses referenced by numeric id rather than by name, and every account renames and renumbers its own stages, so stage logic has to be resolved per tenant instead of hardcoded. Related records are not returned unless requested with the with parameter, which nests contacts, companies and catalogue elements under _embedded, and custom field values come back as arrays of field id and enum id pairs that need the account's field metadata to read. Incoming leads, the unsorted queue, are a separate resource from ordinary leads and have to be accepted or declined before they become one. fastn holds each customer's subdomain and rotating tokens, refreshes them correctly, and keeps every call attributed to the tenant.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own Kommo account so leads captured in your product land in their pipeline.
Write activity from your app back as notes and tasks on the matching lead or contact.
Read pipeline stages per account so your UI shows the customer's real stage names rather than generic ones.
Keep contact and company records in step both ways, including their custom field values.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent which leads have sat in a stage longest, with the read audited per tenant.
Let an agent create a follow-up task on a lead while stage changes remain with a human.
Have an agent summarise the notes on an account before a call, scoped to that tenant's subdomain.
Example prompt
Which deals in our Kommo pipeline have had no activity in the last two weeks?
Set up Kommo in 4 steps
- 01Enable the Kommo connector from your fastn dashboard.
- 02Have each customer authorise their own Kommo account, so calls run under their credentials rather than a shared key.
- 03Decide which accounts, contacts and opportunities your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the Kommo integration
What you get by embedding it with fastn instead of building it yourself.
- Ship a Kommo integration without building it. Your customers connect their own Kommo account inside your product and work their accounts, contacts and opportunities there, with no per-customer code on your side.
- Handle the part that actually costs time: every CRM instance is customised, so standard objects are never the whole story. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so a Kommo update is not your on-call problem.
- One integration serves your product and your agents. The same governed Kommo connection powers in-product features and gives AI agents scoped, audited access, so you keep customer records aligned between your product and the CRM each customer already runs without wiring it twice.
Used by these teams
Compare with
Salesforce
HubSpot
PipedriveOften used alongside
Tools the same teams tend to run next to Kommo, across other categories.
Slack
Mailchimp
Marketo
Google AdsKommo integration FAQ
How do I add a Kommo integration to my product?
Enable the Kommo connector in your fastn dashboard, then let each customer authenticate their own Kommo account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Kommo client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Kommo account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Kommo account and only ever sees their own accounts, contacts and opportunities. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Kommo integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent which leads have sat in a stage longest, with the read audited per tenant.
Who maintains the Kommo integration?
fastn does. When Kommo changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Does the Kommo integration support custom fields and custom objects?
Yes. CRM instances are heavily customised, so field and object mapping is configuration rather than code. Each customer maps their own fields during setup, which means onboarding a customer with an unusual Kommo schema does not require a deploy on your side.
Can records sync both ways?
Yes. You can read from Kommo, write back to it, and react to changes through triggers, so a record updated in your product and a record updated in Kommo do not drift apart.
What can I build with the Kommo integration?
A common starting point: let a customer connect their own Kommo account so leads captured in your product land in their pipeline. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Kommo integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Kommo does not change your per-connector cost. You can start free with 3 connected accounts.
Add Kommo to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.