Skip to content
AI ⇄ ERP

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

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

Ground Autopilot on the customers, suppliers, items, and transactions that live in Linnworks, 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. Linnworks 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 Linnworks where the business is run.

Stacksync connects Contacts, Lists, Custom Fields, Smart Segments in Autopilot with Stock Levels, Locations, Purchase Orders, Suppliers in Linnworks and keeps the two sides in sync in real time. Stock Levels, Locations, Purchase Orders, Suppliers from Linnworks 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 Linnworks. 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 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 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
  • 04 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels

Common sync patterns

Derived fields back on the record

Categories, scores, or extracted values produced in Autopilot sync onto the matching record in Linnworks, where operations and finance teams see and act on them without leaving the ERP.

Continuous freshness, no reload

As records are created or corrected in Linnworks, the copy held in Autopilot updates within seconds, so the model side never reasons over stale ERP data.

One consistent identity across both systems

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

What you can sync between Autopilot and Linnworks

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 Linnworks objects How this pairing syncs
Custom Fields User-defined contact properties (string, number, date, boolean); discovered so field keys map cleanly to destination columns. Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. Custom Fields is specific to Autopilot and Open Orders to Linnworks — 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. Processed Orders Completed orders feed accounting and warehouse-based margin reporting. Smart Segments is specific to Autopilot and Processed Orders to Linnworks — 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 Items SKU records keep product data aligned with ERPs and PIMs. Journeys (Triggers) is specific to Autopilot and Stock Items to Linnworks — 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. Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. Activities is specific to Autopilot and Stock Levels to Linnworks — 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. Locations Warehouse and fulfillment location records scope stock data during mapping. Contacts is specific to Autopilot and Locations to Linnworks — 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. Purchase Orders Replenishment POs sync with suppliers and accounting systems. Lists is specific to Autopilot and Purchase Orders to Linnworks — each maps to any object or custom field on the other side.

How changes propagate between Autopilot and Linnworks

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

Linnworks Autopilot Interval-based propagation

DetectionStacksync polls Linnworks for changes on an incremental schedule, reading only records changed since the previous pass. Polling on order and stock endpoints.

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.
  • Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Autopilot ⇄ Linnworks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

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

Linnworks

Integration surface
REST API
Authentication
Application credentials and an install token exchanged for a session token
Change detection
Polling on order and stock endpoints
Capabilities
read · write
Rate limits
Per-endpoint rate limits apply on the Linnworks API
How it works

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

    Choose tables

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

Autopilot and Linnworks 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 477 integrations available for Autopilot and Linnworks.

Popular · 6 of 477
All Autopilot integrations All Linnworks 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