Skip to content
Business productivity ⇄ ERP

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

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

Bridge the tools people work in and the system the business runs on: real-time, two-way sync between Agiloft and Linnworks.

The ERP holds the records the business is run on, and it is rarely where day-to-day work happens. Agiloft is closer to the work, and the two often need the same facts about the same people, organizations, and transactions. Bridging them by hand, or by nightly file transfer, leaves each side out of date for hours at a time.

Stacksync syncs Custom tables, Contracts, Companies, People in Agiloft with Processed Orders, Stock Items, Stock Levels, Locations in Linnworks bi-directionally and in real time, with field-level mapping and rules for which system wins on conflict. Changes made where the work happens reach the system of record within seconds, and the reverse.

Common use cases

  • 01 Write contract or company records into Agiloft when a deal closes in the CRM to kick off downstream legal and procurement workflows.
  • 02 Two-way sync Contracts between Agiloft and an ERP or warehouse so value, renewal dates, and status stay current without manual re-keying.
  • 03 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
  • 04 Push customer and order data to a CRM or marketing platform for post-purchase campaigns

Common sync patterns

Master data corrections travel

A customer, supplier, or contact detail corrected in either system updates the other, ending duplicate maintenance.

Where Agiloft faces customers and Linnworks carries account records

Order, invoice, or account status from Linnworks appears alongside the customer in Agiloft, so front-line teams answer from live data.

Where Agiloft collects payments: transactions post through

Payment events sync into Linnworks as they occur, keeping the enterprise records current without manual entry.

What you can sync between Agiloft 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.

Agiloft objects Linnworks objects How this pairing syncs
Companies Records for every organization - counterparties, vendors, customers - linked to contracts and people; read and written to keep account master data aligned with a CRM or ERP. Returns & Refunds Post-sale records flow to finance and support systems. Companies is specific to Agiloft and Returns & Refunds to Linnworks — each maps to any object or custom field on the other side.
People Parent table for individuals, split into Employees (internal users) and Contacts (external company contacts); synced to map signers, approvers, and account owners to CRM or HR records. Shipping Services Carrier and service definitions support label and tracking data in order syncs. People is specific to Agiloft and Shipping Services to Linnworks — each maps to any object or custom field on the other side.
Attachments File records holding the executed contract PDFs and supporting documents linked to a contract; read to pull signed files out, or written to push generated documents in. Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. Attachments is specific to Agiloft and Open Orders to Linnworks — each maps to any object or custom field on the other side.
Approvals Per-record approval instances generated from Approval Templates and Workflows; read to report approval status and cycle time, or written to trigger and record decisions. Processed Orders Completed orders feed accounting and warehouse-based margin reporting. Approvals is specific to Agiloft and Processed Orders to Linnworks — each maps to any object or custom field on the other side.
Tasks Assigned action items with owners, due dates, and states tied to contracts or projects; synced two-way to surface Agiloft work inside a PM or operations system. Stock Items SKU records keep product data aligned with ERPs and PIMs. Tasks is specific to Agiloft and Stock Items to Linnworks — each maps to any object or custom field on the other side.
Clause Library Reusable, approved contract clauses with metadata and categories; read to feed clause content into other systems or reporting, or maintained from an external source of truth. Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. Clause Library is specific to Agiloft and Stock Levels to Linnworks — each maps to any object or custom field on the other side.

How changes propagate between Agiloft 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.

Agiloft Linnworks Sub-second propagation

DetectionAgiloft notifies Stacksync of record changes through webhook events. Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL.

DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.

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

Rate-limit considerations

  • Agiloft: Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.
  • Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with Agiloft ⇄ Linnworks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

Track your Agiloft ⇄ Linnworks sync health, view errors, and replay failed events in one click.

Trading partners

EDI

Transform legacy EDI complexity into simple database interactions between Agiloft and Linnworks.

How the Agiloft and Linnworks connectors work

Agiloft

Integration surface
REST API (/ewws/rest/{kb}) and SOAP/EWS v2 web services (EWWSv2Service WSDL), plus a native Webhooks subscription API
Authentication
OAuth 2.0 via OAuth2 Client Setup - Authorization Code with PKCE for user-delegated apps and Client Credentials for machine-to-machine; also JWT tokens or Basic Auth with a session token from POST /ewws/rest/{kb}/login
Change detection
Native webhook subscriptions (POST /ewws/webhooks) fire on record create, edit, or delete after a GET handshake verifies the callback URL; otherwise poll each table by its Date Updated / modified-time fields. Agiloft has no database change-data-capture log.
Capabilities
read · write · webhooks
Rate limits
Agiloft publishes no fixed per-minute REST quota; throughput is instance-specific and bounded by license seats (Assigned/Floating Power User) and concurrent API sessions. Each SOAP/EWS call runs in its own transaction, and REST logins issue a session token meant to be reused rather than re-authenticated per call.

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 Agiloft 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 Agiloft 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
    Agiloft connected
    Linnworks connected
    OAuth 2.0
    SSH tunnel
    SSL certificate
    VPC peering
  2. 02

    Choose tables

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

Agiloft 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
CSA STAR
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 405 integrations available for Agiloft and Linnworks.

Popular · 3 of 405
All Agiloft 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