Conversational CRM
Import leads, deals, and closed revenue from Kommo
Connect via Kommo CRM API v4 long-lived token. Incremental sync for pipelines, stage progression, and status change events.
What this integration connects
Direct communication with Kommo CRM API v4 via long-lived token.
- ✓Leads and deals across all active pipelines in your Kommo account
- ✓Stage progression event history (lead_status_changed)
- ✓Deal owners and monetary transaction values
- ✓Attached contacts with email and phone for deterministic matching
What you see in Ollie
Your Kommo sales pipeline powered by multi-touch digital attribution.
Mapped funnels and pipelines
Complete Kommo pipeline structure mirrored in Ollie with stage-to-stage conversion metrics.
Attributed ad revenue
Won leads in Kommo register verified revenue attributed to the exact campaign that opened the conversation.
Status change event history
Captures the exact historical timestamp when each lead progressed through the sales funnel.
Compliant rate limiting
Batched synchronization adhering to Kommo strict 7 requests/second rate limit.
How to connect in 3 simple steps
No complex engineering required. Authorize and map your data within minutes.
Generate a long-lived token in Kommo
Under Kommo › Settings › Integrations, create a private integration and copy your long-lived token.
Provide token and account subdomain
Enter your account subdomain (e.g., yourcompany.kommo.com) and access token in Ollie.
Map sales pipelines
Select which Kommo pipelines feed into your marketing customer funnel stages.
Honest limits: what this integration does NOT do
Clear operational boundaries for Kommo CRM.
- Leads and deals across all active pipelines in your Kommo account
- Synchronized incrementally and safely into your Ollie tenant.
- Stage progression event history (lead_status_changed)
- Synchronized incrementally and safely into your Ollie tenant.
- Deal owners and monetary transaction values
- Synchronized incrementally and safely into your Ollie tenant.
- Attached contacts with email and phone for deterministic matching
- Synchronized incrementally and safely into your Ollie tenant.
- Strictly read-only connection
- Ollie does not send chat messages, modify lead stages, or alter contact records in Kommo.
- Adheres to 7 req/sec API throttle
- Kommo enforces strict rate limits; large initial syncs run across batched intervals to prevent 429 errors.
- Requires exact account subdomain
- API routing requires your precise Kommo tenant subdomain for secure endpoint dispatch.
- Leads without contact keys are skipped
- To avoid fabricated identities, Ollie only attributes deals containing valid email or phone keys.
Frequently asked questions
Direct answers to operator questions regarding permissions, security, and data handling.
Where do I create a long-lived token in Kommo?
Inside Kommo Settings › Integrations, set up a private integration and generate the permanent access token.
Does Ollie send chat replies or messages in Kommo?
No. The connector only reads deal progression and contact keys for revenue attribution.
How does Ollie handle high lead volume in Kommo?
We paginate in batches of up to 250 records, pacing calls to stay well within Kommo API limits.
Connect Kommo CRM directly to ad performance
Identify which campaigns deliver the highest-closing leads in your Kommo pipeline.