Skip to content
AI ⇄ Data warehouse

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

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

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

Exasol 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 Lists, Custom Fields, Smart Segments, Journeys (Triggers) in Autopilot with Virtual schemas, UDF scripts, Users and roles, Schemas in Exasol field by field, in real time, and in both directions. Rows added or changed in Exasol flow into Autopilot as they happen, and the Lists, Custom Fields, Smart Segments, Journeys (Triggers) that Autopilot generates land back in Exasol 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 Exasol, 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 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 Keep dimension tables such as customers and products aligned with the systems of record.
  • 04 Load CRM and ERP records into Exasol tables on a schedule so analysts query fresh operational data.

Common sync patterns

Model output back in the warehouse

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

Keep an index in step with the source

As records change in Exasol, matching Lists, Custom Fields, Smart Segments, Journeys (Triggers) in Autopilot are inserted, updated, or removed, so what Autopilot serves reflects the warehouse instead of a stale snapshot.

One place to analyze AI results

Combine Autopilot's output with the tables already in Exasol to report on model quality, cost, and coverage without exporting anything to a spreadsheet.

What you can sync between Autopilot and Exasol

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 Exasol 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. Schemas Namespaces that group the tables a sync reads from or writes into. Contacts is specific to Autopilot and Schemas to Exasol — 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. Tables Primary sync target; columnar relational tables written with standard SQL. Lists is specific to Autopilot and Tables to Exasol — 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. Views Read-only query surfaces often used as curated sources for reverse ETL. Custom Fields is specific to Autopilot and Views to Exasol — 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. Virtual schemas Federated views over external sources; useful for deciding what needs physical replication. Smart Segments is specific to Autopilot and Virtual schemas to Exasol — 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. UDF scripts In-database functions that can transform synced data after load. Journeys (Triggers) is specific to Autopilot and UDF scripts to Exasol — 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. Users and roles Grant read/write access for the dedicated integration account. Activities is specific to Autopilot and Users and roles to Exasol — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Exasol

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

Exasol Autopilot Interval-based propagation

DetectionStacksync polls Exasol for changes on an incremental schedule, reading only records changed since the previous pass. Polling with timestamp or key columns.

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.
  • Exasol: No API quota; concurrency is bounded by cluster resources and session limits.
What ships with Autopilot ⇄ Exasol

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Autopilot and Exasol 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

Exasol

Integration surface
SQL over JDBC/ODBC drivers and a WebSocket-based client protocol
Authentication
Database credentials (username and password)
Change detection
Polling with timestamp or key columns; Exasol does not expose a transaction-log change feed to clients
Capabilities
read · write
Rate limits
No API quota; concurrency is bounded by cluster resources and session limits
How it works

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

    Choose tables

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

Autopilot and Exasol 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 405 integrations available for Autopilot and Exasol.

Popular · 7 of 405
All Autopilot integrations All Exasol 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