Skip to content
AI ⇄ CRM

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

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

Write what Autopilot computes onto the contacts, accounts, and deals in Clari, and feed Clari's records back into Autopilot, in real time and in both directions.

Autopilot turns data into something a revenue team can act on: scores, classifications, summaries, and embeddings. But the customers those results describe live in Clari, where reps and marketers actually work. Intelligence that stays inside Autopilot rarely reaches the record where a decision gets made, and Autopilot is only as sharp as the data it sees, which is also held in Clari.

Stacksync connects Journeys (Triggers), Activities, Contacts, Lists in Autopilot to Quota, Opportunities, Activity (Capture), Account field extensions in Clari with bi-directional, real-time sync. Records and fields from Clari flow into Autopilot as the material it scores, indexes, or enriches, and the values Autopilot produces flow back onto the matching contact, account, or deal in Clari, field by field, within seconds. There is no batch export in the middle and no glue code to maintain.

Because the mapping is field-level, you choose exactly which attributes cross and in which direction, so Clari stays the record of the customer while Autopilot stays where the computation happens.

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 Stream Audit Events into a reporting database to monitor forecast-submission changes and user activity for compliance.
  • 04 Pull Activity (Capture) meetings and emails, mapped to their accounts and opportunities, into a database for coverage and engagement analysis.

Common sync patterns

Where Autopilot indexes records for retrieval: Clari keeps it fresh

Contacts, accounts, and notes from Clari sync into Autopilot as they change, so embeddings or search stay aligned with the live CRM instead of a stale export.

Where Autopilot summarizes or drafts: text where reps read it

Summaries, next steps, or drafted messages generated in Autopilot write back onto the account or deal in Clari, next to the relationship they describe.

Where Autopilot enriches people or companies: fields fill in

Enriched attributes from Autopilot populate contact and company fields in Clari, and refreshes keep them from going stale.

What you can sync between Autopilot and Clari

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 Clari objects How this pairing syncs
Custom Fields User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns. Opportunity field extensions Warehouse-computed fields pushed onto Opportunity records via the ingest API; up to 100 records per request or 10MB bulk files. Custom Fields is specific to Autopilot and Opportunity field extensions to Clari — 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. Audit Events User edits and system events exported with filtering by actor, session, and date range; read-only feed for change tracking and compliance. Smart Segments is specific to Autopilot and Audit Events to Clari — 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. Forecast Exported per forecast tab and fiscal period via async jobs; includes submitted forecast calls, updates, manager adjustments, and CRM totals. Read-only. Journeys (Triggers) is specific to Autopilot and Forecast to Clari — 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. Quota Quota and quota-history values exported alongside forecast data, scoped by fiscal quarter; read-only, useful for warehouse attainment reporting. Activities is specific to Autopilot and Quota to Clari — 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. Opportunities Retrieved synchronously by ID from GET /opportunity (up to 100 IDs per call) with Clari CRM scoring and field-change history; read-only, mirroring the CRM opportunity Clari sits on. Contacts is specific to Autopilot and Opportunities to Clari — 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. Activity (Capture) Meetings, emails, and attachments captured by Clari and mapped to accounts and opportunities; exported read-only via async activity jobs. Lists is specific to Autopilot and Activity (Capture) to Clari — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Clari

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

Clari Autopilot Interval-based propagation

DetectionStacksync polls Clari for changes on an incremental schedule, reading only records changed since the previous pass. Polling — reads run as asynchronous export jobs (submit export, poll job status, download results).

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.
  • Clari: Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
What ships with Autopilot ⇄ Clari

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Clari

Integration surface
REST APIs on api.clari.com - Export API (v4, asynchronous bulk jobs for forecast, quota, activity, and audit) and Ingest API (v2, field extensions); Opportunity reads are synchronous via GET /opportunity
Authentication
API token in the apikey header, generated per user in Settings; ingest/partner endpoints also require a partnerkey header, and Copilot endpoints require X-Api-Key and X-Api-Password
Change detection
Polling — reads run as asynchronous export jobs (submit export, poll job status, download results); the ingest API supports an incremental mode for regular field updates. No webhooks.
Capabilities
read · write
Rate limits
Max 3 concurrent exports and roughly 1000 exports per rolling 30-day org window; ingestion capped at 100 requests/sec per API token.
How it works

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

    Choose tables

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

Autopilot and Clari 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 395 integrations available for Autopilot and Clari.

Popular · 7 of 395
All Autopilot integrations All Clari 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