FlowRunner
PricingContact
Theme
Start Free

Dokan

E-commerce

Dokan is the multivendor marketplace plugin for WooCommerce. Agents onboard and approve vendors, publish and maintain marketplace products, track orders, withdrawals and commission, manage coupons and reviews, and pull store reports.

1 trigger 117 actions Basic auth available
Dokan website Platform Documentation Capability data verified 2026-08-26
The payout schedule fires for the marketplace
List Withdrawals returns the pending requests with the vendor and amount on each
Get Withdrawal Balance and Get Withdrawal Charges confirm the balance covers the request and what the method costs
Get Site Capabilities confirms which Dokan modules this store actually serves
The finance approver receives the batch, the totals, the charges, and every vendor whose balance falls short
The approver names which requests are paid, and Batch Update Withdrawals runs on exactly those

What This Integration Enables

Dokan turns a WooCommerce store into a marketplace, and that single change alters what automation has to be careful about. In an ordinary store the counterparty on the other side of every write is a customer. On a marketplace it is a vendor: an independent business with a store page, a commission arrangement, a payout balance, and a commercial relationship that survives the transaction. Approving a withdrawal is not updating a record, it is moving someone else's money. Suspending a vendor is not a status flag, it is taking a business offline.

The second thing worth knowing before building anything is that Dokan is not one API. The free plugin registers roughly sixty routes; a fully loaded Pro marketplace serves several times that, and which modules are installed decides what exists. That is why Get Site Capabilities is the first call rather than a diagnostic: it reports the namespaces served, the module map, and whether the webhook routes the trigger needs are present. A 404 on this platform usually means "that module is not installed here", and a flow that knows the difference behaves very differently from one that treats it as a bug.

FlowRunner agents run the marketplace surface across vendors, catalog, orders, shipments, withdrawals, coupons, reviews, refunds, and reports, with human-in-the-loop steps placed where the consequence lands on a vendor rather than on a row.

Without FlowRunner

Payouts reconstructed by hand Someone opens the vendor dashboard, checks balances one at a time, and approves in the admin panel
Vendor onboarding is a mailbox Applications arrive as messages and a person retypes them into store records
Moderation waits for someone to look Held reviews and refund requests sit until a marketplace manager remembers the queue

With FlowRunner

Payouts arrive assembled Requests, balances, charges, and shortfalls are gathered into one reviewable batch
Applications become stores An approved application creates the vendor, checks the store slug, and sends the onboarding message
Queues come to the manager Held reviews and refund requests are screened and routed, and only the judgment calls surface

Use Case Scenarios

  • Payout day, assembled rather than reconstructed

    On a schedule the agent calls List Withdrawals for pending requests, then Get Withdrawal Balance and Get Withdrawal Charges per vendor so the numbers in front of the approver are the platform's own rather than a spreadsheet's. Requests that exceed the available balance, or whose method carries a charge the vendor may not expect, are called out separately. The whole batch goes to the finance approver in Slack. Approval runs Batch Update Withdrawals once. What changed is not the speed of the approval, it is that the approver sees the same numbers Dokan does at the moment they decide.

  • An application becomes a working store

    Vendor applications arrive through a form in Typeform. The agent reads each response, calls Check Store URL Availability so the store slug does not collide with an existing one, creates the vendor, and sends the onboarding instructions with Email Vendor. The account stays inactive until the documents clear, at which point Update Vendor Status brings the store live. Nothing about the application is retyped, and the slug collision that would otherwise be discovered after launch is discovered before it.

  • Order events that reach the right vendor

    On Store Event fires for a created order, and because WooCommerce delivers store-wide rather than per vendor, the flow resolves the vendor itself before doing anything else. The order and its lines are appended to a reconciliation sheet in Google Sheets, high-value orders are flagged to the operations team, and tracking added later by the vendor goes on with Create Order Shipment. The trigger delivers everyone's orders. Sorting them out is the flow's job, and it is a job worth doing once rather than in every downstream step.

Human-in-Loop Highlight

Batch Update Withdrawals approves a set of vendor payout requests in one call, and two things make it the operation on this page worth stopping for. The first is obvious: the money belongs to the vendors, not to the marketplace, and once a payout is approved the marketplace is paying out against a balance the platform computed rather than one a person checked. The second is particular to Dokan. The operations a flow would reach for to unwind a mistake are module dependent, and Get Site Capabilities is the only way to know which of them this install actually has. A recovery path that exists on a fully loaded Pro marketplace may simply not be registered on the store the agent is running against. So the agent gathers and stops: "11 withdrawal requests pending, 4,912.00 total. Two vendors are requesting more than their available balance, both listed below. Bank transfer charges apply to seven. This store reports the refunds module as absent. Approve all, approve the nine that clear, or hold?" The finance approver answers. An agent can compute a payout batch perfectly well. It should not be the thing that decides to send it.

Agent processes routinely
Detects exception requiring judgment
Clear match Continues automatically
Ambiguous Routes to human via preferred channel
Human decides
Agent resumes with decision

Agent Capabilities

117 actions

Site

1
  • Get Site Capabilities Reads the store's own route index and reports the namespaces served, the Dokan route count, an inferred edition, a per-module present or absent map, and whether the WooCommerce webhook routes the trigger needs exist. Run it first, and again whenever something answers Not Found.

Vendors

13
  • List Vendors Lists the marketplace's vendors with their store details and status.
  • Get Vendor Retrieves one vendor with its store page, address, and settings.
  • Create Vendor Creates a vendor account and its store.
  • Update Vendor Updates a vendor's store details, commission arrangement, or profile.
  • Delete Vendor Deletes a vendor from the marketplace.
  • Update Vendor Status Approves or suspends a vendor, which is what takes a store live or takes it offline.
  • Batch Update Vendors Applies the same change to several vendors in one call.
  • Check Store URL Availability Checks whether a store slug is free before a vendor is created, which is the collision that is otherwise found after launch.
  • List Vendor Products Lists the products belonging to one vendor.
  • Get Vendor Stats Reads a vendor's trading figures, including sales and order counts.
  • List Vendor Categories Lists the product categories a vendor sells in.
  • Contact Vendor Sends a message to a vendor through the marketplace's own contact route.
  • Email Vendor Emails a vendor directly, used for onboarding instructions and operational notices.

Products

12
  • List Products Lists products. On a vendor credential this means that vendor's products, and on an administrator credential it means every vendor's, with no difference in the response to tell you which you got.
  • Get Product Retrieves one product with its price, stock, and vendor.
  • Create Product Creates a marketplace product.
  • Update Product Updates a product's fields.
  • Delete Product Deletes a product.
  • Duplicate Product Copies an existing product, which is the fast way to spin up near-identical listings.
  • Get Product Summary Reads the counts behind a vendor's catalog, such as published, draft, and out of stock.
  • Get Product Filter Data Returns the filter facets the storefront's product browsing is built from.
  • List Related Products Lists the products Dokan relates to a given one.
  • List Curated Products Lists the products the marketplace has curated for promotion.
  • List Product Categories Lists the marketplace's product categories.
  • Get Product Category Retrieves one product category.

Variations and Attributes

16
  • List Product Variations Lists a variable product's variations with their own price and stock.
  • Get Product Variation Retrieves one variation.
  • Create Product Variation Creates a variation on a variable product.
  • Update Product Variation Updates a variation's price, stock, or SKU.
  • Delete Product Variation Deletes a variation.
  • Batch Update Product Variations Creates, updates, or deletes several variations in one call.
  • List Product Attributes Lists the marketplace's global product attributes.
  • Get Product Attribute Retrieves one attribute with its type and ordering.
  • Create Product Attribute Creates a global attribute.
  • Update Product Attribute Updates an attribute.
  • Delete Product Attribute Deletes an attribute.
  • List Attribute Terms Lists the terms defined under one attribute.
  • Create Attribute Term Creates a term under an attribute.
  • Update Attribute Term Updates a term.
  • Delete Attribute Term Deletes a term.
  • Set Default Product Attributes Sets which attribute values a variable product presents as selected by default.

Orders

13
  • List Orders Lists orders, scoped by the credential the connection holds.
  • Get Order Retrieves one order with its lines, totals, customer, and vendor.
  • Update Order Status Moves one order to a new status.
  • Get Order Summary Reads the aggregate order counts and values behind a vendor's dashboard.
  • Bulk Update Order Status Moves several orders to a new status in one call.
  • List Order Notes Lists the notes attached to an order, both private and customer facing.
  • Create Order Note Adds a note to an order, which is where an agent records what it did and why.
  • Get Order Note Retrieves one order note.
  • Delete Order Note Deletes an order note.
  • List Order Downloads Lists the downloadable files granted on an order.
  • Grant Order Downloads Grants download access on an order, which is how a digital entitlement is issued.
  • Update Order Download Updates a granted download, such as its expiry or remaining uses.
  • Revoke Order Download Removes a download grant, ending the customer's access to that file.

Shipments

5
  • List Shipment Statuses Lists the shipment statuses the store's shipment tracking module recognizes.
  • List Order Shipments Lists the shipments recorded against an order.
  • Create Order Shipment Records a shipment with its carrier and tracking number.
  • Update Order Shipment Updates a shipment's tracking or status.
  • Delete Order Shipment Removes a shipment record from an order.

Withdrawals and Commission

11
  • List Withdrawals Lists withdrawal requests, filterable to the pending queue a payout run starts from.
  • Request Withdrawal Creates a withdrawal request on a vendor's behalf.
  • Get Withdrawal Retrieves one withdrawal request with its method, amount, and state.
  • Update Withdrawal Updates a single withdrawal request.
  • Delete Withdrawal Deletes a withdrawal request.
  • Get Withdrawal Balance Reads a vendor's available balance, which is the number an approval should be checked against.
  • Get Withdrawal Summary Reads the aggregate withdrawal position across the marketplace.
  • Get Withdrawal Charges Reads the charges a withdrawal method applies, so the vendor's net is known before approval.
  • List Withdrawal Payment Methods Lists the payout methods the marketplace supports.
  • Batch Update Withdrawals Approves or rejects several withdrawal requests in one call. The operation this page's human gate exists for.
  • Calculate Commission Computes the marketplace commission on an amount under the current arrangement.

Coupons

5
  • List Coupons Lists the marketplace's coupons.
  • Get Coupon Retrieves one coupon with its scope, limits, and expiry.
  • Create Coupon Creates a coupon.
  • Update Coupon Updates a coupon's value, limits, or expiry.
  • Delete Coupon Deletes a coupon.

Reviews

8
  • List Product Reviews Lists product reviews, including the held queue moderation starts from.
  • Update Product Review Status Publishes or holds a product review.
  • Get Product Review Summary Reads the aggregate rating and review counts for a product.
  • List Vendor Reviews Lists the reviews left about a vendor.
  • Create Vendor Review Creates a vendor review, used when migrating reviews in from another platform.
  • List Store Reviews Lists reviews of a store page.
  • Get Store Review Retrieves one store review.
  • Delete Store Review Permanently deletes a store review, which removes a customer's own words from a vendor's page.

Refunds

5
  • List Refunds Lists refund requests, including the queue awaiting a decision.
  • Approve Refund Approves a refund request, returning money to the customer against the vendor's account.
  • Cancel Refund Rejects a refund request.
  • Delete Refund Deletes a refund record.
  • Batch Update Refunds Approves or rejects several refund requests in one call.

Reports

4
  • Get Report Reads a marketplace report, such as sales overview or top sellers.
  • Get Withdraw Report Reads the payout report across vendors and periods.
  • Start Report Export Begins an asynchronous report export and returns its id. The first response is not the report.
  • Get Report Export Status Polls an export until it completes and returns the finished file reference.

Settings and Dashboard

6
  • Get Store Settings Reads a store's settings as a whole.
  • Get Settings Group Reads one group of settings.
  • Update Settings Group Updates a group of settings in one call.
  • Get Setting Reads one setting's value.
  • Update Setting Changes one setting.
  • Get Vendor Dashboard Reads the figures a vendor sees on their own dashboard.

Reference Data

2
  • List Countries Lists the countries the store recognizes, with their state lists.
  • List Continents Lists continents and the countries under them, used for shipping zones.

Customers

6
  • List Customers Lists the marketplace's customers.
  • Get Customer Retrieves one customer with their addresses.
  • Create Customer Creates a customer account.
  • Update Customer Updates a customer record.
  • Delete Customer Deletes a customer account.
  • Search Customers Searches customers by name or email, which is the lookup a support flow starts from.

Announcements

5
  • List Announcements Lists the announcements published to vendors.
  • Get Announcement Retrieves one announcement.
  • Create Announcement Publishes an announcement to all vendors, featured vendors, or a chosen list.
  • Update Announcement Updates an announcement.
  • Delete Announcement Deletes an announcement.

Store Categories

5
  • List Store Categories Lists the categories stores are grouped under on the marketplace.
  • Get Store Category Retrieves one store category.
  • Create Store Category Creates a store category.
  • Update Store Category Updates a store category.
  • Delete Store Category Deletes a store category.

Triggers

1 triggers

Event Triggers

1
  • On Store Event Fires on WooCommerce's own store events for orders, products, coupons, and customers, covering creation, update, and deletion for each. Dokan publishes no outbound webhook of its own, so this is built on the WooCommerce core Dokan requires, and registering it needs an administrator or shop manager credential. Deliveries are store wide rather than per vendor, so resolve the vendor inside the flow before acting on an event.

Frequently Asked Questions

What can FlowRunner do with Dokan?

FlowRunner agents can run Get Site Capabilities, List Vendors, and Get Vendor in Dokan, plus 114 more actions.

Does connecting Dokan to FlowRunner require OAuth?

No. Dokan connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.

Can Dokan trigger a FlowRunner workflow automatically?

Yes. Dokan supports 1 trigger that can start a FlowRunner workflow automatically.

Start building with Dokan

Free plan, no card required. Connect in minutes.