Skip to content
CRM ⇄ ERP

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

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

Close the gap between front office and back office: Close and Linnworks share customers and status in real time, in both directions.

Close holds the customer relationship; Linnworks runs the operations and records behind the business. The two overlap wherever the same organizations and transactions matter to both, and when that overlap is bridged by re-keying or overnight batch, each side spends the day working from stale data.

Stacksync syncs Tasks, Custom Activities, Custom Fields, Users in Close with Channel Listings, Returns & Refunds, Shipping Services, Open Orders in Linnworks field by field, in real time, and in both directions. You decide which system owns which fields; Stacksync keeps every copy consistent and resolves conflicts by rules you set.

Common use cases

  • Two-way sync between Close and a billing or ERP system so closed-won opportunities create customers and invoices automatically.
  • Keep Close contacts aligned with a marketing automation platform so outreach lists stay current.
  • Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
  • Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock

One customer master

Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.

Where Linnworks manages people and org data: keep Close aligned

Owners, territories, and org structure informed by Linnworks stay current in Close.

Where Linnworks handles order-to-cash: closed-won flows through

A deal won in Close creates or updates the customer in Linnworks with clean data, so fulfillment and invoicing start without re-entry.

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

Close objects Linnworks objects
Custom Activities User-defined activity types with their own custom fields, mapped like standard activities. Locations Warehouse and fulfillment location records scope stock data during mapping.
Custom Fields Org-specific fields on leads, contacts, and opportunities; addressed by stable field ids in syncs. Purchase Orders Replenishment POs sync with suppliers and accounting systems.
Users Sales reps referenced as owners on leads, opportunities, and activities. Suppliers Vendor records keep procurement data consistent across tools.
Smart Views Saved lead searches that can scope which records a segment-based sync pulls. Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs.
Leads The top-level record in Close; represents a company and holds its contacts, opportunities, and activity history. Returns & Refunds Post-sale records flow to finance and support systems.
Contacts People nested under a lead, with emails and phone numbers used for outreach syncs. Shipping Services Carrier and service definitions support label and tracking data in order syncs.
What ships with Close ⇄ Linnworks

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

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

Real-time

Two-way sync

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

No-code + pro-code

Workflow automation

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

Observability

Monitoring

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

Trading partners

EDI

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

How the Close and Linnworks connectors work

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

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

    Choose tables

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

Close and Linnworks integration FAQ

SECURITY

Security teams love 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 386 integrations available for Close and Linnworks.

Popular · 8 of 386
All Close 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