Skip to content
AI ⇄ Database

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

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

Sync the records in Reltio into Autopilot and land its embeddings, classifications, and generated fields back on the same rows, in real time and without a pipeline to maintain.

AI systems do not hold customers or invoices the way business apps do. What they hold is derived from your data: the vectors and metadata in a vector store, or the classifications, extracted fields, and generated text a model produces over records it was given. Reltio is where those source records actually live. The bridge between the two is the row itself, since an item in Autopilot and the record in Reltio it describes are two halves of the same thing, and they drift the moment one is updated without the other.

Stacksync syncs Matches (Potential Matches), Activity Log, Data Change Requests (DCR), Reference Data (RDM) in Reltio with Journeys (Triggers), Activities, Contacts, Lists in Autopilot in real time. Rows created or changed in Reltio flow into Autopilot so inference and embedding run on current data, and the scores, labels, and generated fields Autopilot produces flow back onto the matching rows in Reltio, mapped field by field. A change on either side appears on the other within seconds, with no extraction job or webhook plumbing to keep alive.

Because matching is by a stable identifier, every row in Reltio stays tied to its AI-side counterpart in Autopilot. Retrieval, enrichment, and generated content always resolve back to the record they came from, so there are no orphaned vectors and no labels describing a version of a row that no longer exists.

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 Push cleansed, deduplicated golden records and survivorship results from Reltio back into CRM and ERP systems so every app works from the mastered record.
  • 04 Sync Relations (affiliations, hierarchies, households) between Reltio and a CRM or graph so account and affiliation structures stay aligned.

Common sync patterns

Run the AI on current data

Rows created or changed in Reltio flow into Autopilot as they happen, so embeddings, classifications, and prompts run on the latest records instead of a nightly snapshot.

Write results back onto the record

Scores, labels, extracted fields, or generated text produced in Autopilot land on the matching row in Reltio, next to the source data your applications already query.

Keep derived data fresh as sources change

When a row in Reltio is updated or removed, its counterpart in Autopilot is updated or removed too, so nothing in Autopilot describes a record that has since changed or gone.

What you can sync between Autopilot and Reltio

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 Reltio objects How this pairing syncs
Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. Reference Data (RDM) Managed lookup and reference values (country codes, standardized values, hierarchies); read and updated so downstream systems share consistent reference data. Lists is specific to Autopilot and Reference Data (RDM) to Reltio — 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. Entities Golden records for each configured entity type (for example Organization, Individual/Contact, Location, or Product); full CRUD via /entities, so records are created, updated, and deleted, and Reltio matches and merges them by survivorship rules. Custom Fields is specific to Autopilot and Entities to Reltio — 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. Relations Typed relationships between two entities (affiliations, hierarchies, employment, households); read and written via /relations to keep account hierarchies and affiliation graphs aligned across systems. Smart Segments is specific to Autopilot and Relations to Reltio — 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. Crosswalks Per-entity references to the source systems and their record IDs; written when loading records so Reltio ties each source contribution to a golden record, and read to trace lineage back to origin systems. Journeys (Triggers) is specific to Autopilot and Crosswalks to Reltio — 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. Interactions Transactional or event records linked to entities (purchases, visits, activities); read and written via /interactions to enrich profiles and power 360-degree reporting. Activities is specific to Autopilot and Interactions to Reltio — 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. Matches (Potential Matches) Candidate duplicate pairs produced by match rules; read to review, and resolved with merge, unmerge, or not-a-match actions to control survivorship. Contacts is specific to Autopilot and Matches (Potential Matches) to Reltio — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Reltio

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

Reltio Autopilot Interval-based propagation

DetectionStacksync polls Reltio for changes on an incremental schedule, reading only records changed since the previous pass. Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored.

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.
  • Reltio: Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
What ships with Autopilot ⇄ Reltio

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Reltio

Integration surface
Reltio REST API (Data API) — /entities, /relations, /interactions, /activities, plus Match, RDM (reference data), and Data Change Request endpoints; base URL https://{environment}.reltio.com/reltio/api/{tenantId}
Authentication
OAuth 2.0 bearer tokens obtained from Reltio's central auth server (POST https://auth.reltio.com/oauth/token, client-credentials or password grant, application/x-www-form-urlencoded) and sent as Authorization: Bearer <token>; access tokens expire after about 60 minutes and are renewed with a refresh token, and are scoped per API (entities_api, relations_api, interactions_api, configuration_api, graphs_api)
Change detection
Polling the REST API on updateTime (epoch-ms), for example filter=gt(updateTime,<timestamp>), for entities and relations changed past a stored watermark. Reltio has no CDC log external tools consume; separately, Reltio's event streaming can publish entity change events (created, changed, removed) to a customer-configured message queue (Amazon SQS/SNS, Google Pub/Sub, Azure Service Bus, or Kafka), which is a queue feed rather than HTTP webhooks.
Capabilities
read · write
Rate limits
Reltio applies per-tenant API throttling and returns HTTP 429 (Too Many Requests) when limits are exceeded; there is no single fixed request-per-second cap published for all tenants, and throttling is tuned per tenant and environment. Large loads and reads use bulk create/update and the asynchronous export/jobs API rather than row-by-row calls.
How it works

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

    Choose tables

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

Autopilot and Reltio 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 404 integrations available for Autopilot and Reltio.

Popular · 7 of 404
All Autopilot integrations All Reltio 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