Skip to content
CRM ⇄ Analytics

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

Keep Clari 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 Clari and Microsoft Power Bi

Put live Clari data behind every dashboard and cohort in Microsoft Power Bi, and write the segments and scores Microsoft Power Bi computes back onto the Clari 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 Clari, so Clari always reflects the current state of Microsoft Power Bi — without exports, scripts, or schedulers.

Microsoft Power Bi turns data into dashboards, cohorts, and metrics; Clari 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 Forecast, Quota, Opportunities, Activity (Capture) from Clari 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 Clari, 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 Write warehouse-computed health scores and usage metrics onto Clari Opportunity records as field extensions via the ingest API so deal reviews show product signals.
  • 04 Enrich Clari Account records with firmographic or billing data points through the ingest API in incremental mode.

Common sync patterns

A record that outlives edits in the CRM

A continuously synced copy of Clari's records and activity in Microsoft Power Bi keeps a queryable history even as records change or age out of the CRM.

Customer context in Microsoft Power Bi

Accounts, contacts, deals, and activity from Clari sync into Microsoft Power Bi, so metrics and dashboards group by real customers, segments, and stage instead of anonymous IDs.

Report on live CRM data

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

What you can sync between Clari 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.

Clari objects Microsoft Power Bi objects How this pairing syncs
Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. Datasources and Gateways The connections behind datasets and dataflows and the on-premises gateways serving them, read via REST for lineage and dependency mapping. Forecast is specific to Clari and Datasources and Gateways to Microsoft Power Bi — each maps to any object or custom field on the other side.
Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. Refresh History Dataset refresh runs read via GET /datasets/{id}/refreshes, including status, type, and timing, to alert on failed or slow scheduled refreshes. Quota is specific to Clari and Refresh History to Microsoft Power Bi — each maps to any object or custom field on the other side.
Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. 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. Opportunities is specific to Clari and Workspaces (Groups) to Microsoft Power Bi — each maps to any object or custom field on the other side.
Activity (Capture) Meetings, emails, and attachments captured by Clari and mapped to accounts and opportunities; exported read-only via async activity jobs. 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. Activity (Capture) is specific to Clari and Activity Events (Audit Log) to Microsoft Power Bi — each maps to any object or custom field on the other side.
Account field extensions External data points written onto Account records through the ingest API in initial or incremental mode; requires an apikey plus a partnerkey. Users and Access Workspace users and roles read via GET /groups/{id}/users or the admin scanner APIs; read for access reviews and identity reconciliation against an IdP. Account field extensions is specific to Clari and Users and Access to Microsoft Power Bi — each maps to any object or custom field on the other side.
Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. Datasets (Semantic Models) Tabular models behind reports; their rows are read with DAX via POST datasets/{id}/executeQueries, and datasource and refresh metadata via REST list endpoints. Opportunity field extensions is specific to Clari and Datasets (Semantic Models) to Microsoft Power Bi — each maps to any object or custom field on the other side.

How changes propagate between Clari 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.

Clari Microsoft Power Bi Interval-based propagation

DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).

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 Clari records.

Microsoft Power Bi Clari 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 Clari through its API, with automatic retries and rate-limit backoff.

Rate-limit considerations

  • Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
  • 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 Clari ⇄ Microsoft Power Bi

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

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

Real-time

Real-time sync

Changes in Clari 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 Clari 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 Clari or Microsoft Power Bi record.

Observability

Monitoring

Track your Clari ⇄ 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 Clari and Microsoft Power Bi.

How the Clari and Microsoft Power Bi connectors work

Clari

Integration surface
REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
Authentication
API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
Change detection
Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
Capabilities
read · write
Rate limits
Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.

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 Clari 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 Clari 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
    Clari connected
    Microsoft Power Bi connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Clari 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 · Clari ⇄ 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
    Clari Microsoft Power Bi
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Clari 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 354 integrations available for Clari and Microsoft Power Bi.

Popular · 8 of 354
All Clari 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