Skip to content
CRM ⇄ Analytics

Kommo to Microsoft Power Bi integration — real-time data sync

Keep Kommo and Microsoft Power Bi in sync without custom scripts. Cut weeks of integration work, eliminate silent data drift, and give your team a single, reliable source of truth.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes

Adopted by fast-scaling companies moving mission-critical data in real time

Case study
Migrated from MuleSoft
Case study
Migrated from Celigo
Migrated from Heroku Connect
Migrated from Matillion
Case study
Migrated from Fivetran
Case study
Migrated from Celigo
Why teams connect Kommo and Microsoft Power Bi

Put live Kommo data behind every dashboard and cohort in Microsoft Power Bi, and write the segments and scores Microsoft Power Bi computes back onto the Kommo record — one connection, not a nightly export.

Microsoft Power Bi is a read-only source: Stacksync reads its data in real time and delivers it into Kommo, so Kommo always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.

Microsoft Power Bi turns data into dashboards, cohorts, and metrics; Kommo is where customers, contacts, deals, and activity actually live and change. The two meet wherever a number is really about a specific account, segment, or stage — yet most teams feed the CRM into analytics as a nightly extract or a hand-maintained connector, so the reporting lags the business and can't be sliced by the customers and segments that matter.

Stacksync syncs Notes, Custom Fields, Users, Chats from Kommo into Microsoft Power Bi field by field and within seconds, so every dashboard and cohort runs on current records instead of a stale copy. Because the connection runs both ways, the cohorts, scores, and metrics computed in Microsoft Power Bi write back to fields in Kommo, landing where the people working accounts can see them. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • 01 Read Users and workspace access for periodic access reviews reconciled against an HR or Microsoft Entra ID source of record.
  • 02 Mirror Workspaces, Reports, Dashboards, and Dataset metadata into a catalog database so teams discover Power BI content from a central index.
  • 03 Keep customer records consistent between Kommo and invoicing or ERP systems
  • 04 Mirror pipeline stage changes into BI tools for forecasting

Common sync patterns

Report on live CRM data

New records and status changes in Kommo appear in Microsoft Power Bi within seconds, so dashboards and cohorts track the current pipeline rather than last night's export.

Where Kommo accepts updates: segments and scores back on the record

Cohorts, scores, and computed metrics from Microsoft Power Bi sync onto fields in Kommo, putting the analysis where reps and owners actually work the accounts.

One customer across analytics and CRM

The same account or person is keyed consistently in both systems, so a profile or row in Microsoft Power Bi lines up with the contact or account in Kommo.

What you can sync between Kommo and Microsoft Power Bi

Representative objects on each side — any object or custom field can map to any target. Schemas are auto-detected; types are converted between the two systems.

Kommo objects Microsoft Power Bi objects How this pairing syncs
Notes Free-text and system notes attach context to synced leads and contacts. Dashboards and Tiles Dashboards and their pinned tiles read via GET /dashboards and /dashboards/{id}/tiles; inventoried to map dashboard content back to its source datasets. Notes is specific to Kommo and Dashboards and Tiles to Microsoft Power Bi — each maps to any object or custom field on the other side.
Custom Fields Per-entity custom fields hold data written from external databases and enrichment. Dataflows Power Query ETL definitions read via GET /groups/{id}/dataflows; used to document lineage from upstream sources into datasets. Custom Fields is specific to Kommo and Dataflows to Microsoft Power Bi — each maps to any object or custom field on the other side.
Users Account users map lead ownership to people in other systems. Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Users is specific to Kommo and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side.
Chats Messenger conversations from WhatsApp, Instagram, and other channels attach to leads and contacts. Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. Chats is specific to Kommo and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side.
Leads The central pipeline record; external signups and form fills sync in as leads. Workspaces (Groups) Containers for content read via GET /groups (tenant-wide via GET /admin/groups); mirrored to reproduce the tenant's content hierarchy in a catalog. Leads is specific to Kommo and Workspaces (Groups) to Microsoft Power Bi — each maps to any object or custom field on the other side.
Contacts Person records sync with other CRMs and databases for a shared contact file. Activity Events (Audit Log) Admin audit log of user and content actions read via GET /admin/activityevents; loaded for security, access, and usage reporting across the tenant. Contacts is specific to Kommo and Activity Events (Audit Log) to Microsoft Power Bi — each maps to any object or custom field on the other side.

How changes propagate between Kommo and Microsoft Power Bi

Each direction of the sync is driven by what the source system can signal and what the destination accepts — detection, delivery, and expected latency below.

Kommo Microsoft Power Bi Sub-second propagation

DetectionKommo notifies Stacksync of record changes through webhook events. Webhooks on record add and update events, plus polling for backfill.

DeliveryMicrosoft Power Bi does not accept inbound record writes, so this direction carries requests rather than records: Microsoft Power Bi's output flows back as field updates on the originating Kommo records.

Microsoft Power Bi Kommo Interval-based propagation

DetectionStacksync polls Microsoft Power Bi for changes on an incremental schedule, reading only records changed since the previous pass. Pull-based: no webhooks or change-data-capture.

DeliveryEach detected change is written to Kommo through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Kommo: Subject to per-account request rate limits.
  • Microsoft Power Bi: Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
What ships with Kommo ⇄ Microsoft Power Bi

Connect Kommo and Microsoft Power Bi for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Kommo–Microsoft Power Bi connection.

Real-time

Real-time sync

Changes in Kommo or Microsoft Power Bi instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Kommo or Microsoft Power Bi data changes, update records, fire webhooks, or kick off sequences without brittle API scripts.

At scale

Event queues

Handle millions of events per minute without losing a single Kommo or Microsoft Power Bi record.

Observability

Monitoring

Track your Kommo ⇄ Microsoft Power Bi sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Kommo and Microsoft Power Bi.

How the Kommo and Microsoft Power Bi connectors work

Kommo

Integration surface
REST API
Authentication
OAuth 2.0 with refresh tokens
Change detection
Webhooks on record add and update events, plus polling for backfill
Capabilities
read · write · webhooks
Rate limits
Subject to per-account request rate limits

Microsoft Power Bi

Integration surface
Power BI REST API, including the Execute Queries (DAX) endpoint and admin scanner APIs; a read-write XMLA endpoint is available on Premium, Premium-Per-User, and Fabric capacity.
Authentication
Microsoft Entra ID (Azure AD) OAuth 2.0 bearer tokens. Supports delegated user tokens and app-only service principals; service principals must be enabled under the tenant's Developer settings and granted workspace access. Tenant-wide admin reads require the Tenant.Read.All scope.
Change detection
Pull-based: no webhooks or change-data-capture. Content is polled via REST list endpoints, dataset changes are inferred from Refresh History and the admin Activity Events audit log, and the scanner API's GetModifiedWorkspaces reports workspaces changed since a given time.
Capabilities
read
Rate limits
Endpoints throttle per user and per app and return HTTP 429 with a Retry-After header. Execute Queries allows up to 120 requests per minute per user and caps a query at 100,000 rows (or 1,000,000 values) and 15 MB; admin scanner metadata APIs are limited to about 500 requests per hour with 16 concurrent.
How it works

How to connect Kommo to Microsoft Power Bi — three steps, no code

Configure and sync within minutes, no code. Whether you sync 50k or 100M+ records, Stacksync handles the queues, infra, and plumbing. Integrations are non-invasive and need zero setup on your systems.

  1. 01

    Connect your apps

    Authenticate Kommo and Microsoft Power Bi with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.

    • OAuth 2.0
    • SSH tunnel
    • VPC peering
    Kommo connected
    Microsoft Power Bi connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Kommo and Microsoft Power Bi objects to sync — Stacksync auto-detects both schemas, including custom fields where the platform exposes them. Sync to existing tables, or let Stacksync create new ones with ideal data types.

    • Standard objects
    • Custom objects
    • Auto-schema
    objects · Kommo ⇄ Microsoft Power Bi
    Customers 12,480
    Sales Orders 8,213
    Invoices 5,902
    Items 1,344
  3. 03

    Map fields

    Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.

    • Auto-map
    • Type casting
    • Transforms
    Kommo Microsoft Power Bi
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Kommo and Microsoft Power Bi integration FAQ

SECURITY

Security teams trust Stacksync

As a data company, we understand the importance of keeping your data secure. Stacksync is built with security best practices to keep your data safe at every layer, and is DPF-certified for US, EU, UK and CH data transfers.

Learn more about security
SOC 2 Type II
ISO 27001
HIPAA BAA
GDPR
CCPA
DPF US-EU-UK-CH
→ SECURITY WITH BENEFITS

SSO & SCIM

Let your users access Stacksync from your centralized user management systems. Works with Okta, Azure, Google SSO and more.

Alerts

Immediately get alerted about record syncing issues over email, Slack, PagerDuty and WhatsApp. Resolve issues from a centralized dashboard with retry and revert options.

Secure connection options

Securely connects to your systems with:

OAuth 2 SSH Tunnelling SSL certificates IP Whitelisting VPN gateway VPC peering and more

Related integrations

Every pair below is a real-time, two-way sync. Search all 450 integrations available for Kommo and Microsoft Power Bi.

Popular · 8 of 450
All Kommo integrations All Microsoft Power Bi integrations Browse all integrations
Coworkers laughing in front of a laptop in a casual office setting

Your last integration took months.
Your next one takes a prompt.

Book a demo Tour the platform on your own