Skip to content
AI ⇄ ERP

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

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

Ground Autopilot on the customers, suppliers, items, and transactions that live in Cin7, and write the classifications, scores, and extracted fields Autopilot produces back onto those records in real time.

An AI system does not keep customers, orders, or invoices the way an ERP does. What it keeps is derived: the vectors and metadata in a store, or the classifications, extracted fields, and generated text a model produces over records it was handed. Cin7 is where those source records actually live, across finance, operations, procurement, and inventory, and that data usually stays behind a strict API with many record types. Whatever Autopilot produces, whether a category, a risk flag, an extracted value, or an embedding, only earns its keep when it lands back on the record in Cin7 where the business is run.

Stacksync connects Contacts, Lists, Custom Fields, Smart Segments in Autopilot with Products, Inventory levels, Sales orders, Purchase orders in Cin7 and keeps the two sides in sync in real time. Products, Inventory levels, Sales orders, Purchase orders from Cin7 replicate into Autopilot continuously, so retrieval, classification, and reasoning run against current ERP records instead of last night's extract, and the fields Autopilot generates sync back onto the matching record in Cin7. Mapping is field-level, matching is on identifiers you choose, and Stacksync handles the ERP's API limits and schema drift, so there is no extraction pipeline to build or babysit.

Because every AI-side item carries the key of the record it came from, results always resolve to the right customer, supplier, or transaction. Autopilot reasons over the business as it actually is within seconds of a change, and the people running operations act on model output where they already work, without exporting a file or logging into a second system.

Common use cases

  • 01 Mirror List and Smart Segment membership into a warehouse to power attribution and audience analytics alongside other sources.
  • 02 Stream Activities into a warehouse so opens, clicks, and journey steps sit next to product and revenue data for lifecycle reporting.
  • 03 Write purchase orders created in a planning tool back into Cin7 for receiving.
  • 04 Consolidate stock movements from multiple branches into one reporting database.

Common sync patterns

One consistent identity across both systems

A customer, supplier, item, or transaction in Cin7 maps to the corresponding entry in Autopilot, so every AI result attaches to the right entity on both sides.

Document extraction round-trip

Purchase orders, invoices, or other documents flow from Cin7 into Autopilot for parsing or classification, and the structured result returns to the record it came from.

ERP records as live context

Customers, suppliers, items, and transactions from Cin7 replicate into Autopilot as they change, so search, retrieval, and reasoning run against current records rather than a periodic extract.

What you can sync between Autopilot and Cin7

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 Cin7 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 Customers and suppliers, matched to CRM records to keep account data consistent. 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.
Activities Per-contact activity and event history (opens, clicks, journey steps); read-only feed used for engagement reporting. Inventory levels Stock on hand by branch or location, published outward for availability. Activities is specific to Autopilot and Inventory levels to Cin7 — 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. Sales orders Orders captured from all channels; the main object for fulfillment and revenue syncs. Lists is specific to Autopilot and Sales orders to Cin7 — 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. Purchase orders Supplier orders synced with procurement and accounting workflows. Custom Fields is specific to Autopilot and Purchase orders to Cin7 — 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. Branches / locations Warehouse entities that scope every stock movement and order allocation. Smart Segments is specific to Autopilot and Branches / locations to Cin7 — 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. Stock adjustments and transfers Inventory movements read for audit and reconciliation reporting. Journeys (Triggers) is specific to Autopilot and Stock adjustments and transfers to Cin7 — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Cin7

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

Cin7 Autopilot Sub-second propagation

DetectionCin7 notifies Stacksync of record changes through webhook events. Polling on modified-date filters.

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.
  • Cin7: Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core.
What ships with Autopilot ⇄ Cin7

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Cin7

Integration surface
REST API; note that Cin7 Omni and Cin7 Core (formerly DEAR Systems) are separate products with separate APIs
Authentication
API key credentials (paired with a username or account ID, depending on the product)
Change detection
Polling on modified-date filters; webhook support exists on some editions for order and stock events
Capabilities
read · write · webhooks
Rate limits
Subject to per-account API rate limits that differ between Cin7 Omni and Cin7 Core
How it works

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

    Choose tables

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

Autopilot and Cin7 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 473 integrations available for Autopilot and Cin7.

Popular · 7 of 473
All Autopilot integrations All Cin7 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