Resources · Make integration

Order Desk Make integrationAutomate Order Desk with Make.

Can Make look after your Order Desk orders while you work on something else? The Order Desk Make integration gives you 26 modules: 4 instant triggers, 18 actions and 4 searches. This guide is for ops teams: link your store, then build a first scenario that files new orders.

Try the Order Desk integration on MakeSee the 26 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Order Desk Make integration automate?

The Order Desk Make integration links your Order Desk store to Make, a no-code tool where you build scenarios: chains of modules that each do one job. Order Desk brings 26 modules to that toolbox, with four instant triggers that react to orders and events, 18 actions on orders, items, shipments and stock, and four searches.

New orders filed the moment they arrive. Watch Orders picks up every order created outside Order Desk, and Change Orders Folder drops it into a review folder. Nobody has to sort the inbox by hand anymore.

Shipments followed from a simple folder move. When a teammate drags an order into a shipping folder, Watch Order Folder Changed fires. List Shipments then gathers the parcels of that order, ready to feed a customer message in another app.

Stock that stays in step with your catalog. A product shows up in another tool: Search Inventory Items checks whether Order Desk already knows it, then Create an Inventory Item or Update an Inventory Item does the rest.

One honest limit: the Make documentation for Order Desk is flagged as AI-generated from the vendor's docs and may contain mistakes, so confirm key details with Order Desk. When a run fails, the Make troubleshooting guide helps, and Make training covers the editor basics. Still weighing another tool? Read n8n vs Make.

Connect

How do you connect Order Desk to Make?

  1. 01

    Copy your Store ID and API key

    In Order Desk, open the Settings menu in the left sidebar, click Store Settings, then the API tab. Copy the Store ID and the API key shown on that page: Make asks for both.

  2. 02

    Add an Order Desk module

    In your scenario, add any Order Desk module and click Create a connection. A connection is your Order Desk account linked to Make once, then reused by every Order Desk module. Type a label in Connection name if you want to spot it later.

  3. 03

    Paste your credentials and confirm

    Paste the Store ID and the API key you copied, or follow the on-screen instructions, and confirm. The module can now reach your store, and the same connection shows up in every other Order Desk module you add.

First scenario

Your first scenario: file new Order Desk orders on arrival

GoalWhen an order reaches Order Desk from outside, Make moves it into the folder your team checks first.

  1. 01

    Create the scenario

    Open the Scenarios page in Make and create a new scenario, the automation you are about to build. Click the big + in the middle of the editor to add its first module.

  2. 02

    Set up Watch Orders

    Search for Order Desk and pick Watch Orders. Click Create a webhook, then Create a connection with your Store ID and API key. This instant trigger now waits for orders created outside Order Desk.

  3. 03

    Add Change Orders Folder

    Click the + on the right of Watch Orders and choose Change Orders Folder. Map the order coming from the trigger's bundle, the item it hands over, then pick the folder your team reviews first.

  4. 04

    Test with Run once

    Click Run once, then let an order come in from outside Order Desk. Read the bundle each module received, and open Order Desk to check that the order sits in the right folder.

  5. 05

    Switch the scenario on

    Turn the scenario on. Watch Orders is instant, so Order Desk calls Make as each outside order appears. Every module run on one bundle counts as one operation on your Make plan.

Triggers

Order Desk triggers in Make

4 modules start a scenario when something happens in Order Desk. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by Order Desk as soon as it happens.

Order Desk1Watch New Event

Watch New Event

Instant trigger

In Make“Triggers when a selected event have been occured.”

Watch New Event starts your scenario when an Order Desk event you selected takes place, which covers cases the three order triggers leave aside. You pick the event in the module, and each occurrence reaches Make as a bundle passed to the next module.

How it fires
instant. Order Desk calls Make through a webhook as soon as the event happens.
When to use it
reach for it when the moment you care about is neither a new order nor a folder move.
Watch out
the documentation does not spell out which events are on offer, so open the module and read its list before you design the scenario around one.
Order Desk2Watch Order Folder Changed

Watch Order Folder Changed

Instant trigger

In Make“Triggers when an order's folder has been changed.”

Each time an order lands in a different folder in Order Desk, this trigger hands that order to your scenario. A simple drag between folders becomes a signal Make can act on.

How it fires
instant. Order Desk calls Make through a webhook as soon as the folder changes.
When to use it
pick it when moving an order should set off the next job, such as gathering its parcels with List Shipments or alerting another app.
Watch out
if the same scenario also runs Change Orders Folder, the move it makes can fire this trigger again. Keep those two in separate scenarios so an order does not bounce endlessly.
Order Desk3Watch Orders

Watch Orders

Instant trigger

In Make“Triggers when an order has been created outside of Order Desk.”

Your scenario receives every order that reaches Order Desk from outside, as opposed to orders typed in by hand. It is the natural starting point for anything that should happen to a fresh order.

How it fires
instant. Order Desk calls Make through a webhook as soon as the order is created.
When to use it
choose it to sort, check or copy incoming orders before anyone on the team opens them.
Watch out
orders keyed in by hand have their own trigger, Watch Orders Created Manually. Set up that one too, in a second scenario, if both kinds of orders matter to you.
Order Desk4Watch Orders Created Manually

Watch Orders Created Manually

Instant trigger

In Make“Triggers when an order has been created manually.”

Orders someone enters by hand in Order Desk get a trigger of their own here, so you can handle them differently from the ones that flow in from outside.

How it fires
instant. Order Desk calls Make through a webhook as soon as the order is saved.
When to use it
when a teammate keys in an order and you want Make to follow up, for example by adding a line with Create an Order Item or filing it with Change Orders Folder.
Watch out
like every instant Order Desk module, it asks you to click Create a webhook before Create a connection; skip that and nothing reaches the scenario.
Modules

Everything Order Desk can do in Make

Order Desk gives you 22 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

Order Desk1

Change Orders Folder

Action

In Make“Moves specified orders to the specified folder.”

Change Orders Folder moves the orders you point to into the folder you choose, so your Order Desk board reflects what Make has just checked or done.

When to use it
at the end of a scenario, to file a new order in a review folder or push a processed one to its next stage.
Watch out
a scenario that starts on Watch Order Folder Changed and ends with this module can set itself off again; split that work into two scenarios.
Order Desk2

Create an Inventory Item

Action

In Make“Creates an inventory item.”

Adding a product to your Order Desk stock from another tool takes a single module: this one writes a new inventory record from the data you map into it.

When to use it
when a product appears in a spreadsheet or a catalog app and Order Desk should know about it too.
Watch out
run Search Inventory Items first if the product might already exist, or you could end up with two records for the same item.
Order Desk3

Create an Order

Action

In Make“Creates an order.”

Create an Order places a fresh order in Order Desk from data an earlier module produced, which spares your team from retyping orders that already exist somewhere else.

When to use it
when orders start life outside Order Desk, in a form or a quote tool, and should end up next to all the others.
Watch out
each bundle creates one order, so test with Run once on a single item before you switch the scenario on.
Order Desk4

Create an Order Item

Action

In Make“Creates an order item.”

With this module you add a line to an order that already exists, so the order grows without being rebuilt from scratch.

When to use it
when a customer adds a product after ordering, or when a scenario should slip a sample into certain orders.
Watch out
the module has to know which order to extend; map that order from the trigger or from Get an Order instead of typing it by hand.
Order Desk5

Create a Shipment

Action

In Make“Creates a shipment.”

Create a Shipment records a shipment on an order in Order Desk, so anyone who opens that order sees what has been sent.

When to use it
when your shipping app confirms a parcel and Order Desk should hold that information as well.
Watch out
each run adds a new shipment. If the parcel is already on the order and only its details changed, use Update a Shipment instead.
Order Desk6

Delete an Inventory Item

Action

In Make“Deletes an inventory item.”

Retiring a product for good becomes one step: Delete an Inventory Item removes its record from Order Desk stock and keeps the list clean.

When to use it
when a product is discontinued in your source catalog and should disappear from Order Desk as well.
Watch out
treat the deletion as final, and read the record with Get an Inventory Item before this module runs so you remove the right one.
Order Desk7

Delete an Order

Action

In Make“Deletes an order.”

This module erases an order from Order Desk entirely, which is handy for test orders or duplicates that clutter your folders.

When to use it
after Search Orders has surfaced a duplicate that really has to go.
Watch out
when there is any doubt, park the order in a holding folder with Change Orders Folder rather than deleting it, since a removed order will not come back by itself.
Order Desk8

Delete an Order Item

Action

In Make“Deletes an order item.”

Delete an Order Item takes one line off an order and leaves the rest of that order in place, which keeps corrections small.

When to use it
when a customer drops one product from a larger order, or when a scenario added a line by mistake.
Watch out
List Order Items shows every line of the order first, so you target the right one instead of guessing.
Order Desk9

Delete a Shipment

Action

In Make“Deletes a shipment.”

A shipment that should never have been recorded can be cleared from its order with this module, leaving the order's history accurate.

When to use it
when a parcel is cancelled before it leaves, or when a scenario recorded the same shipment twice.
Watch out
run List Shipments on the order first to see every shipment attached to it, then pick the one to delete.
Order Desk10

Get an Inventory Item

Action

In Make“Retrieves an inventory item.”

Get an Inventory Item reads one product record from Order Desk and passes its details on, so the next modules work from current stock data.

When to use it
when you already know which item you need, for instance right before an update or a deletion.
Watch out
if you only have a partial detail about the product, start with Search Inventory Items, which can return several matches.
Order Desk11

Get an Order

Action

In Make“Retrieves an order.”

Pull the full picture of a single order into your scenario: the modules that follow can then use its data without anyone copying it over.

When to use it
when a trigger or another app hands you an order and you need its latest state before acting on it, such as ahead of Update an Order.
Watch out
it returns one order only; to find orders you cannot pinpoint yet, Search Orders is the right tool.
Order Desk12

Get an Order Item

Action

In Make“Retrieves an order item.”

One line of an order, fetched on its own: that is what this module brings when a single product matters more than the whole order.

When to use it
before changing a line with Update an Order Item, to see what it holds right now.
Watch out
to read all the lines of an order at once, List Order Items does the job in one module instead of a chain of single reads.
Order Desk13

Get a Shipment

Action

In Make“Retrieves a shipment.”

Get a Shipment brings the details of one shipment from Order Desk to the modules that follow, so a message or a report can quote them.

When to use it
when an order moves to a shipping folder and another app, such as your customer messaging tool, needs what was sent.
Watch out
it reads one shipment only; to see every parcel of an order, List Shipments is the better pick.
Order Desk14

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call lets your scenario reach any endpoint of the Order Desk API with the connection you already set up, so a missing module is rarely a dead end.

When to use it
when none of the ready-made actions and searches covers what you have in mind.
Watch out
you write the request yourself here, so keep the Order Desk API documentation open and test with Run once before going live.
Order Desk15

Update an Inventory Item

Action

In Make“Updates an inventory item.”

Update an Inventory Item changes an existing stock record in Order Desk, so the product stays in line with the tool where your team maintains it.

When to use it
when a product changes in your catalog and Order Desk should follow without a manual edit.
Watch out
locate the record with Search Inventory Items first; updating the wrong item quietly overwrites good data.
Order Desk16

Update an Order

Action

In Make“Updates an order.”

Rather than editing orders by hand, let this module rewrite the details of an existing order with values from earlier modules.

When to use it
when another system corrects something about an order, like a customer request logged in your help desk.
Watch out
placed after a search, it runs once per bundle and changes every order found, so test on a single order with Run once.
Order Desk17

Update an Order Item

Action

In Make“Updates an order item.”

Update an Order Item edits one line of an order without touching its other lines, which keeps a correction precise.

When to use it
when a line was entered wrong or a product gets swapped for another one.
Watch out
Get an Order Item or List Order Items tells you which line to target; map it from them rather than typing it in.
Order Desk18

Update a Shipment

Action

In Make“Updates a shipment.”

A shipment already recorded in Order Desk can be corrected here, so the order keeps telling the right delivery story.

When to use it
when details about a parcel change after it was recorded, for instance when the shipping app sends an update.
Watch out
if the shipment does not exist yet, Create a Shipment is the module you need, since this one only edits.
Order Desk19

List Order Items

Search

In Make“Returns a list of items for a specific order.”

List Order Items returns every line of one order, each as its own bundle, so the next modules can deal with the products one by one.

When to use it
when each product of an order needs its own treatment, such as a stock check with Get an Inventory Item.
Watch out
every module placed after it runs once per line, and Make counts each of those runs as an operation.
Order Desk20

List Shipments

Search

In Make“Returns a list of shipments for a specific order.”

Every shipment tied to an order comes back from this search, one bundle per shipment, giving you the full delivery picture for that order.

When to use it
when an order leaves in several parcels and you want to report on all of them, or before Delete a Shipment.
Watch out
the search can return zero shipments, so think about what the scenario should do for an order that has not shipped yet.
Order Desk21

Search Inventory Items

Search

In Make“Searches for inventory items.”

Search Inventory Items looks through your Order Desk stock and returns the matching products, zero, one or many, as separate bundles.

When to use it
before creating a product, to avoid duplicates, or when you only know part of a product's details.
Watch out
a broad search can return a long list, and each result then costs operations in the modules that follow.
Order Desk22

Search Orders

Search

In Make“Searches for orders.”

Finding the orders that match what you look for is this module's job; each one comes out as a bundle, ready for an update, a move or a report.

When to use it
when you need to act on a set of orders at once, or to spot a duplicate before Delete an Order.
Watch out
read the bundles it returns in a Run once test before chaining an action that changes every order found.
Need help

Need help automating Order Desk with Make?

A person reads every message.

FAQ

Order Desk and Make: common questions

01Is the Order Desk Make integration free?
Yes, on the Make side. Order Desk is a standard app, so its modules are available from the Free plan. That plan allows 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. On the Order Desk side, you still need an active account; its pricing page covers the subscription.
02What do you need to connect Order Desk to Make?
An active Order Desk account and two values from it: the Store ID and the API key. Both sit under Settings, then Store Settings, then the API tab. In Make, add an Order Desk module, click Create a connection, give it a name if you like and paste the two values. For one of the four instant triggers, click Create a webhook before the connection. The connection is saved once and reused by every Order Desk module afterward.
03Do Order Desk triggers fire in real time in Make?
Yes. All four Order Desk triggers are instant: Watch New Event, Watch Order Folder Changed, Watch Orders and Watch Orders Created Manually. Order Desk calls Make through a webhook as soon as the event happens, rather than Make checking on a schedule. That is why these modules ask you to create a webhook when you add them. The scenario must be switched on to react to those calls, and Run once lets you test with a single event beforehand.
04What if an Order Desk module is missing in Make?
Use Make an API Call. It reaches any endpoint of the Order Desk API with the connection you already have, so whatever the 26 listed modules leave out can still be requested. Before relying on a detail, keep in mind that the Make documentation for Order Desk is flagged as AI-generated from the vendor's own docs and may contain mistakes. Check important points with Order Desk directly, especially when you build a raw API request.
05Make or n8n for Order Desk?
It depends on the tool your other automations already run on. In Make, Order Desk comes with 26 ready modules, four instant triggers among them, and a connection built from a Store ID and an API key. n8n is a separate automation tool, and the same app often has an n8n node there too. If you are weighing both, compare what each one gives you for Order Desk and for the other apps in your flow before you commit.
Same platform

Other docs you might need on this stack.

Browse all integrations