Source connector

Autopilot connector

Autopilot integration for databases, warehouses and BI tools

Visual marketing automation and customer journeys. Datrise captures Autopilot entities such as contacts, journeys, lists, email events, triggers and custom fields, then lands normalized and typed models for warehouse reporting, attribution, and AI workflows.

The Ortto API (formerly Autopilot) authenticates with API key, and Autopilot caps calls at Per plan: Sandbox 5, Starter 10, Professional 30, Enterprise 30 requests/second (expandable on request); per IP 2000 requests per 10 seconds and 6000 per 60 seconds; HTTP 429 with a `try-in-seconds` retry hint.

Of the 6 objects, 5 sync as upserts keyed on the primary key and 1 as append-only streams, so each incremental run moves only what changed since the last watermark. Every object lands in its own table (for example `autopilot_contacts`) with a schema derived from the Autopilot API rather than a flattened CSV, in any of the 43 supported destinations.

Datrise is in early access: pick a destination below to open the Autopilot pipeline page, and join the waitlist to get the Autopilot connector with guided onboarding.

Incremental syncSchema-aware mapping43 destinations available

What Autopilot data Datrise extracts

Each object lands in its own typed table. Sync mode is derived from the object: history-style objects append, everything else upserts.

Object	Landing table	Sync mode
contacts	autopilot_contacts	Upsert by primary key, incremental on updated-at
journeys	autopilot_journeys	Upsert by primary key, incremental on updated-at
lists	autopilot_lists	Upsert by primary key, incremental on updated-at
email events	autopilot_email_events	Append-only, incremental by timestamp
triggers	autopilot_triggers	Upsert by primary key, incremental on updated-at
custom fields	autopilot_custom_fields	Upsert by primary key, incremental on updated-at

Autopilot API: setup facts for the connector

Verified against the vendor documentation on 2026-10-05. Unknown values are left blank rather than guessed.

API	Ortto API (formerly Autopilot)
Authentication	API key — A private custom API key, created per Custom API data source in Ortto, is sent in an `X-Api-Key` request header; the docs say requests without it are rejected.
Pagination	offset — POST /v1/person/get takes `limit` (page length, 100 in the docs example) and `offset`, and returns `next_offset`, `cursor_id` and `has_more`; the second page is requested with the returned `offset` and `cursor_id`.
Rate limit	Per plan: Sandbox 5, Starter 10, Professional 30, Enterprise 30 requests/second (expandable on request); per IP 2000 requests per 10 seconds and 6000 per 60 seconds; HTTP 429 with a `try-in-seconds` retry hint
Incremental cursor	Not published
Webhooks	Not published
Bulk export	Not published
Deletes detectable	Not published

Official API reference

What bites when replicating Autopilot

Autopilot was renamed Ortto (autopilothq.com now redirects to ortto.com); the legacy Autopilot REST API at api2.autopilothq.com still answers (HTTP 400 asking for an `autopilotapikey` header or `apikey` query parameter), but the current Ortto Knowledge Base documents only the Ortto API, which uses different base URLs, endpoints (`/v1/person/get`) and an `X-Api-Key` header.
Base URL depends on the instance region: https://api.ap3api.com/ by default, https://api.au.ap3api.com/ for Australia and https://api.eu.ap3api.com/ for Europe; a key only works against its own account's region.
Bad requests are punished: 15 bad requests in 15 seconds, or 15 bad-credential requests in 15 seconds, trigger a 15-second IP ban.
Archived people stop receiving activities: activity sent for an archived person creates a duplicate contact record that does not keep the original subscription status; archive, restore and delete accept `inclusion_ids` in batches of up to 100 contacts.

Compare this against every other documented API

Popular destinations for Autopilot

Choose a destination below to open the ready pipeline page.

A
Airtable
Relational spreadsheet destination for ops and go-to-market teams.
View pipeline
A
Amazon Athena
Serverless SQL over S3 data lake tables.
View pipeline
A
Amazon DynamoDB
Serverless key-value and document store on AWS.
View pipeline
A
Amazon QuickSight
AWS serverless BI with SPICE and embedded analytics.
View pipeline
A
Amazon Redshift
AWS petabyte-scale warehouse with Spectrum.
View pipeline
A
Amazon S3 Data Lake
Object storage landing zone for parquet and snapshots.
View pipeline
A
Apache Superset
Open-source BI for SQL exploration, charts, and dashboard publishing.
View pipeline
A
Azure Data Lake Storage
ADLS Gen2 object storage for analytics workloads.
View pipeline
A
Azure Synapse
Microsoft analytics workspace with SQL pools.
View pipeline

Autopilot connector FAQ

What Autopilot data does the connector extract?: 6 objects: contacts, journeys, lists, email events, triggers and custom fields. Each lands in its own table with types preserved; history-style objects (1: email events) load as append-only streams.
Is the Autopilot integration incremental?: Yes. After the initial full load, every run reads only records changed since the last watermark (updated-at or event timestamp) and applies an upsert or an append depending on the object.
Where can I load Autopilot data?: Into 43 destinations: relational databases, cloud warehouses, data lakes, spreadsheets and BI tools. Each Autopilot → destination pair has its own page with the object-to-table mapping.

Related sources

Other sources in the same category, each with its own connector page.

Early access

Launch your Autopilot pipeline with guided onboarding

Join the waitlist to get priority access for Autopilot integrations with guided setup, schema-aware mapping, and production-grade incremental sync.