Approve or reject Dokan marketplace vendors from Slack

by Dokan · 26 views · created 2026-06-03 · HR

What this workflow does

This workflow has 16 nodes and runs on a schedule (every 15 minutes) (plus 2 other triggers). Along the way it connects Slack.

How it runs

Trigger: On a schedule (every 15 minutes) (plus 2 other triggers).

1. Fetch pending vendors (HTTP Request): calls an HTTP API
2. Verify token (approve) (If): checks a condition and branches into true / false
3. Verify token (reject) (If): checks a condition and branches into true / false
4. Skip already-announced (Code): runs custom JavaScript code
5. Activate vendor (HTTP Request): calls an HTTP API (POST)
6. Mark inactive (HTTP Request): calls an HTTP API (POST)
7. Post to Slack channel (Slack): uses Slack
8. Clear dedupe (approve) (Code): runs custom JavaScript code
9. Clear dedupe (reject) (Code): runs custom JavaScript code
10. Confirm approval (Slack) (Slack): uses Slack

…plus 3 more steps. See the full node list below.

Services it uses

Slack

Before you upgrade to n8n 3.0

Nodes used (7)

• Schedule Triggern8n-nodes-base.scheduleTrigger
• HTTP Requestn8n-nodes-base.httpRequest
• Coden8n-nodes-base.code
• Webhookn8n-nodes-base.webhook
• Ifn8n-nodes-base.if
• Slackn8n-nodes-base.slack
• Respond to Webhookn8n-nodes-base.respondToWebhook

From the author

Quick overview This workflow polls Dokan for newly registered vendors awaiting approval, posts each pending vendor to a Slack channel with Approve/Reject buttons, and updates the vendor’s status in Dokan when an admin clicks a button. How it works 1. Runs…

View the original on n8n.io → Check your own copy