Real-time
Two-way sync
Changes in D2l Brightspace or Linnworks instantly reflect in both systems. No stale data, no manual imports.
Human resources ⇄ ERP
D2l Brightspace to Linnworks integration — real-time, two-way sync
Keep D2l Brightspace 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 D2l Brightspace and Linnworks
Sync the workers, org structure, and cost centers that Linnworks and D2l Brightspace share in real time, so the people D2l Brightspace manages stay current in the system that runs finance and operations.
D2l Brightspace is the system of record for people: who was hired, which department and location they sit in, who they report to, and how they are paid. Linnworks runs finance and operations, and much of what it does depends on that same information, from booking labor cost to approving an expense report to staffing a project. Where the two are bridged by re-keying or an overnight file, each side spends the day out of step, with new hires missing from the systems they need and leavers still active where they should not be.
Stacksync syncs Suppliers, Channel Listings, Returns & Refunds, Shipping Services in Linnworks with Org Units, Grades, Content (Modules, Topics, and User Progress), Quizzes in D2l Brightspace field by field, in real time, and in both directions. You decide which system owns which fields, so the people side stays authoritative for worker data while Linnworks keeps its own accounting and operational detail, and every change made in one is reflected in the other within seconds instead of at the next batch run.
Common use cases
- 01 Sync product and listing data with a PIM so channel listings stay aligned with the catalog
- 02 Push customer and order data to a CRM or marketing platform for post-purchase campaigns
- 03 Sync Assignment (Dropbox) submissions and feedback into a reporting database or downstream review tool.
- 04 Two-way sync of Users and Enrollments between Brightspace and an SIS or HRIS so new learners and their course rosters stay aligned without manual CSV imports.
Common sync patterns
One org structure
Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Linnworks roll up to the same structure D2l Brightspace maintains.
Reporting lines drive approvals
Manager and reporting-hierarchy changes in D2l Brightspace keep expense and purchase approval chains in Linnworks pointed at the right people.
Where D2l Brightspace runs payroll: labor cost in the books
Pay and compensation data from D2l Brightspace posts into Linnworks as labor cost, so finance sees workforce spend without re-entering it by hand.
What you can sync between D2l Brightspace 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.
| D2l Brightspace objects | Linnworks objects | How this pairing syncs | |
|---|---|---|---|
| Assignments (Dropbox) Dropbox folders, submissions, and feedback; submission and evaluation data is read into reporting systems and feedback can be written back. | Shipping Services Carrier and service definitions support label and tracking data in order syncs. | Assignments (Dropbox) is specific to D2l Brightspace and Shipping Services to Linnworks — each maps to any object or custom field on the other side. | |
| Groups and Sections Group categories, groups, and section membership within an org unit; enrollments are read and written to keep cohort assignments aligned. | Open Orders Unshipped orders aggregated from sales channels sync into ERPs and fulfillment systems. | Groups and Sections is specific to D2l Brightspace and Open Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Users User accounts in the Learning Platform (lp) component; created, read, updated, and deleted through the Valence API and typically synced two-way with an SIS or HRIS. | Processed Orders Completed orders feed accounting and warehouse-based margin reporting. | Users is specific to D2l Brightspace and Processed Orders to Linnworks — each maps to any object or custom field on the other side. | |
| Enrollments Links between Users and Org Units; enroll/unenroll and batch-enrollment routes let rosters be written from an upstream system and read back for reporting. | Stock Items SKU records keep product data aligned with ERPs and PIMs. | Enrollments is specific to D2l Brightspace and Stock Items to Linnworks — each maps to any object or custom field on the other side. | |
| Org Units The org structure — course offerings, sections, departments, and semesters; read for hierarchy and created/updated to provision courses from a database. | Stock Levels Per-location quantities sync outward so channels and planning tools reflect current availability. | Org Units is specific to D2l Brightspace and Stock Levels to Linnworks — each maps to any object or custom field on the other side. | |
| Grades Grade objects, categories, schemes, and per-user grade values in the Learning Environment (le) component; values can be read out and written back onto the gradebook. | Locations Warehouse and fulfillment location records scope stock data during mapping. | Grades is specific to D2l Brightspace and Locations to Linnworks — each maps to any object or custom field on the other side. |
How changes propagate between D2l Brightspace 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.
D2l Brightspace Linnworks Sub-second propagation
DetectionD2l Brightspace notifies Stacksync of record changes through webhook events. Polling Valence endpoints with date/bookmark filters, differential Brightspace Data Sets (BDS) bulk exports for changed rows via the Data Hub, and.
DeliveryEach detected change is written to Linnworks through its API, with automatic retries and rate-limit backoff.
Linnworks D2l Brightspace 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 D2l Brightspace through its API, with automatic retries and rate-limit backoff.
Rate-limit considerations
- D2l Brightspace: Per-caller token-bucket credit scheme; each route costs credits, responses carry X-Rate-Limit-Remaining, and over-quota calls return HTTP 429. D2L can adjust per-route credit costs.
- Linnworks: Per-endpoint rate limits apply on the Linnworks API.
What ships with D2l Brightspace ⇄ Linnworks
Connect D2l Brightspace and Linnworks for flexible, real-time data sync.
Real-time sync, workflow automation, event queues, EDI, and monitoring, for every D2l Brightspace–Linnworks connection.
No-code + pro-code
Workflow automation
Trigger automated workflows whenever D2l Brightspace 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 D2l Brightspace or Linnworks record.
Observability
Monitoring
Track your D2l Brightspace ⇄ Linnworks sync health, view errors, and replay failed events in one click.
Trading partners
EDI
Transform legacy EDI complexity into simple database interactions between D2l Brightspace and Linnworks.
How the D2l Brightspace and Linnworks connectors work
D2l Brightspace
- Integration surface
- Brightspace (Valence) REST API split into independently-versioned Learning Platform (lp) and Learning Environment (le) components, plus the Data Hub / Data Export Framework and Brightspace Data Streams
- Authentication
- OAuth 2.0 authorization-code grant against the D2L auth service (auth.brightspace.com); a registered app holds a client ID and secret with per-scope grants (group:resource:action, e.g. users:userdata:read), short-lived access tokens, and refresh tokens
- Change detection
- Polling Valence endpoints with date/bookmark filters, differential Brightspace Data Sets (BDS) bulk exports for changed rows via the Data Hub, and Brightspace Data Streams webhooks (xAPI activity events) for near-real-time signals
- Capabilities
- read · write · webhooks
- Rate limits
- Per-caller token-bucket credit scheme; each route costs credits, responses carry X-Rate-Limit-Remaining, and over-quota calls return HTTP 429. D2L can adjust per-route credit costs.
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 D2l Brightspace 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 D2l Brightspace 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.
D2l Brightspace
connected
Linnworks
connected
OAuth 2.0SSH tunnelSSL certificateVPC peering - 02
Choose tables
Pick the D2l Brightspace 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 · D2l Brightspace ⇄ 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.
D2l Brightspace LinnworksCompany company_name textEmail email textAmount amount numericCreated created_at timestamp
FAQ
D2l Brightspace and Linnworks integration FAQ
-
Yes. Stacksync provides a managed, real-time two-way integration between D2l Brightspace and Linnworks: authenticate both systems, choose the objects to sync (such as D2l Brightspace's Assignments (Dropbox) and Groups and Sections), map fields visually, and changes propagate both ways in milliseconds — no code required.
-
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 D2l Brightspace and Linnworks: One org structure; Reporting lines drive approvals; Where D2l Brightspace runs payroll: labor cost in the books. Departments, cost centers, and locations that both systems reference stay in agreement, so labor cost, approvals, and reporting in Linnworks roll up to the same structure D2l Brightspace maintains.
-
D2l Brightspace: Brightspace (Valence) REST API split into independently-versioned Learning Platform (lp) and Learning Environment (le) components, plus the Data Hub / Data Export Framework and Brightspace Data Streams. Authentication: OAuth 2.0 authorization-code grant against the D2L auth service (auth.brightspace.com); a registered app holds a client ID and secret with per-scope grants (group:resource:action, e.g. users:userdata:read), short-lived access tokens, and refresh tokens. 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.
-
Linnworks: Orders are modeled in two populations, open orders and processed orders, and syncs typically treat processing as the state transition that moves a record between them. D2l Brightspace: The API is served per tenant from the institution's own Brightspace host (https://{host}/d2l/api/), so each customer has a distinct base URL and version set. Stacksync's field mapping accounts for these differences between D2l Brightspace and Linnworks without custom code.
-
Stacksync is SOC 2 Type II and ISO 27001 certified with HIPAA BAA support. Data is encrypted in transit, and a zero-persistent-storage architecture means D2l Brightspace and Linnworks records are not retained after a sync operation.
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 401 integrations available for D2l Brightspace and Linnworks.
Popular · 5 of 401
-
D2l Brightspace ⇄ Epicor ERP -
Linnworks ⇄ Ukg Pro -
Linnworks ⇄ Greenhouse -
Linnworks ⇄ Jobvite -
Linnworks ⇄ Lever
No integrations match .
