Skip to content
AI ⇄ Business productivity

Autopilot to Customer.io integration — real-time, two-way sync

Keep Autopilot and Customer.io 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 Customer.io

Feed Customer.io's records into Autopilot for indexing, classification, and generation, then land the model's output back on those same records, in real time and in both directions.

Autopilot works on data it does not own. The records, conversations, tickets, messages, and events it needs to embed, classify, summarize, or answer questions about actually live in Customer.io, the tool the team uses every day. So the value of Autopilot depends on two flows that most teams stitch together with a custom script or a one-time export: getting Customer.io's data in, and getting the model's results back out to where people can act on them. When either flow runs on a batch or a stale snapshot, the model reasons over yesterday's data and its output never reaches the record it belongs to.

Stacksync syncs Broadcasts, Deliveries / Messages, Newsletters, People from Customer.io into Autopilot continuously, so the model always works from current records instead of a snapshot, and writes Journeys (Triggers), Activities, Contacts, Lists, the scores, labels, summaries, drafts, and embedding metadata Autopilot produces, back onto the matching record in Customer.io. The sync is field-level and keyed on a stable identifier, so every output attaches to the exact record it came from and each system keeps its own extra fields untouched.

You decide the direction and the trigger conditions per field: pull records one way to build and keep a retrieval corpus current, push results the other way onto the operational record, or both.

Common use cases

  • 01 Add contacts to a Journey from a database event or CRM stage change to start automated onboarding or nurture sequences.
  • 02 Mirror List and Smart Segment membership into a warehouse to power attribution and audience analytics alongside other sources.
  • 03 Land delivery and engagement events (sent, opened, clicked, bounced) from reporting webhooks into a warehouse for attribution analysis.
  • 04 Keep unsubscribe and subscription-preference state consistent between Customer.io and the CRM to avoid compliance gaps.

Common sync patterns

Build a retrieval corpus from Customer.io's records

Records, tickets, messages, or events from Customer.io sync into Autopilot so they can be indexed, embedded, or retrieved as context, without a hand-built extraction job.

Keep the model's knowledge current

As records change in Customer.io, the synced copy in Autopilot updates within seconds, so retrieval and generation reason over live data rather than a stale export.

Where Autopilot classifies or scores: results land on the record

Categories, sentiment, priority, or scores produced by Autopilot write back onto the matching record in Customer.io, so the team acts on them in the tool they already use.

What you can sync between Autopilot and Customer.io

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 Customer.io objects How this pairing syncs
Smart Segments Rule-based dynamic audiences; membership is computed by Autopilot, so it is read-only over the API. People Profiles with attributes, matched on identifiers like id or email; the main write target of data syncs. Smart Segments is specific to Autopilot and People to Customer.io — 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. Objects Non-person entities such as accounts or companies, related to people for account-level messaging. Journeys (Triggers) is specific to Autopilot and Objects to Customer.io — 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. Events Behavioral events sent via the Track API that trigger campaigns. Activities is specific to Autopilot and Events to Customer.io — 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. Segments Attribute- or event-based groups; data syncs feed the attributes segments evaluate. Contacts is specific to Autopilot and Segments to Customer.io — 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. Campaigns Automated workflows whose membership and metrics can be read via the App API. Lists is specific to Autopilot and Campaigns to Customer.io — 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. Broadcasts One-off sends to segments or audiences, triggerable via API. Custom Fields is specific to Autopilot and Broadcasts to Customer.io — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Customer.io

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 Customer.io 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 written to Customer.io through its API, with automatic retries and rate-limit backoff.

Customer.io Autopilot Sub-second propagation

DetectionCustomer.io notifies Stacksync of record changes through webhook events. Reporting webhooks push message and delivery events.

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.
  • Customer.io: Subject to per-API rate limits documented by Customer.io.
What ships with Autopilot ⇄ Customer.io

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

How the Autopilot and Customer.io 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

Customer.io

Integration surface
REST APIs split by purpose: Track API for data ingestion, App API for campaigns, people lookups, and messages
Authentication
Basic auth with site ID and API key for the Track API; bearer token for the App API
Change detection
Reporting webhooks push message and delivery events; person attribute changes are not streamed and require source-side detection
Capabilities
read · write · webhooks
Rate limits
Subject to per-API rate limits documented by Customer.io
How it works

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

    Choose tables

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

Autopilot and Customer.io 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 390 integrations available for Autopilot and Customer.io.

Popular · 6 of 390
All Autopilot integrations All Customer.io 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