Real-time
Two-way sync
Changes in Autopilot or DuckDB instantly reflect in both systems. No stale data, no manual imports.
AI ⇄ Database
Autopilot to DuckDB integration — real-time, two-way sync
Keep Autopilot and DuckDB 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 DuckDB
Sync the records in DuckDB 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. DuckDB 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 DuckDB it describes are two halves of the same thing, and they drift the moment one is updated without the other.
Stacksync syncs Database files, Schemas, Tables, Views in DuckDB with Contacts, Lists, Custom Fields, Smart Segments in Autopilot in real time. Rows created or changed in DuckDB 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 DuckDB, 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 DuckDB 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 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.
- 02 Add contacts to a Journey from a database event or CRM stage change to start automated onboarding or nurture sequences.
- 03 Use DuckDB as a transform step: read synced Parquet exports, aggregate with SQL, and write results back to an operational database.
- 04 Sync SaaS data to Parquet on object storage and query it with DuckDB without standing up a warehouse.
Common sync patterns
One record, one identifier
Each item in Autopilot carries the key of the row in DuckDB it came from, so results resolve back to the exact record with nothing orphaned or duplicated.
Run the AI on current data
Rows created or changed in DuckDB 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 DuckDB, next to the source data your applications already query.
What you can sync between Autopilot and DuckDB
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 | DuckDB objects | How this pairing syncs | |
|---|---|---|---|
| Contacts Core people records (email, name, custom fields, list and segment membership); upserted two-way as the primary sync object. | Views SQL views used to shape or filter data for downstream consumers. | Contacts is specific to Autopilot and Views to DuckDB — each maps to any object or custom field on the other side. | |
| Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. | External files (Parquet/CSV/JSON) Files DuckDB queries in place without loading, common as a sync interchange format. | Lists is specific to Autopilot and External files (Parquet/CSV/JSON) to DuckDB — 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. | Attached databases Additional database files or external systems attached into one session for cross-source queries. | Custom Fields is specific to Autopilot and Attached databases to DuckDB — 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. | Database files Single-file .duckdb databases that jobs read and write directly on disk or object storage. | Smart Segments is specific to Autopilot and Database files to DuckDB — 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. | Schemas Namespaces within a database used to organize tables in sync outputs. | Journeys (Triggers) is specific to Autopilot and Schemas to DuckDB — 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. | Tables Columnar tables created via SQL; the destination for materialized sync data. | Activities is specific to Autopilot and Tables to DuckDB — each maps to any object or custom field on the other side. |
How changes propagate between Autopilot and DuckDB
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 DuckDB 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 DuckDB as a row-level write, with types converted between the two schemas.
DuckDB Autopilot Interval-based propagation
DetectionStacksync polls DuckDB for changes on an incremental schedule, reading only records changed since the previous pass. Polling or full re-reads.
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.
- DuckDB: No API rate limits; throughput is bounded by local compute and I/O.
What ships with Autopilot ⇄ DuckDB
Connect Autopilot and DuckDB for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Autopilot–DuckDB connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Autopilot or DuckDB 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 DuckDB record.
Observability
Monitoring
Track your Autopilot ⇄ DuckDB 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 DuckDB.
How the Autopilot and DuckDB 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.
DuckDB
- Integration surface
- In-process SQL engine via client libraries (Python, Node.js, JDBC, CLI); no server or network API by default
- Authentication
- None built in; access control is file-system level (MotherDuck adds token auth for its hosted service)
- Change detection
- Polling or full re-reads; no change feed or transaction log API
- Capabilities
- read · write
- Rate limits
- No API rate limits; throughput is bounded by local compute and I/O
How it works
How to connect Autopilot to DuckDB — 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 DuckDB 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
DuckDB
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Autopilot and DuckDB 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 ⇄ DuckDBCustomers 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 DuckDBCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Autopilot and DuckDB integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Autopilot and DuckDB: authenticate both systems, choose the objects to sync (such as Autopilot's Contacts and Lists), 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 DuckDB connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Autopilot–DuckDB integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Autopilot and DuckDB. 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 DuckDB: Polling or full re-reads; no change feed or transaction log API. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Autopilot side: Contacts, Lists, Custom Fields, Smart Segments, plus custom fields where Autopilot exposes them. On the DuckDB side: Database files, Schemas, Tables, Views. 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 421 integrations available for Autopilot and DuckDB.
Popular · 7 of 421
-
Autopilot ⇄ OCI Database (Oracle Cloud) -
Autopilot ⇄ OpenSearch -
Autopilot ⇄ Oracle DB -
Autopilot ⇄ RavenDB -
DuckDB ⇄ Openai -
DuckDB ⇄ Azure OpenAI -
DuckDB ⇄ Pinecone
No integrations match .
