Skip to content
AI ⇄ CRM

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

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

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

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

Common use cases

  • 01 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.
  • 02 Add contacts to a Journey from a database event or CRM stage change to start automated onboarding or nurture sequences.
  • 03 Sync Close leads and opportunities into Postgres or a warehouse for pipeline reporting outside Close's built-in reports.
  • 04 Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.

Common sync patterns

Where Autopilot indexes records for retrieval: Close keeps it fresh

Contacts, accounts, and notes from Close 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 Close, 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 Close, and refreshes keep them from going stale.

What you can sync between Autopilot and Close

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 Close 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 nested under a lead, with emails and phone numbers used for outreach syncs. 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.
Custom Fields User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns. Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Activities Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting. Activities Calls, emails, SMS, notes, and meetings logged against a lead; the source for engagement analytics. Same entity on both sides — records pair one-to-one and field-level changes reconcile in both directions.
Lists Static contact lists; membership is readable per list and writable by adding or removing contacts. Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Lists is specific to Autopilot and Custom Activities to Close — 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. Users Sales reps referenced as owners on leads, opportunities, and activities. Smart Segments is specific to Autopilot and Users to Close — 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. Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Journeys (Triggers) is specific to Autopilot and Smart Views to Close — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Close

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

Close Autopilot Sub-second propagation

DetectionClose notifies Stacksync of record changes through webhook events. Webhook subscriptions for record events, with polling on date_updated fields for backfills.

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.
  • Close: Subject to per-endpoint rate limits communicated in response headers.
What ships with Autopilot ⇄ Close

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Close

Integration surface
REST API
Authentication
API key (sent via HTTP Basic auth)
Change detection
Webhook subscriptions for record events, with polling on date_updated fields for backfills
Capabilities
read · write · webhooks
Rate limits
Subject to per-endpoint rate limits communicated in response headers
How it works

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

    Choose tables

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

Autopilot and Close 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 502 integrations available for Autopilot and Close.

Popular · 8 of 502
All Autopilot integrations All Close 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