Resources · Make integration

eDock Make integrationAutomate eDock with Make.

What happens to an eDock order once nobody has to copy it by hand? The eDock Make integration gives you 13 modules: 4 triggers that watch orders, 5 actions and 4 searches. This guide helps online sellers connect their account, build a first scenario and pick the right module.

Try the eDock integration on MakeSee the 13 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the eDock Make integration let you automate?

The eDock Make integration links your eDock account to Make, so orders can start automations and be handled by them without manual copying. In Make, an automation is a scenario: a chain of modules, where each module is one brick such as a trigger, an action or a search. eDock brings 13 of those bricks, all centered on orders and price lists.

A team that hears about paid orders right away. Watch Paid Order starts the scenario when an order is paid, and Get an Order pulls the full record so the next app, a chat tool or a spreadsheet, receives everything it needs. The warehouse stops refreshing the eDock screen.

Orders from another channel that land in eDock. A form or a second shop collects a sale, and Create an Order writes it into eDock. One place for every order, whatever the source.

A status board that keeps itself current. Watch Changed Order Status and Watch Shipped Order feed a shared sheet, while List Orders Statuses tells you which status names your account uses.

Know the limits before you build. Make's own documentation for eDock is short, because little public information about the app exists, so test each module on a real order with Run once before you trust it. If you want a structured path, the Make training starts from zero, and Make troubleshooting helps when a run fails. Weighing the other tool? Our n8n vs Make comparison sets the criteria side by side.

Connect

How do you connect eDock to Make?

  1. 01

    Add an eDock module

    Open a scenario in Make, add any eDock module and click Create a connection. A connection is your eDock account linked to Make once; every eDock module you add later reuses it.

  2. 02

    Give it a clear name

    Naming the connection is optional. It still helps as soon as a colleague opens the scenario, or when you run more than one eDock account, because the name shows at a glance which store the modules talk to.

  3. 03

    Authorize and save

    Follow what the dialog asks: either authorize Make on the eDock page that opens, or paste the key eDock gives you. Click Save, and the module can now list what your account holds.

First scenario

Your first scenario with eDock

GoalWhen a sale comes in through another app, Make creates the matching order in eDock.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the +. Pick the app where your sales arrive first, a form or another shop, and choose its trigger.

  2. 02

    Add Create an Order

    Click the + on the right of that first module, search for eDock and pick Create an Order. Click Create a connection if eDock is not linked yet.

  3. 03

    Map the sale to the order

    Fill the fields Make shows for the order by mapping data from the first module: each value you drag in comes from the bundle, the single sale that the previous module handed over.

  4. 04

    Test with Run once

    Click Run once, submit a test sale in the source app, then open each module's bubble to read the bundles it received. Check in eDock that the order really appeared.

  5. 05

    Schedule and switch on

    Open the clock on the first module and set the schedule, every 15 minutes by default. Switch the scenario on, and each run counts operations, one per module per bundle, on your plan.

Triggers

What can start an eDock scenario?

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

eDock1Watch Changed Order Status

Watch Changed Order Status

triggerIn the docs only

You find out when an eDock order moves from one status to another, and the scenario takes over from there. Each order it catches travels to the next module as one bundle, so a follow up happens per order and never gets forgotten.

How it fires
scheduled, Make checks the app on the scenario's schedule, every 15 minutes by default.
When to use it
when any status change, not just payment or shipping, should alert someone or update another tool.
Watch out
eDock's documentation in Make is limited, so run it once on a test order to see what a status change sends.
eDock2Watch Created Order

Watch Created Order

triggerIn the docs only

Every new order in eDock becomes the starting point of an automation, before anyone has touched it. That is the earliest moment you can react, which suits tasks that should happen for all orders, paid or not.

How it fires
scheduled, Make checks the app on the scenario's schedule; the Free plan never checks more often than every 15 minutes.
When to use it
when a fresh order should be logged in a sheet or announced to the team right away.
Watch out
an order that is later cancelled was still caught here, so keep downstream steps reversible.
eDock3Watch Paid Order

Watch Paid Order

triggerIn the docs only

Your scenario starts only on orders that have been paid, which filters out the ones still waiting. That makes it the safe choice for anything that costs you effort or stock, like preparing a parcel or issuing a document.

How it fires
scheduled, Make checks the app on the scenario's schedule instead of eDock pushing the event.
When to use it
when the warehouse or accounting should act only once the money is in.
Watch out
between two checks, several paid orders can pile up; each arrives as its own bundle and each module run on it counts as one operation.
eDock4Watch Shipped Order

Watch Shipped Order

triggerIn the docs only

Shipping closes the loop: this trigger hands your scenario each order eDock marks as shipped, so the customer side of the story can continue without a manual check.

How it fires
scheduled, Make checks the app on the scenario's schedule, which means a small delay after the order ships, never an instant alert.
When to use it
when a shipping confirmation, a review request or a sheet update should follow the parcel.
Watch out
on the Free plan only 2 scenarios can be active, so decide whether this one deserves a slot before you add more.
Modules

What can eDock do inside a scenario?

eDock gives you 9 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

eDock1

Create an Order

ActionIn the docs only

A sale collected elsewhere becomes a real eDock order, with nobody retyping it. The module writes one order per bundle it receives.

When to use it
when a form, a marketplace or a second shop takes sales that eDock should manage too.
Watch out
run it once with a test sale and check the result in eDock, because the documentation does not describe every field.
eDock2

Get a Pricelist for a Module

ActionIn the docs only

Going by its name, this brings back the price list attached to one eDock module, so your scenario works with the prices eDock actually holds rather than a copy that drifts.

When to use it
when you already know which eDock module you care about and need its prices in a sheet or a message.
Watch out
run List Modules first if you are unsure which module to point at.
eDock3

Get an Order

ActionIn the docs only

Hand it one order and it returns the complete record, which is handy when a trigger or a search gave you only part of the story.

When to use it
right after a trigger, to pass the full order to the next app, for example a message to the packing team.
Watch out
it reads a single order; for several at once, List Orders is the better fit.
eDock4

List Modules

SearchIn the docs only

Here "module" means eDock's own modules, not Make's bricks. Going by its name, it lists the ones in your account, one bundle each, so you know what the price list modules can target without leaving Make.

When to use it
before Get a Pricelist for a Module, to find the right module to query.
Watch out
a search can return zero, one or many bundles, and every module after it runs once per bundle.
eDock5

List Orders

SearchIn the docs only

Pull a batch of eDock orders into your scenario in one step, instead of waiting for a trigger to catch them one by one. Each order comes out as its own bundle.

When to use it
when a scenario started by another app, a form or a button, needs to look at existing orders.
Watch out
a long list multiplies the operations of every module that follows, so filter before heavy steps.
eDock6

List Orders Statuses

SearchIn the docs only

This shows the status names your eDock account uses for orders. Knowing them saves guesswork when a later step has to compare or set a status.

When to use it
while building a scenario around Move Orders or Watch Changed Order Status, to check the exact names.
Watch out
it is a reference lookup; it tells you nothing about any single order.
eDock7

List Pricelists

SearchIn the docs only

Every price list in your eDock account lands in the scenario, one bundle each, ready to be copied to a sheet or compared with another source.

When to use it
when you need an overview of all price lists rather than the one tied to a single module.
Watch out
each price list is a separate bundle, so a message step placed after it sends one message per list.
eDock8

Make an API Call

ActionIn the docs only

When none of the ready modules does what you need, this one lets you call any endpoint of the eDock API from your scenario, reusing the same connection as the other eDock modules.

When to use it
for an eDock feature that has no dedicated module in Make.
Watch out
you have to know the eDock API yourself, since Make's documentation for the app stays short.
eDock9

Move Orders

ActionIn the docs only

Orders shift in eDock from the scenario itself, so a change decided elsewhere shows up in the store without anyone clicking through it.

When to use it
when a step in another tool, such as a packed parcel, should be reflected on the matching eDock orders.
Watch out
the documentation does not say where orders move to, so test it with Run once on a dummy order before touching real ones.
Need help

Need help automating eDock with Make?

A person reads every message.

FAQ

Common questions about eDock and Make

01Is the eDock Make integration free?
Yes, eDock is a standard app, so its modules work from the Make Free plan. That plan has limits: 2 active scenarios, scheduled runs no closer than 15 minutes apart, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams, Enterprise) bring the interval down to 1 minute and remove the cap on active scenarios. Usage is counted in operations, one per module per bundle. Whatever you pay eDock itself is a separate matter.
02What do you need to connect eDock to Make?
An eDock account and a Make account. Make's documentation lists no special prerequisite for eDock and gives no app-specific connection guide, so the generic path applies: add an eDock module, click Create a connection, name it if you like, then either authorize Make on the eDock page or paste the key eDock gives you, and click Save. The connection is then shared by all eDock modules in your scenarios, so you only do this once per account.
03Does the eDock Make trigger fire in real time?
No. The documentation does not describe the 4 eDock triggers (changed status, created, paid and shipped orders), but their "Watch" names mark them as scheduled triggers: Make checks eDock on the scenario's schedule, which is every 15 minutes by default. On the Free plan the shortest gap is 15 minutes; paid plans go down to 1 minute. So expect a short delay between the event in eDock and the scenario run. None of the eDock modules is an instant trigger, which would be the kind the app calls through a webhook.
04What if an eDock module is missing in Make?
Use Make an API Call. It sends a request to any endpoint of the eDock API with the same connection as the ready modules, so you are not limited to the 13 listed ones. The catch: Make's eDock documentation is limited, because little public information about the app exists, so you will need eDock's own API reference to build the request. Test each call with Run once and read the returned bundle before you switch the scenario on.
05Make or n8n for eDock?
It depends on what you check. In Make, eDock comes with 13 ready modules, 4 scheduled triggers among them, plus Make an API Call, and it runs on the Free plan within its limits. For n8n, look up whether an eDock node exists and what it covers before comparing, since this page does not document it. Then decide on the modules you actually need and on how your team prefers to build. Neither tool is ranked here.
Same platform

Other docs you might need on this stack.

Browse all integrations