Skip to content
AI ⇄ CRM

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

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

Write what Autopilot computes onto the contacts, accounts, and deals in Salesforce, and feed Salesforce'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 Salesforce, 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 Salesforce.

Stacksync connects Custom Fields, Smart Segments, Journeys (Triggers), Activities in Autopilot to Opportunities, Cases, Campaigns, Tasks and Events in Salesforce with bi-directional, real-time sync. Records and fields from Salesforce 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 Salesforce, 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 Salesforce stays the record of the customer while Autopilot stays where the computation happens.

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 Trigger provisioning or billing changes in an operational database when an Opportunity moves to closed-won.
  • 04 Consolidate multiple Salesforce orgs into a single database for cross-org reporting after an acquisition.

Common sync patterns

Where Autopilot classifies or tags: labels sync onto the record

Categories, sentiment, or intent produced in Autopilot attach to the right contact, account, or deal in Salesforce, keeping segmentation current as new data arrives.

Where Autopilot indexes records for retrieval: Salesforce keeps it fresh

Contacts, accounts, and notes from Salesforce 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 Salesforce, next to the relationship they describe.

What you can sync between Autopilot and Salesforce

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 Salesforce objects How this pairing syncs
Contacts Core people records (email, name, custom fields, list and segment membership); upserted two-way as the primary sync object. Contacts People linked to Accounts; synced two-way with marketing, support, and warehouse person records. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions. Custom fields on either side are included in the mapping.
Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. Opportunities Deal records with stage and amount; synced to databases for pipeline reporting and to ERPs at close. Lists is specific to Autopilot and Opportunities to Salesforce — 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. Cases Support records; synced with help desk tools or internal databases for escalation workflows. Custom Fields is specific to Autopilot and Cases to Salesforce — 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. Campaigns Marketing membership data; read out for attribution analysis in the warehouse. Smart Segments is specific to Autopilot and Campaigns to Salesforce — 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. Tasks and Events Activity records; usually read-only in syncs to feed activity reporting. Journeys (Triggers) is specific to Autopilot and Tasks and Events to Salesforce — 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. Products and Price Books Catalog and pricing data; commonly mastered in an ERP and written into Salesforce. Activities is specific to Autopilot and Products and Price Books to Salesforce — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Salesforce

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

Salesforce Autopilot Sub-second propagation

DetectionChanges in Salesforce are captured at the source via change data capture — no polling loop against its API. Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting).

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.
  • Salesforce: Daily API request allocations vary by edition and license count.
What ships with Autopilot ⇄ Salesforce

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Salesforce

Integration surface
REST, SOAP, and Bulk APIs
Authentication
OAuth login via a Salesforce user (browser-based authorization flow); requires "API Enabled" permission for polling mode, plus "Author Apex" and "Customize Application" OR "Modify All Data" for trigger mode
Change detection
Apex triggers are used whenever possible (Salesforce actively notifies Stacksync via an Apex trigger + callout class + remote site setting)
Capabilities
read · write · CDC
Rate limits
Daily API request allocations vary by edition and license count.
Salesforce setup guide
How it works

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

    Choose tables

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

Autopilot and Salesforce 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 510 integrations available for Autopilot and Salesforce.

Popular · 8 of 510
All Autopilot integrations All Salesforce 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