Skip to content
AI

Connect Autopilot to any app with two-way sync.

Two-way sync Autopilot across all your CRMs, databases, data warehouses, EDI systems, and AI tools, with custom workflows tailored to your data.

  • SOC 2 and 6 other compliance frameworks
  • POC with real engineers in minutes
Setup guide: how Stacksync connects to Autopilot

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
Object catalog

What Stacksync syncs in Autopilot.

These objects sync between Autopilot and any connected system, with field-level mapping and conflict resolution. Custom fields are picked up from the live schema where Autopilot exposes them.

Contacts
Core people records (email, name, custom fields, list and segment membership); upserted two-way as the primary sync object.
Lists
Static contact lists; membership is readable per list and writable by adding or removing contacts.
Custom Fields
User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns.
Smart Segments
Rule-based dynamic audiences; membership is computed by Autopilot, so it is read-only over the API.
Journeys (Triggers)
Automation journeys; a contact can be added to a journey via its trigger endpoint to start automated email or SMS sequences.
Activities
Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting.
API surface

How Stacksync connects to Autopilot.

The connector runs on Autopilot's native API. Stacksync manages authentication, rate limits, retries, and schema changes so your team does not maintain integration code.

Connection
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.
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.

Sync directions

  • Read Supported
  • Write Supported
  • Change data capture Not available
  • Webhooks Not available
Autopilot connector documentation
What ships with Autopilot

Connect Autopilot for flexible, real-time data sync.

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

Real-time

Two-way sync

Changes in Autopilot instantly reflect across connected systems. No stale data, no manual imports.

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Autopilot sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions.

Use cases

What teams run on the Autopilot connector.

Autopilot (rebranded Ortto in 2021) is a marketing automation and customer-journey platform owned by lifecycle marketers, growth, and RevOps teams. Its data centers on Contacts, each with custom fields, list memberships, segment memberships, and activity history. Teams push signups and profile changes into Autopilot to drive email and SMS journeys, then read engagement and membership back out for reporting. Because it exposes a REST API with no CDC, keeping Autopilot aligned with a CRM or warehouse means upserting contacts in and polling changes out.

  • Marketing operations and lifecycle marketers
  • Growth and demand-generation teams
  • Revenue operations (RevOps)
  • Data engineering and analytics

  1. Read Contacts with their custom fields into Postgres or Snowflake so marketing ops can report on list membership, segments, and engagement in SQL.

  2. 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.

  3. Add contacts to a Journey from a database event or CRM stage change to start automated onboarding or nurture sequences.

  4. Two-way sync Contacts and custom fields between Autopilot and a CRM such as Salesforce or HubSpot so marketing and sales work from one profile.

  5. Mirror List and Smart Segment membership into a warehouse to power attribution and audience analytics alongside other sources.

  6. Stream Activities into a warehouse so opens, clicks, and journey steps sit next to product and revenue data for lifecycle reporting.

All Autopilot integrations

Pick the system you need to keep in sync with Autopilot. Each page covers the sync setup, field mapping, and common workflows for that pair.

CRM · 41

ERP · 37

Database · 50

Data warehouse · 28

Business productivity · 37

How it works

Set up Autopilot in minutes, without APIs.

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 with its 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
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

    Pick the Autopilot objects to sync — Stacksync auto-detects the schema, 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
    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 database
    Company company_name text
    Email email text
    Amount amount numeric
    Created created_at timestamp
Try interactive demo

FAQ

Autopilot connector FAQ

What can I sync with the Autopilot connector?

Autopilot's core objects — Contacts, Lists, Custom Fields, Smart Segments and custom fields — can sync with any of 302 other systems. Every integration is real-time and bidirectional, with field-level mapping and conflict resolution.

How does Stacksync connect to Autopilot?

Via REST API (Autopilot v1); Autopilot rebranded to Ortto in 2021 and the newer Ortto API co-exists with the legacy Autopilot endpoints, authenticated with 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/. Changes are detected as follows — 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.. Stacksync manages rate limits, retries, and schema changes automatically.

Is the Autopilot connector two-way?

Yes. Changes made in Autopilot propagate to the connected system and vice versa, in milliseconds. One-way flows are also supported when a direction should stay read-only.

How long does an Autopilot integration take to set up?

Most Autopilot integrations go live in minutes: authenticate Autopilot and the other system, pick objects and fields, and enable the sync. No code and no infrastructure to manage.

Is Autopilot data secure in transit?

Stacksync is SOC 2 Type II, ISO 27001, GDPR and HIPAA compliant. Autopilot data is encrypted in transit, and a zero-persistent-storage architecture means records are not retained after a sync operation.

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