Resources · Make integration

Dokan Make integrationAutomate Dokan with Make.

What can your store run on its own once Dokan talks to Make? The Dokan Make integration gives you 15 modules: 3 scheduled triggers, 9 actions and 3 searches around orders, products and order notes. This guide is for store operators who want the setup, a first working scenario and a plain read of every module.

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What does the Dokan Make integration let you automate?

The Dokan Make integration links your Dokan account to Make, a no-code tool where you build a scenario: a chain of modules that runs on a schedule. Each module is one brick of that chain. With Dokan, those bricks watch new orders, products and order notes, then read, create, update or delete them for you.

Orders that land somewhere useful. Watch Orders picks up each new order, and the next module sends its details to the tool your team already reads, such as a base built like the one on the Airtable Make integration page. No one has to copy order data by hand anymore.

A catalog that keeps itself tidy. Search Products finds the items that match what you are looking for, and Update a Product changes them one by one. Create a Product adds new listings from a source you already maintain.

A paper trail on every order. Create an Order Note writes a note on the order as soon as another step finishes, so whoever opens the order sees what happened. Watch Order Notes can in turn start a scenario when someone adds a note.

Know the limits before you start. The Make documentation for Dokan is marked as limited: Make says there is not enough public information about the app to document it fully, so each module is described in one line and field details are thin. All 3 triggers are scheduled, which means Make checks Dokan on the scenario's schedule instead of hearing about changes the moment they happen. When a listed module falls short, Make an API Call reaches the rest of the Dokan API with the same connection. The same app often has an n8n node too; the n8n vs Make comparison lays out both tools side by side, and the Make training covers scenario building from the ground up.

Connect

How do you connect Dokan to Make?

  1. 01

    Add a Dokan module

    Open your scenario, click the +, search for Dokan and pick any of its modules. Make then asks for a connection: your Dokan account linked to Make once, and reused by every Dokan module you add later.

  2. 02

    Create and name the connection

    Click Create a connection. Giving it a name is optional, but a clear one, like the store it belongs to, saves confusion the day you manage more than one Dokan account in the same Make workspace.

  3. 03

    Authorize and save

    Depending on what the app offers, either approve Make on the Dokan authorization page or paste the key Dokan gives you, then click Save. The module can now read your orders, products and notes.

First scenario

Build your first scenario with Dokan

GoalWhen a new order arrives in Dokan, Make adds a note to that order so your team sees it was picked up.

  1. 01

    Create the scenario

    From the Scenarios page, create a new scenario and click the + in the middle of the canvas. That empty circle is where your first module goes.

  2. 02

    Add Watch Orders

    Search for Dokan, pick Watch Orders and select your connection, or click Create a connection if this is your first Dokan module. Fill in the fields Make shows you.

  3. 03

    Add Create an Order Note

    Click the + to the right of Watch Orders and choose Create an Order Note. Map the order from the first module so the note lands on the right order, then write the note text.

  4. 04

    Test with Run once

    Click Run once. Make runs the scenario a single time and shows the bundles each module received, a bundle being one item passed along, here one order. Check the note in Dokan.

  5. 05

    Schedule and switch it on

    Open the clock on Watch Orders to set the schedule, every 15 minutes by default for a new scenario, then turn the scenario on. From then on each check picks up the orders placed since the last one.

Triggers

What can start a Dokan scenario?

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

Dokan1Watch Order Notes

Watch Order Notes

Scheduled trigger

In MakeWatches for new order notes.

Watch Order Notes starts your scenario each time a new note shows up on an order, so a comment left by staff or by the system can set off a follow-up without anyone forwarding it.

How it fires
it is a scheduled trigger, meaning Make checks Dokan on the scenario's schedule and collects the notes added since its previous check.
When to use it
your team writes a note when an order needs attention and you want that note copied to the channel where someone will act on it.
Watch out
it reacts to new notes only, and it waits for the next scheduled check, so a note is never picked up the second it is written.
Dokan2Watch Orders

Watch Orders

Scheduled trigger

In MakeWatches for new orders.

Watch Orders hands your scenario every new order placed in Dokan, one bundle per order, which makes it the natural first brick for anything that should happen after a sale.

How it fires
scheduled, so Make asks Dokan for new orders at each run of the scenario rather than being told by the store.
When to use it
a new order should create a line in your tracking sheet, trigger a note on the order or alert whoever prepares shipments.
Watch out
it catches new orders, not changes to existing ones. To follow an order after it was placed, read it again later with Get an Order or List Orders.
Dokan3Watch Products

Watch Products

Scheduled trigger

In MakeWatches for new products.

Watch Products brings each newly added product into your scenario, so a fresh listing can spread to the rest of your tools without a second round of data entry.

How it fires
this one is scheduled as well. Make polls Dokan on the scenario's schedule and returns the products created since the last check.
When to use it
a new product should appear in a catalog sheet, a review queue or an announcement draft as soon as the next check runs.
Watch out
its description only mentions new products, so do not count on it to catch edits. Check a product again with Get a Product when you need its latest state.
Modules

Every Dokan module, explained

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

Dokan1

Create an Order Note

Action

In MakeCreates an order note.

Create an Order Note writes a note on an order you point to, so the order itself tells the story of what your automations did with it.

When to use it
right after a step succeeds elsewhere, for example once the order was copied to your shipping sheet, to leave a visible trace on the order.
Watch out
map the order from an earlier module; a note needs to know which order it belongs to.
Dokan2

Create a Product

Action

In MakeCreates a product.

Create a Product adds a new product to Dokan from data your scenario already holds, which spares you from typing the same listing twice.

When to use it
your product details live in a sheet or a form and each new row should become a listing in the store.
Watch out
run it once with a test item first, since the Make documentation for Dokan does not detail which fields are required.
Dokan3

Delete an Order Note

Action

In MakeDeletes an order note.

Delete an Order Note removes one note from an order, handy when a scenario posted a note that no longer applies and you want the order history clean.

When to use it
a temporary note, such as a reminder that a payment check is pending, should vanish once that check passes.
Watch out
deletion cannot be undone from Make, so read the note with Get an Order Note first if you are unsure which one you target.
Dokan4

Delete a Product

Action

In MakeDeletes a product.

Delete a Product takes a product out of your Dokan catalog for good, the cleanest way to retire an item that another system marks as discontinued.

When to use it
a product is flagged as withdrawn in the source you maintain and must disappear from the store too.
Watch out
there is no undo. Test it on a dummy product with Run once before letting it touch real listings.
Dokan5

Get an Order

Action

In MakeRetrieves a specific order.

Get an Order fetches one order in full when you already know which one you want, giving later modules its current details to work with.

When to use it
a note or a message mentions an order and your scenario needs the rest of its data, not just the reference.
Watch out
it returns a single order. To pull several orders at once, List Orders is the better pick.
Dokan6

Get an Order Note

Action

In MakeRetrieves a specific order note.

Get an Order Note reads a single note on an order, useful when your scenario holds the note's reference and needs its full content before deciding what to do.

When to use it
before deleting or forwarding a note, to check its text and make sure it is the right one.
Watch out
it targets one known note. If you only know the order, start with List Order Notes instead.
Dokan7

Get a Product

Action

In MakeRetrieves a specific product.

Get a Product loads one product with its current details, so your scenario works from what the store shows today rather than from an old copy.

When to use it
just before Update a Product, to compare the stored values with the new ones and skip changes that are not needed.
Watch out
you need the product's identifier; when you only have a name, find it first with Search Products.
Dokan8

Make an API Call

Action

In MakePerforms an arbitrary authorized API call.

Make an API Call lets you call any endpoint of the Dokan API through the connection you already set up, which covers whatever the ready-made modules leave out.

When to use it
you need a Dokan feature that has no dedicated module here, and you know which API request serves it.
Watch out
you write the request yourself, and the Make documentation for Dokan is limited, so check the app's own API reference.
Dokan9

Update a Product

Action

In MakeUpdates a product.

Update a Product changes an existing product in place, keeping your Dokan listing in step with the source where you actually edit prices or descriptions.

When to use it
a row changes in your catalog sheet and the matching product in the store should follow.
Watch out
pair it with Search Products or Get a Product so each update hits the right item, not a lookalike.
Dokan10

List Order Notes

Search

In MakeRetrieves a list of order notes.

List Order Notes returns the notes attached to an order, each one as its own bundle, so you can review an order's whole history in one pass.

When to use it
you want every note on an order copied into a customer file or a support ticket.
Watch out
it can return zero, one or many notes, and each following module runs once per note, which counts as more operations.
Dokan11

List Orders

Search

In MakeRetrieves a list of orders.

List Orders pulls a batch of orders from Dokan, which suits reports and checks where one order at a time would be too slow.

When to use it
you run a review of open orders and want them all in a sheet before sorting them.
Watch out
every order becomes one bundle, and each operation, one module run on one bundle, counts on your Make plan.
Dokan12

Search Products

Search

In MakeSearches for products or list them all.

Search Products finds the products matching your criteria, or lists the whole catalog, so the next modules can act on exactly the items you care about.

When to use it
before Update a Product, to locate the listing that matches a row from your source sheet.
Watch out
it can return zero, one or many products, and a broad search makes every following module run once per product found.
Need help

Need help automating Dokan with Make?

A person reads every message.

FAQ

Dokan and Make: common questions

01Is the Dokan Make integration free?
Yes, you can start on the Free plan. Dokan is a standard app, and standard apps are available on every Make plan, the free one included. The Free plan comes with limits: 2 active scenarios, at least 15 minutes between two scheduled runs, 5 minutes of execution at most per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute and allow unlimited active scenarios. Usage is counted in credits, meaning operations, per month.
02What do you need to connect Dokan to Make?
A Dokan account you can authorize, and a Make account. The Make documentation for Dokan lists no specific prerequisite and gives no official connection steps, so the generic flow applies: add any Dokan module, click Create a connection, optionally name it, authorize Make on the Dokan page or paste the key Dokan provides, then click Save. That single connection is reused by every Dokan module in your scenarios, so you only do this once per account.
03Do Dokan triggers in Make fire in real time?
No. All 3 Dokan triggers, Watch Orders, Watch Products and Watch Order Notes, are scheduled. Make checks Dokan on the scenario's schedule and picks up what is new since the previous check, instead of Dokan calling Make the moment something changes. A new scenario runs every 15 minutes by default. On the Free plan the shortest interval is 15 minutes; paid plans can go down to 1 minute. Each check collects everything that arrived in between.
04What if a Dokan module you need is missing in Make?
Use Make an API Call. It is available for Dokan and calls any endpoint of the Dokan API with the connection you already created, so you are not limited to the 15 listed modules. Keep in mind that Make marks its Dokan documentation as limited, because there is not enough public information about the app, so the request details have to come from Dokan's own API reference. Test each new call with Run once before switching the scenario on.
05Should you use Make or n8n for Dokan?
It depends on the tool your team already works in. Make offers 15 ready-made Dokan modules, with 3 scheduled triggers, 9 actions and 3 searches, plus Make an API Call for the rest of the API. The same app often has an n8n node as well, so check what that node covers before choosing. The sensible move is to pick the platform where your other automations already live, then compare the specific modules you need for your order and product flows.