# Linnworks

## Overview

The **Linnworks Connector** in **DBSync Cloud Workflow** enables secure and automated integration between **Linnworks** - a cloud-based order and inventory management platform - and other enterprise systems.

This connector allows you to synchronize inventory, orders, and other key data between Linnworks and your external systems. By automating these flows, organizations reduce manual effort, maintain accurate data across channels, and improve operational efficiency.

## Key Benefits

**For Business Users:**

* **Unified Operations Data:** Keep inventory, orders, listings, and fulfillment data aligned across systems.
* **Process Automation:** Eliminate repetitive data exports and imports with scheduled or event-driven workflows.
* **Better Visibility:** Accurate real-time data supports smarter decision-making and reporting.

**For Technical Teams:**

* **Flexible Configuration:** Supports a broad set of Linnworks objects for mapping in workflows.
* **Workflow-Based Triggers:** Configure workflows to launch automated processes across multiple systems.

## Prerequisites

Before configuring the Linnworks Connector, ensure the following prerequisites are met:

1. **DBSync Access**

* A valid license for this connector and access to the DBSync Cloud Workflow platform.

2. **Linnworks Account**

* An active Linnworks subscription with API access enabled and sufficient permissions for the objects you plan to sync.

## Connector Configuration

Each Linnworks connector instance represents a connection to a specific Linnworks account/environment. To integrate multiple environments (For example, sandbox vs production), create separate connector entries.

After configuring the credentials, you can test the connection to validate access and permissions.

## Quick Setup Guide

{% stepper %}
{% step %}

### Login to DBSync Cloud Workflow

* Use your DBSync credentials to access the platform.
  {% endstep %}

{% step %}

### Add the Linnworks Connector

* Navigate to the connectors list in the Apps pane and select **Linnworks** from the Apps list.
  {% endstep %}

{% step %}

### Authenticate

* Click **Login to Linnworks**. 

<figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FkuKfUsLlLJVGtF2H8n3y%2Fimage.png?alt=media&#x26;token=bebc0ebb-3724-469c-a941-964b56dca25c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Authorize

* Log in to your Linnworks account and approve access for DBSync.

  <figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FqyVmWZsBWeI1AATtauOP%2Fimage.png?alt=media&#x26;token=ff157efc-a2b6-4550-807a-b50d1cf5c314" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Test Connection

* Use **Test Connection** to verify credentials and API access.

  <figure><img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FzL5jowBweEHMQPMVeowJ%2Fimage.png?alt=media&#x26;token=b29a7486-6985-4437-b6c8-690837d1039a" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Save Configuration

* Once validated, save the connector.
  {% endstep %}
  {% endstepper %}

After setup, Linnworks objects are available to use in workflows for triggers, mapping, and data sync tasks.

#### **Create a Flow**

* Drag and drop a Flow action into the Flow Builder.
* Click **Configure** to provide a description for the flow, such as Sync Linnworks Orders.

#### Add Query Action

* Add a Query action to your flow to specify what data you want to pull from Linnworks, such as orders or products.
* Configure the query by selecting the Linnworks connector as the source and specify the object (For example, Orders).

#### Map Fields

If you send data to another application (For example, QuickBooks), add a Transform and Write action to map the fields from Linnworks to the target application.

#### Run the Integration

Click Run <img src="https://1036205596-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fv9avy716UiAsS24zOznZ%2Fuploads%2FEmiOZJxzJ5S5UT99xnH6%2Funknown.png?alt=media&#x26;token=1d470f89-ab27-43b3-b415-7881deb04ec2" alt="" data-size="line"> to execute the integration. Monitor the console output for any errors or confirmation messages.

#### Debugging

If you encounter issues, add a Debug action to inspect the processed data. This can help identify any discrepancies in the integration.

#### Review Results

After running the integration, check the console output to ensure that the data from Linnworks is being processed correctly.

{% hint style="info" %}
PRO TIP

**Automate Regular Syncs:** Set up scheduled tasks to automate regular synchronization between Linnworks and other systems, ensuring data is always up-to-date without manual intervention.
{% endhint %}

## Common Use Cases

The Linnworks Connector supports a wide range of commerce automation scenarios:

* **Inventory Sync** Keep stock levels up-to-date between channels, ERP, and inventory systems.
* **Order Integration** Push marketplace and store orders into back-office systems for fulfillment and financial processing.
* **Price & Listing Updates** Sync price changes and listing updates between inventory management and sales channels.
* **Shipping & Fulfillment Tracking** Reflect shipment status and tracking details across platforms.
* **Returns & Adjustments** Automate inventory and order adjustments based on returns or corrections.

## Frequently Asked Questions (FAQ)

<details>

<summary>Can I connect multiple Linnworks environments?</summary>

Yes, create separate connector configurations for each Linnworks environment you need to integrate.

</details>

<details>

<summary>Is the connection secure?</summary>

Yes, the connector uses encrypted credentials and secure API authentication mechanisms.

</details>

<details>

<summary>Can workflows be triggered based on Linnworks events?</summary>

Workflows can be configured to run on schedules or triggers such as order creation or status updates.

</details>

<details>

<summary>Does the connector support custom attributes?</summary>

Yes, object fields and custom attributes exposed via the Linnworks API can be mapped within workflows.

</details>

<details>

<summary>Can data sync be bi-directional?</summary>

Yes, workflows can be configured for one-way or two-way synchronization between Linnworks and connected systems.

</details>

## Summary

The **Linnworks Connector** in **DBSync Cloud Workflow** provides a robust and flexible integration solution for synchronizing commerce operations data between Linnworks and your enterprise systems. With support for orders, inventory, listings, and fulfillment objects - and the ability to automate workflows across platforms - this connector helps streamline operations, improve data accuracy, and accelerate business processes.

## Related Content

[Error logs:](https://docs.mydbsync.com/cloud-workflow/create-your-workflow/actions/flow-management/logs) Resolve common integration errors by viewing the logs.

[Monitoring and Alerts Setup](https://docs.mydbsync.com/cloud-workflow/create-your-workflow/actions/flow-management/notification): Set up alerts to monitor your workflows proactively.

[Scheduler](https://docs.mydbsync.com/cloud-workflow/create-your-workflow/actions/flow-management/schedule): By setting up a schedule, you can ensure that your workflows run automatically without manual intervention, helping you manage recurring tasks efficiently.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mydbsync.com/cloud-workflow/2026_connectors_new/linnworks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.