Real-time
Real-time sync
Changes in 6sense or Linnworks instantly reflect in both systems. No stale data, no manual imports.
CRM ⇄ ERP
6sense to Linnworks integration — real-time data sync
Keep 6sense 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 6sense and Linnworks
Flow 6sense data into Linnworks in real time — no exports, no schedulers, no custom scripts.
6sense is a read-only source: Stacksync reads its data in real time and delivers it into Linnworks, so Linnworks always reflects the current state of 6sense — without exports, scripts, or schedulers.
6sense 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.
Common use cases
- 01 Sync 6sense buying stage and intent scores onto CRM accounts so sellers prioritize in-market targets.
- 02 Pull segment membership into a marketing automation platform to trigger campaigns when accounts enter a segment.
- 03 Sync orders from Linnworks into an ERP or accounting system as they are processed, without CSV exports
- 04 Keep stock levels consistent between Linnworks and external systems so multichannel listings stay aligned with sellable stock
Common sync patterns
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 6sense aligned
Owners, territories, and org structure informed by Linnworks stay current in 6sense.
Where Linnworks handles order-to-cash: closed-won flows through
A deal won in 6sense creates or updates the customer in Linnworks with clean data, so fulfillment and invoicing start without re-entry.
What you can sync between 6sense 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.
| 6sense objects | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Segments Dynamic account lists built from intent and fit criteria, read out to drive targeting. | Shipping Services Carrier and service definitions support label and tracking data in order syncs. | Segments is specific to 6sense and Shipping Services to Linnworks — each maps to any object or custom field on the other side. | |
| Buying Stage Scores Model-predicted stage per account, synced onto CRM records for prioritization. | Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Buying Stage Scores is specific to 6sense and Open Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Intent Signals Keyword-level research activity used to flag in-market accounts. | Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Intent Signals is specific to 6sense and Processed Orders to Linnworks — each maps to any object or custom field on the other side. | |
| People / Contacts Persona and contact data surfaced for accounts, used to build outreach lists. | Stock Items SKU records keep product data aligned with ERPs and PIMs. | People / Contacts is specific to 6sense and Stock Items to Linnworks — each maps to any object or custom field on the other side. | |
| Reach Scores Model scores reflecting the level and recency of outreach to an account or contact, used to prioritize follow-up. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Reach Scores is specific to 6sense and Stock Levels to Linnworks — each maps to any object or custom field on the other side. | |
| Accounts Company records enriched with firmographics and intent data, matched to CRM accounts. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Accounts is specific to 6sense and Locations to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between 6sense 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.
6sense Linnworks Interval-based propagation
DetectionStacksync polls 6sense for changes on an incremental schedule, reading only records changed since the previous pass. Polling.
DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks 6sense 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.
Delivery6sense does not accept inbound record writes, so this direction carries requests rather than records: 6sense's output flows back as field updates on the originating Linnworks records.
Rate-limit considerations
- 6sense: Subject to the platform's API rate limits, which vary by contracted API package.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with 6sense ⇄ Linnworks
Connect 6sense and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every 6sense–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever 6sense 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 6sense or Linnworks record.
Observability
Monitoring
Track your 6sense ⇄ Linnworks sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between 6sense and Linnworks.
How the 6sense and Linnworks connectors work
6sense
- Integration surface
- REST API
- Authentication
- API key (token passed in request headers)
- Change detection
- Polling; scores and segment membership are typically refreshed on the platform's model update cadence
- Capabilities
- read
- Rate limits
- Subject to the platform's API rate limits, which vary by contracted API package
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 6sense 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.
- 01
Connect your apps
Authenticate 6sense 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.
6sense
connected
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the 6sense 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.
objects · 6sense ⇄ LinnworksCustomers 12,480Sales Orders 8,213Invoices 5,902Items 1,344 - 03
Map fields
Fields map automatically even when names and types differ. Stacksync handles transformation and type casting for you, zero configuration required.
6sense LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
6sense and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time integration between 6sense and Linnworks — 6sense is a read-only source, so data flows from it into the other system: authenticate both systems, choose the objects to sync, map fields visually, and changes propagate in milliseconds — no code required.
-
On the 6sense side: Intent Signals, People / Contacts, Reach Scores, Accounts, plus custom fields where 6sense exposes them. On the Linnworks side: Channel Listings, Returns & Refunds, Shipping Services, Open Orders. Stacksync auto-detects both schemas and converts types between the two systems.
-
6sense is a read-only source, so this integration runs one-way: Stacksync reads from 6sense in real time and delivers into Linnworks. Field mapping and monitoring work the same as for two-way pairs.
-
Common patterns for 6sense and Linnworks: One customer master; Where Linnworks manages people and org data: keep 6sense aligned; Where Linnworks handles order-to-cash: closed-won flows through. Where both systems keep customer or organization records, corrections in either propagate to the other, ending dual maintenance.
-
6sense: REST API. Authentication: API key (token passed in request headers). Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Stacksync manages authentication, retries, and rate limits on both sides.
-
6sense: Segments are dynamic: accounts enter and leave based on intent and fit criteria, so integrations re-read membership rather than treating lists as static. Linnworks: The Linnworks API uses a token-exchange model: application credentials plus a per-account install token are exchanged for a session token that authorizes subsequent calls. Stacksync's field mapping accounts for these differences between 6sense and Linnworks without custom code.
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.
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:
Related integrations
Every pair below is a real-time, two-way sync. Search all 432 integrations available for 6sense and Linnworks.
Popular · 2 of 432
No integrations match .
