Real-time
Two-way sync
Changes in Linnworks or Splunk instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Analytics
Linnworks to Splunk integration — real-time, two-way sync
Keep Linnworks and Splunk 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 Linnworks and Splunk
Put Linnworks's records into Splunk as live data for reporting and dashboards, without nightly exports, and send the segments and metrics Splunk computes back where Linnworks can use them.
ERP data is some of the most requested data for analysis and some of the hardest to pull: the record types are many, the APIs are strict, and export jobs break on every upgrade. Whether Linnworks carries financials, operations, workforce data, or all three, those numbers belong in Splunk, next to the product, behavioral, and web data the team already measures.
Stacksync syncs Stock Items, Stock Levels, Locations, Purchase Orders from Linnworks into Splunk continuously, handling API limits and schema drift as it goes, so each record type arrives as Users and Roles, Dashboards, Search Results, Saved Searches ready to report on. The connection is bi-directional, so segments, scores, and metrics computed in Splunk can be written back to fields in Linnworks where that is useful.
Common use cases
- 01 Ingest application, CRM, or database records into Splunk via the HTTP Event Collector so operational data lands alongside logs for correlation and dashboards.
- 02 Read and write KV Store collections to keep Splunk lookups — asset inventories, allow/deny lists, enrichment tables — in sync with an external source of truth in both directions.
- 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
Where Linnworks runs order-to-cash: customer and account analytics
Orders, invoices, and account records from Linnworks join the behavioral and usage data Splunk already tracks, so customer analysis spans activity and dollars in one view.
Where Linnworks runs operations: inventory and fulfillment metrics
Operational records from Linnworks become measurable in Splunk, joinable with the rest of what the company tracks for supply and fulfillment reporting.
Where Linnworks is the HR system of record: workforce and cost analysis
Worker and organization data from Linnworks syncs into Splunk for headcount, cost, and utilization reporting alongside other company data.
What you can sync between Linnworks and Splunk
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.
| Linnworks objects | Splunk objects | How this pairing syncs | |
|---|---|---|---|
| Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | HTTP Event Collector The write-in path: POST events and metrics to /services/collector (port 8088, or 443 on Splunk Cloud) authenticated with a per-input HEC token, so external records are indexed alongside logs for search and correlation. | Open Orders is specific to Linnworks and HTTP Event Collector to Splunk — each maps to any object or custom field on the other side. | |
| Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Users and Roles Accounts at /services/authentication/users and role/capability definitions at /services/authorization/roles, with full CRUD; exported for access reviews or provisioned from an identity source of truth. | Processed Orders is specific to Linnworks and Users and Roles to Splunk — each maps to any object or custom field on the other side. | |
| Stock Items SKU records keep product data aligned with ERPs and PIMs. | Dashboards Simple XML dashboard and view definitions at /servicesNS/{owner}/{app}/data/ui/views; exported for backup and audit, or created and updated programmatically from version control. | Stock Items is specific to Linnworks and Dashboards to Splunk — each maps to any object or custom field on the other side. | |
| Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Search Results SPL searches dispatched via POST /services/search/jobs return a search ID (SID); results are pulled from /services/search/jobs/{sid}/results once the job completes, or synchronously via oneshot/export mode. The primary read path for streaming indexed events out to a warehouse. | Stock Levels is specific to Linnworks and Search Results to Splunk — each maps to any object or custom field on the other side. | |
| Locations Warehouse and fulfillment location records scope stock data during mapping. | Saved Searches Scheduled searches, reports, and the definitions behind alerts at /services/saved/searches with full create, update, and delete. Read out for governance and coverage review, or provisioned and updated from a config source. | Locations is specific to Linnworks and Saved Searches to Splunk — each maps to any object or custom field on the other side. | |
| Purchase Orders Replenishment POs sync with suppliers and accounting systems. | Fired Alerts Triggered alert instances listed at /services/alerts/fired_alerts; alert configuration (conditions, schedule, actions) lives on the corresponding saved search. Landed in a database for alert-trend and detection-coverage reporting. | Purchase Orders is specific to Linnworks and Fired Alerts to Splunk — each maps to any object or custom field on the other side. |
How changes propagate between Linnworks and Splunk
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.
Linnworks Splunk 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 Splunk through its API, with automatic retries and rate-limit backoff.
Splunk Linnworks Sub-second propagation
DetectionSplunk notifies Stacksync of record changes through webhook events. Time-range searches over indexed events (earliest/latest on _time or _indextime).
DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
- Splunk: The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
What ships with Linnworks ⇄ Splunk
Connect Linnworks and Splunk for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Splunk connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks or Splunk 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 Linnworks or Splunk record.
Observability
Monitoring
Track your Linnworks ⇄ Splunk sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between Linnworks and Splunk.
How the Linnworks and Splunk connectors work
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
Splunk
- Integration surface
- REST API (management API + HTTP Event Collector)
- Authentication
- HTTP Basic (username/password), or a session key from POST /services/auth/login sent as Authorization: Splunk <key>, or a bearer authentication token (Authorization: Bearer <token>). The HTTP Event Collector uses its own per-input token (Authorization: Splunk <hec-token>). Management API defaults to port 8089; HEC to port 8088 (443 on Splunk Cloud).
- Change detection
- Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action.
- Capabilities
- read · write · webhooks
- Rate limits
- The management REST API throttles through search-concurrency quotas — max concurrent searches per user and role, plus per-CPU historical search limits in limits.conf — rather than a fixed per-request rate; exceeding quota queues or blocks jobs. HEC has per-token and per-instance throughput limits, and Splunk Cloud adds ingestion and API limits on top.
How it works
How to connect Linnworks to Splunk — 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 Linnworks and Splunk with each platform's native method — OAuth, API keys, or service accounts — plus secure options like SSH tunneling, IP whitelisting, and VPC peering.
Linnworks
connected
Splunk
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks and Splunk 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 · Linnworks ⇄ SplunkCustomers 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.
Linnworks SplunkCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Splunk integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Splunk: authenticate both systems, choose the objects to sync (such as Linnworks's Open Orders and Processed Orders), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
Stacksync pricing is usage-based and starts at $1,000/month, including the managed Linnworks and Splunk connectors, real-time two-way sync, monitoring, and support. That replaces building and maintaining a custom Linnworks–Splunk integration in-house.
-
Yes — Stacksync ships production-grade connectors for both Linnworks and Splunk. The connectors handle authentication, schema detection, rate limits, and retries; you configure the sync, and Stacksync operates it.
-
Change detection on Linnworks: Polling on order and stock endpoints. On Splunk: Time-range searches over indexed events (earliest/latest on _time or _indextime); events are immutable once indexed, so incremental extraction advances a time cursor rather than a modified-date CDC feed. Config objects such as saved searches and KV Store are polled; alerts can push via a saved-search webhook action. Each detected change propagates to the other side in milliseconds, with field-level conflict resolution and an inspectable event log.
-
On the Splunk side: Users and Roles, Dashboards, Search Results, Saved Searches, plus custom fields where Splunk exposes them. On the Linnworks side: Stock Items, Stock Levels, Locations, Purchase Orders. Stacksync auto-detects both schemas and converts types between the two systems.
-
Yes. Each object mapping can be bidirectional or restricted to a single direction (both systems accept writes). Read-only mirrors, one-way pushes, and full two-way sync can be mixed in the same integration.
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 476 integrations available for Linnworks and Splunk.
Popular · 8 of 476
-
Linnworks ⇄ Microsoft Power Bi -
Linnworks ⇄ Tableau -
Linnworks ⇄ Adobeanalytics -
Linnworks ⇄ Pendo -
Splunk ⇄ Dynamics 365 F&O -
Splunk ⇄ SuiteAnalytics -
Splunk ⇄ Dynamics 365 Business Central -
Splunk ⇄ SAP Business ByDesign
No integrations match .
