Real-time
Two-way sync
Changes in Azure Cosmos DB or Gladly instantly reflect in both systems. No stale data, no manual imports.
Database ⇄ CRM
Azure Cosmos DB to Gladly integration — real-time, two-way sync
Keep Azure Cosmos DB and Gladly 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 Gladly
Treat Gladly like part of your database: its records live in Azure Cosmos DB as real tables, and writes in either place sync to the other in seconds.
Product and engineering teams constantly need CRM data, and the CRM API is a poor way to get it: rate limits, pagination, custom objects, and integration code that breaks when an admin renames a field. What they actually want is the data in Azure Cosmos DB, where it can be queried and joined like everything else.
Stacksync mirrors Customer profiles, Conversations, Conversation items, Agents from Gladly into Stored procedures and triggers, Databases, Containers, Items (JSON documents) in Azure Cosmos DB with real-time, bi-directional sync. Read CRM records with plain queries; write updates from your application and they appear in Gladly with validation intact. Go-to-market teams keep working in the CRM, engineers keep working in the database, and neither has to think about the other.
Common use cases
- 01 Mirror conversations and topics into a warehouse for CX analytics and staffing models.
- 02 Keep customer attributes such as loyalty tier and lifetime value synced from a warehouse into Gladly profiles for routing and prioritization.
- 03 Stream operational documents from Cosmos DB into a SQL warehouse via the change feed for analytics without hitting request-unit budgets with full scans.
- 04 Sync CRM or ERP records into a Cosmos DB container that backs a customer-facing application.
Common sync patterns
Internal tools without API code
Back-office apps read and write the synced tables; Stacksync handles the Gladly API, limits, and retries.
Trigger workflows from CRM changes
Field and stage updates in Gladly arrive as row changes in Azure Cosmos DB, ready to drive jobs and notifications.
Query the CRM like a database
Accounts, contacts, and custom objects from Gladly become tables in Azure Cosmos DB you can join with application data directly.
What you can sync between Azure Cosmos DB and Gladly
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 | Gladly objects | How this pairing syncs | |
|---|---|---|---|
| Containers The unit of partitioning and throughput; each container maps to a synced collection. | Customer profiles The central entity; merges identifiers like email, phone, and order IDs, which syncs use for matching. | Containers is specific to Azure Cosmos DB and Customer profiles to Gladly — each maps to any object or custom field on the other side. | |
| Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Conversations Each customer's continuous timeline; status and outcomes sync to CRMs and warehouses. | Items (JSON documents) is specific to Azure Cosmos DB and Conversations to Gladly — each maps to any object or custom field on the other side. | |
| Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Conversation items Individual messages across voice, SMS, chat, and email attached to the conversation. | Partition keys is specific to Azure Cosmos DB and Conversation items to Gladly — each maps to any object or custom field on the other side. | |
| Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Agents User records used to attribute work in CX analytics. | Change feed entries is specific to Azure Cosmos DB and Agents to Gladly — each maps to any object or custom field on the other side. | |
| Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Topics Categorization applied to conversations; the key dimension for contact-driver reporting. | Stored procedures and triggers is specific to Azure Cosmos DB and Topics to Gladly — each maps to any object or custom field on the other side. | |
| Databases Top-level namespaces that scope containers and throughput provisioning. | Tasks Follow-up work items created from external triggers or synced for workload reporting. | Databases is specific to Azure Cosmos DB and Tasks to Gladly — each maps to any object or custom field on the other side. |
How changes propagate between Azure Cosmos DB and Gladly
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.
Azure Cosmos DB Gladly Sub-second propagation
DetectionChanges in Azure Cosmos DB are captured at the source via change data capture — no polling loop against its API. Built-in change feed exposing inserts and updates in order within each partition key range.
DeliveryEach detected change is written to Gladly through its API, with automatic retries and rate-limit backoff.
Gladly Azure Cosmos DB Sub-second propagation
DetectionGladly notifies Stacksync of record changes through webhook events. Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports.
DeliveryEach detected change is applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.
Rate-limit considerations
- Gladly: Subject to the platform's API rate limits.
What ships with Azure Cosmos DB ⇄ Gladly
Connect Azure Cosmos DB and Gladly for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Azure Cosmos DB–Gladly connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Azure Cosmos DB or Gladly 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 Gladly record.
Observability
Monitoring
Track your Azure Cosmos DB ⇄ Gladly 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 Gladly.
How the Azure Cosmos DB and Gladly 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
Gladly
- Integration surface
- REST API
- Authentication
- API tokens used with basic authentication tied to an agent email
- Change detection
- Webhook event subscriptions for conversation and customer events, supplemented by polling and report exports
- Capabilities
- read · write · webhooks
- Rate limits
- Subject to the platform's API rate limits
How it works
How to connect Azure Cosmos DB to Gladly — 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.
- 01
Connect your apps
Authenticate Azure Cosmos DB and Gladly with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Azure Cosmos DB
connected
Gladly
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Azure Cosmos DB and Gladly 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.
objects · Azure Cosmos DB ⇄ GladlyCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
Azure Cosmos DB GladlyCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Azure Cosmos DB and Gladly integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Azure Cosmos DB and Gladly: authenticate both systems, choose the objects to sync (such as Azure Cosmos DB's Containers and Items (JSON documents)), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Gladly side: Customer profiles, Conversations, Conversation items, Agents, plus custom fields where Gladly exposes them. On the Azure Cosmos DB side: Stored procedures and triggers, Databases, Containers, Items (JSON documents). Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
-
Common patterns for Azure Cosmos DB and Gladly: Internal tools without API code; Trigger workflows from CRM changes; Query the CRM like a database. Back-office apps read and write the synced tables; Stacksync handles the Gladly API, limits, and retries.
-
Azure Cosmos DB: 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. Gladly: REST API. Authentication: API tokens used with basic authentication tied to an agent email. Stacksync manages authentication, retries, and rate limits on both sides.
-
Gladly: Gladly's model is customer-centric rather than ticket-centric: each customer has one continuous conversation timeline, and channel interactions attach as conversation items. Azure Cosmos DB: The change feed is a first-class feature: it records inserts and updates (and, in newer modes, deletes) so incremental sync does not require scanning containers. Stacksync's field mapping accounts for these differences between Azure Cosmos DB and Gladly without custom code.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 345 integrations available for Azure Cosmos DB and Gladly.
Popular · 3 of 345
No integrations match .
