Skip to content
Database ⇄ Accounting and finance

Azure Cosmos DB to Pigment integration — real-time, two-way sync

Keep Azure Cosmos DB and Pigment 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 Azure Cosmos DB and Pigment

Work with Pigment's financial data straight from Azure Cosmos DB: read it with ordinary queries, write to it from your own code, and let Stacksync keep both sides consistent.

Engineers need finance data more often than finance systems make it easy to get: for internal tools, reporting services, or logic that reacts to invoices and payments. Working through the vendor API means rate limits, pagination, and glue code that has to be maintained forever.

Stacksync mirrors Users and permissions, Applications, Metrics, Dimension lists from Pigment into Items (JSON documents), Partition keys, Change feed entries, Stored procedures and triggers in Azure Cosmos DB and keeps the two in sync bi-directionally and in real time. Your services read finance records with normal queries against Azure Cosmos DB, and rows your code writes or updates flow back into Pigment with validation, so the finance system stays the system of record.

Common use cases

  • Sync headcount and compensation data from an HRIS into workforce planning models.
  • Push CRM pipeline data (deals, stages, amounts) into Pigment for revenue and capacity planning.
  • Stream operational documents from Cosmos DB into a SQL warehouse via the change feed for analytics without hitting request-unit budgets with full scans.
  • Sync CRM or ERP records into a Cosmos DB container that backs a customer-facing application.

Query finance data like any other data

Customers, invoices, and payments from Pigment live in Azure Cosmos DB as regular tables or collections your team can join, index, and query.

Internal tools without API plumbing

Build dashboards and back-office tools directly on Azure Cosmos DB; Stacksync handles the API calls, rate limits, and retries against Pigment.

Write back safely

Updates written to the synced tables in Azure Cosmos DB propagate into Pigment, so automations can create or correct finance records without custom integration code.

What you can sync between Azure Cosmos DB and Pigment

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.

Azure Cosmos DB objects Pigment objects
Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. Data imports Scheduled loads that bring actuals from ERPs, CRMs, and HRIS into the model
Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. Users and permissions Access controls governing which model areas a sync can touch
Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. Applications Planning models organized by domain such as finance, sales, or workforce
Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. Metrics Multidimensional values holding plans and actuals; the main target for inbound data
Databases Top-level namespaces that scope containers and throughput provisioning. Dimension lists Master data like accounts, products, or employees that metrics are sliced by
Containers The unit of partitioning and throughput; each container maps to a synced collection. Tables Row-based transactional data loaded into models from source systems
What ships with Azure Cosmos DB ⇄ Pigment

Connect Azure Cosmos DB and Pigment for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Pigment connection.

Real-time

Two-way sync

Changes in Azure Cosmos DB or Pigment instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Azure Cosmos DB or Pigment 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 Azure Cosmos DB or Pigment record.

Observability

Monitoring

Track your Azure Cosmos DB ⇄ Pigment sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Azure Cosmos DB and Pigment.

How the Azure Cosmos DB and Pigment connectors work

Azure Cosmos DB

Integration surface
REST API and SDKs over HTTPS (API for NoSQL, formerly the SQL API); also MongoDB, Cassandra, Gremlin, and Table API surfaces
Authentication
Account keys, resource tokens, or Microsoft Entra ID role-based access
Change detection
Built-in change feed exposing inserts and updates in order within each partition key range
Capabilities
read · write · CDC

Pigment

Integration surface
REST-based import and export API
Authentication
API keys, issued separately for import and export
Change detection
no change feed; syncs run scheduled imports and exports
Capabilities
read · write
Rate limits
subject to the platform's API rate limits
How it works

How to connect Azure Cosmos DB to Pigment — 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 Azure Cosmos DB and Pigment 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
    Azure Cosmos DB connected
    Pigment connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Azure Cosmos DB and Pigment 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 · Azure Cosmos DB ⇄ Pigment
    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
    Azure Cosmos DB Pigment
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
FAQ

Azure Cosmos DB and Pigment integration FAQ

SECURITY

Security teams love 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.

SOC 2 type II
ISO 27001
HIPAA BAA
GDPR
CCPA
CSA STAR
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:

Related integrations

Every pair below is a real-time, two-way sync. Search all 386 integrations available for Azure Cosmos DB and Pigment.

Popular · 8 of 386
Coworkers laughing in front of a laptop in a casual office setting

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