Skip to content
AI ⇄ Data warehouse

Autopilot to ClickHouse integration — real-time, two-way sync

Keep Autopilot and ClickHouse 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 ClickHouse

Send the records ClickHouse holds into Autopilot for embedding, classification, and scoring, and land what Autopilot produces back in ClickHouse as new columns, one two-way connection instead of a batch job.

ClickHouse holds the raw records the business runs on; Autopilot turns those records into embeddings, scores, labels, and summaries. The two meet wherever a warehouse row needs to be enriched by a model and the result needs somewhere durable to live. Most teams stitch that meeting together with export scripts and a queue, then spend their time keeping the glue alive.

Stacksync syncs Smart Segments, Journeys (Triggers), Activities, Contacts in Autopilot with Dictionaries, Tables (MergeTree family), Databases, Views in ClickHouse field by field, in real time, and in both directions. Rows added or changed in ClickHouse flow into Autopilot as they happen, and the Smart Segments, Journeys (Triggers), Activities, Contacts that Autopilot generates land back in ClickHouse as columns or tables, with field-level mapping and conflict rules in place of a custom pipeline.

The payoff is that model output stops living in a separate place from the data it describes. Once results sit in ClickHouse, they join against billing, product, and usage tables already there, so you can report on quality, cost, and coverage without moving anything by hand.

Common use cases

  • 01 Mirror List and Smart Segment membership into a warehouse to power attribution and audience analytics alongside other sources.
  • 02 Stream Activities into a warehouse so opens, clicks, and journey steps sit next to product and revenue data for lifecycle reporting.
  • 03 Consolidate logs and business records from multiple sources into MergeTree tables for retention and reporting.
  • 04 Land product event data alongside synced CRM accounts so analysts join usage and revenue in one place.

Common sync patterns

History that outlives a run

A continuously synced copy in ClickHouse preserves every generated result, so outputs stay auditable even as they are overwritten or expire inside Autopilot.

Feed live warehouse records to Autopilot

Rows added or changed in ClickHouse flow into Autopilot within seconds, so embeddings, classifications, and enrichments are computed on current data rather than a nightly extract.

Model output back in the warehouse

Scores, labels, embeddings, or summaries produced in Autopilot land in ClickHouse as columns or tables, queryable and joinable with the rest of the business data.

What you can sync between Autopilot and ClickHouse

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 ClickHouse objects How this pairing syncs
Activities Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting. Views Saved queries used as curated, read-only sync sources. Activities is specific to Autopilot and Views to ClickHouse — 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. Materialized views Insert-time transformations that reshape incoming synced rows into aggregates. Contacts is specific to Autopilot and Materialized views to ClickHouse — 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. Distributed tables Query-routing tables over cluster shards in self-managed deployments. Lists is specific to Autopilot and Distributed tables to ClickHouse — 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. Dictionaries In-memory lookup structures refreshed from external sources, sometimes fed by syncs. Custom Fields is specific to Autopilot and Dictionaries to ClickHouse — 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. Tables (MergeTree family) Columnar, append-optimized tables that serve as the destination for high-volume sync loads. Smart Segments is specific to Autopilot and Tables (MergeTree family) to ClickHouse — 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. Databases Namespaces that group tables and scope permissions for sync users. Journeys (Triggers) is specific to Autopilot and Databases to ClickHouse — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and ClickHouse

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 ClickHouse 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 ClickHouse as a row-level write, with types converted between the two schemas.

ClickHouse Autopilot Interval-based propagation

DetectionStacksync polls ClickHouse for changes on an incremental schedule, reading only records changed since the previous pass. No log-based CDC for consumers.

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 ⇄ ClickHouse

Connect Autopilot and ClickHouse for flexible, real-time data sync.

Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Autopilot–ClickHouse connection.

Real-time

Two-way sync

Changes in Autopilot or ClickHouse instantly reflect in both systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

Trigger automated workflows whenever Autopilot or ClickHouse 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 ClickHouse record.

Observability

Monitoring

Track your Autopilot ⇄ ClickHouse 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 ClickHouse.

How the Autopilot and ClickHouse 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.
Autopilot setup guide

ClickHouse

Integration surface
Native TCP protocol and HTTP interface; standard SQL dialect, with MySQL and PostgreSQL wire compatibility available
Authentication
Database credentials (username/password); ClickHouse Cloud issues per-service credentials over TLS
Change detection
No log-based CDC for consumers; incremental reads use polling on monotonic columns, and ClickHouse is usually the destination rather than the source
Capabilities
read · write
How it works

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

    Choose tables

    Pick the Autopilot and ClickHouse 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 · Autopilot ⇄ ClickHouse
    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
    Autopilot ClickHouse
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo
FAQ

Autopilot and ClickHouse 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 513 integrations available for Autopilot and ClickHouse.

Popular · 8 of 513
All Autopilot integrations All ClickHouse 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