Real-time
Two-way sync
Changes in Autopilot or Azure Cosmos DB instantly reflect in both systems. No stale data, no manual imports.
AI ⇄ Database
Autopilot to Azure Cosmos DB integration — real-time, two-way sync
Keep Autopilot and Azure Cosmos DB 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 Autopilot and Azure Cosmos DB
Sync the records in Azure Cosmos DB into Autopilot and land its embeddings, classifications, and generated fields back on the same rows, in real time and without a pipeline to maintain.
AI systems do not hold customers or invoices the way business apps do. What they hold is derived from your data: the vectors and metadata in a vector store, or the classifications, extracted fields, and generated text a model produces over records it was given. Azure Cosmos DB is where those source records actually live. The bridge between the two is the row itself, since an item in Autopilot and the record in Azure Cosmos DB it describes are two halves of the same thing, and they drift the moment one is updated without the other.
Stacksync syncs Stored procedures and triggers, Databases, Containers, Items (JSON documents) in Azure Cosmos DB with Journeys (Triggers), Activities, Contacts, Lists in Autopilot in real time. Rows created or changed in Azure Cosmos DB flow into Autopilot so inference and embedding run on current data, and the scores, labels, and generated fields Autopilot produces flow back onto the matching rows in Azure Cosmos DB, mapped field by field. A change on either side appears on the other within seconds, with no extraction job or webhook plumbing to keep alive.
Because matching is by a stable identifier, every row in Azure Cosmos DB stays tied to its AI-side counterpart in Autopilot. Retrieval, enrichment, and generated content always resolve back to the record they came from, so there are no orphaned vectors and no labels describing a version of a row that no longer exists.
Common use cases
- 01 Stream Activities into a warehouse so opens, clicks, and journey steps sit next to product and revenue data for lifecycle reporting.
- 02 Upsert Contacts from a CRM or product database into Autopilot so new signups and profile changes flow into email and SMS journeys without manual CSV imports.
- 03 Two-way sync between a Cosmos DB-backed product catalog and a PIM or commerce platform.
- 04 Consolidate documents from multiple containers into a single reporting store.
Common sync patterns
Run the AI on current data
Rows created or changed in Azure Cosmos DB flow into Autopilot as they happen, so embeddings, classifications, and prompts run on the latest records instead of a nightly snapshot.
Write results back onto the record
Scores, labels, extracted fields, or generated text produced in Autopilot land on the matching row in Azure Cosmos DB, next to the source data your applications already query.
Keep derived data fresh as sources change
When a row in Azure Cosmos DB is updated or removed, its counterpart in Autopilot is updated or removed too, so nothing in Autopilot describes a record that has since changed or gone.
What you can sync between Autopilot and Azure Cosmos DB
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.
| Autopilot objects | Azure Cosmos DB objects | How this pairing syncs | |
|---|---|---|---|
| Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. | Databases Top-level namespaces that scope containers and throughput provisioning. | Lists is specific to Autopilot and Databases to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Custom Fields User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns. | Containers The unit of partitioning and throughput; each container maps to a synced collection. | Custom Fields is specific to Autopilot and Containers to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Smart Segments Rule-based dynamic audiences; membership is computed by Autopilot, so it is read-only over the API. | Items (JSON documents) Schema-flexible JSON records read and written during sync; nested structures are flattened or mapped as needed. | Smart Segments is specific to Autopilot and Items (JSON documents) to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Journeys (Triggers) Automation journeys; a contact can be added to a journey via its trigger endpoint to start automated email or SMS sequences. | Partition keys Determine data distribution and must be included on writes for the sync to route items correctly. | Journeys (Triggers) is specific to Autopilot and Partition keys to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Activities Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting. | Change feed entries Ordered record of inserts and updates per partition, consumed for incremental sync. | Activities is specific to Autopilot and Change feed entries to Azure Cosmos DB — each maps to any object or custom field on the other side. | |
| Contacts Core people records (email, name, custom fields, list and segment membership); upserted two-way as the primary sync object. | Stored procedures and triggers Server-side logic scoped to a partition; relevant when writes must respect existing validation. | Contacts is specific to Autopilot and Stored procedures and triggers to Azure Cosmos DB — each maps to any object or custom field on the other side. |
How changes propagate between Autopilot and Azure Cosmos DB
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.
Autopilot Azure Cosmos DB Interval-based propagation
DetectionStacksync polls Autopilot for changes on an incremental schedule, reading only records changed since the previous pass. No CDC.
DeliveryEach detected change is applied to Azure Cosmos DB as a row-level write, with types converted between the two schemas.
Azure Cosmos DB Autopilot 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 Autopilot through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Autopilot: The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
What ships with Autopilot ⇄ Azure Cosmos DB
Connect Autopilot and Azure Cosmos DB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Autopilot–Azure Cosmos DB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Autopilot or Azure Cosmos DB 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 Autopilot or Azure Cosmos DB record.
Observability
Monitoring
Track your Autopilot ⇄ Azure Cosmos DB sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Autopilot and Azure Cosmos DB.
How the Autopilot and Azure Cosmos DB connectors work
Autopilot
- Integration surface
- REST API (Autopilot v1); Autopilot rebranded to Ortto in 2021 and the newer Ortto API co-exists with the legacy Autopilot endpoints
- Authentication
- Per-account API key sent in the autopilotapikey request header (generated in account settings); requests use Content-Type application/json against https://api2.autopilothq.com/v1/
- Change detection
- No CDC; incremental sync polls the /contacts endpoint with bookmark cursor pagination and updated timestamps. Journey webhook actions can push specific contact events, but there is no general change-subscription webhook, so polling is the reliable path.
- Capabilities
- read · write
- Rate limits
- The REST API is capped at 100 requests/minute per account; exceeding it returns HTTP 429. Enterprise plans can request a higher limit. Contact writes accept an array for bulk upsert, and list and segment reads paginate via a bookmark cursor.
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
How it works
How to connect Autopilot to Azure Cosmos DB — 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 Autopilot and Azure Cosmos DB with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Autopilot
connected
Azure Cosmos DB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Autopilot and Azure Cosmos DB 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 · Autopilot ⇄ Azure Cosmos DBCustomers 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.
Autopilot Azure Cosmos DBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Autopilot and Azure Cosmos DB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Autopilot and Azure Cosmos DB: authenticate both systems, choose the objects to sync (such as Autopilot's Lists and Custom Fields), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Autopilot and Azure Cosmos DB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Autopilot–Azure Cosmos DB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Autopilot and Azure Cosmos DB. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Autopilot: No CDC; incremental sync polls the /contacts endpoint with bookmark cursor pagination and updated timestamps. Journey webhook actions can push specific contact events, but there is no general change-subscription webhook, so polling is the reliable path. On Azure Cosmos DB: Built-in change feed exposing inserts and updates in order within each partition key range. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Autopilot side: Journeys (Triggers), Activities, Contacts, Lists, plus custom fields where Autopilot 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.
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 411 integrations available for Autopilot and Azure Cosmos DB.
Popular · 7 of 411
-
Autopilot ⇄ Firebase -
Autopilot ⇄ SingleStore -
Autopilot ⇄ Amazon Aurora -
Autopilot ⇄ Amazon Lightsail -
Azure Cosmos DB ⇄ Pinecone -
Azure Cosmos DB ⇄ Openai -
Azure Cosmos DB ⇄ Azure OpenAI
No integrations match .
