Real-time
Two-way sync
Changes in Linnworks or Onelogin instantly reflect in both systems. No stale data, no manual imports.
ERP ⇄ Security and identity
Linnworks to Onelogin integration — real-time, two-way sync
Keep Linnworks and Onelogin 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 Onelogin
Keep the employee, group, and account records that Linnworks and Onelogin share aligned in real time, so a person added, moved, or offboarded in one system shows up correctly in the other within seconds.
An ERP and an identity system describe the same workforce from two angles. Linnworks holds the authoritative record of who works at the company, and often their department, title, manager, and cost center. Onelogin controls the accounts, groups, and access those same people use every day. When the two aren't connected, every hire, transfer, and departure has to be keyed twice, and the window between someone leaving in Linnworks and their account still being active in Onelogin is a real security exposure.
Stacksync syncs Locations, Purchase Orders, Suppliers, Channel Listings in Linnworks with Authentication factors (MFA), Custom user fields, Users, Roles in Onelogin in real time, with field-level mapping and conflict resolution in place of CSV exports and nightly jobs. A new hire, a department change, or a termination propagates within seconds, and where you want changes to flow both ways — the ERP's org data into the directory, account status back into the ERP — the same mapping handles it.
That matters most at offboarding and audit time. When the directory reflects the ERP's current headcount and org structure, disabling access no longer depends on someone remembering to update a second system, and access reviews start from a roster both sides already agree on.
Common use cases
- 01 Mirror processed orders, refunds, and returns into a warehouse for margin reporting across channels
- 02 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
- 03 Read the OneLogin Events audit log into a warehouse or SIEM for login analytics, access reviews, and SOC 2 audit evidence.
- 04 Keep Role membership aligned with application or database entitlement tables so each role's assigned users match who should hold that access.
Common sync patterns
Create accounts from new records
A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
Disable access at offboarding
When a person is marked terminated or inactive in one system, the matching account is disabled in the other within seconds, closing the gap that leaves ex-employees with live access.
Keep profile attributes current
A name, email, title, manager, or department corrected in either system updates the other, so directory entries and employee records don't drift apart.
What you can sync between Linnworks and Onelogin
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 | Onelogin objects | How this pairing syncs | |
|---|---|---|---|
| Channel Listings Marketplace and webstore listing mappings tie channel products to internal SKUs. | Users User accounts (email, username, custom attributes, status, roles); full CRUD via the v2 Users API - create, update, delete, set password, lock/unlock, and add or remove role assignments. | Channel Listings is specific to Linnworks and Users to Onelogin — each maps to any object or custom field on the other side. | |
| Returns & Refunds Post-sale records flow to finance and support systems. | Roles Roles that bundle app access; created, updated, and deleted via the Roles API, with users, admins, and apps assigned to each role. | Returns & Refunds is specific to Linnworks and Roles to Onelogin — each maps to any object or custom field on the other side. | |
| Shipping Services Carrier and service definitions support label and tracking data in order syncs. | Apps (app instances) Connected SAML/OIDC application configs on the account; create, update, delete, and assign to users and roles - the writable app catalog. | Shipping Services is specific to Linnworks and Apps (app instances) to Onelogin — each maps to any object or custom field on the other side. | |
| Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Groups Account groups used for mapping and reporting; listed and read through the API, which has no create or update endpoint, so groups are read-only. | Open Orders is specific to Linnworks and Groups to Onelogin — each maps to any object or custom field on the other side. | |
| Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Mappings (mapping rules) Attribute-driven rules that assign roles and app access; full CRUD via the Mappings API, then reapplied across matching users. | Processed Orders is specific to Linnworks and Mappings (mapping rules) to Onelogin — each maps to any object or custom field on the other side. | |
| Stock Items SKU records keep product data aligned with ERPs and PIMs. | Events Audit log of every authentication and admin action; read-only, filtered by since/until, and pushed live through the Event Webhook. | Stock Items is specific to Linnworks and Events to Onelogin — each maps to any object or custom field on the other side. |
How changes propagate between Linnworks and Onelogin
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 Onelogin 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 Onelogin through its API, with automatic retries and rate-limit backoff.
Onelogin Linnworks Sub-second propagation
DetectionOnelogin notifies Stacksync of record changes through webhook events. Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time.
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.
- Onelogin: Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
What ships with Linnworks ⇄ Onelogin
Connect Linnworks and Onelogin for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every Linnworks–Onelogin connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever Linnworks or Onelogin 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 Onelogin record.
Observability
Monitoring
Track your Linnworks ⇄ Onelogin 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 Onelogin.
How the Linnworks and Onelogin 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
Onelogin
- Integration surface
- OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery
- Authentication
- OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write.
- Change detection
- Event Webhook (Event Broadcaster) posts batches of Event objects to a registered endpoint in near real time; the Events API also supports polling with since/until time filters and pagination for historical backfill.
- Capabilities
- read · write · webhooks
- Rate limits
- Account-level limit of 5,000 API calls per hour shared across all access tokens; responses carry X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, over-limit calls return HTTP 429, and the count resets each hour. Paid plans can request an increase.
How it works
How to connect Linnworks to Onelogin — 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 Onelogin 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
Onelogin
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the Linnworks and Onelogin 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 ⇄ OneloginCustomers 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 OneloginCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
Linnworks and Onelogin integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between Linnworks and Onelogin: authenticate both systems, choose the objects to sync (such as Linnworks's Channel Listings and Returns & Refunds), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
On the Linnworks side: Locations, Purchase Orders, Suppliers, Channel Listings, plus custom fields where Linnworks exposes them. On the Onelogin side: Authentication factors (MFA), Custom user fields, Users, Roles. 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.
-
Common patterns for Linnworks and Onelogin: Create accounts from new records; Disable access at offboarding; Keep profile attributes current. A person added in one system gets a matching account or record in the other automatically, so a new hire can be granted access without anyone re-keying their details.
-
Linnworks: REST API. Authentication: Application credentials and an install token exchanged for a session token. Onelogin: OneLogin API (REST, v1 and v2 resource endpoints on <subdomain>.onelogin.com) plus the Event Webhook (Event Broadcaster) for event delivery. Authentication: OAuth 2.0 client credentials - an admin generates an API credential pair (client_id + client_secret) in the OneLogin portal and exchanges it at POST /auth/oauth2/v2/token for a bearer access token sent on every call; each credential carries a scope (Manage all, Manage users, Read users, etc.) that governs read vs write. Stacksync manages authentication, retries, and rate limits on both sides.
-
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. Onelogin: Users, Roles, Apps, and Mapping rules are the writable surface; Groups and the Events audit log are read-only through the OneLogin API. Stacksync's field mapping accounts for these differences between Linnworks and Onelogin 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 502 integrations available for Linnworks and Onelogin.
Popular · 7 of 502
-
Linnworks ⇄ Jumpcloud -
Linnworks ⇄ Active Directory - Linnworks ⇄ Azure Active Directory
-
Linnworks ⇄ Okta -
Onelogin ⇄ Odoo -
Onelogin ⇄ Blue Yonder WMS -
Onelogin ⇄ Brightpearl
No integrations match .
