Skip to main content

Approve or reject Dokan marketplace vendors from Telegram

Workflow preview

Workflow preview
100%
Approve or reject Dokan marketplace vendors from Telegram preview
Open on n8n.io

1. Workflow Overview

Quick Overview This workflow polls your Dokan marketplace for vendors awaiting approval and posts each new pending vendor to Telegram with Approve/Reject actions, then updates the vendor status in ...

Best for

  • HR automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

n8n-nodes-base.stickynote, n8n-nodes-base.scheduletrigger, n8n-nodes-base.httprequest, n8n-nodes-base.code, n8n-nodes-base.webhook, n8n-nodes-base.if, n8n-nodes-base.respondtowebhook

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Dokan.

Original n8n.io source

1.1 Workflow description

Title
Approve or reject Dokan marketplace vendors from Telegram
Workflow name
Approve or reject Dokan marketplace vendors from Telegram

Quick Overview

This workflow polls your Dokan marketplace for vendors awaiting approval and posts each new pending vendor to Telegram with Approve/Reject actions, then updates the vendor status in Dokan via token-protected webhooks and confirms the result back in Telegram.

How it works

  1. Runs every 15 minutes on a schedule.
  2. Fetches up to 100 Dokan vendors with the inactive status via the Dokan REST API and keeps only vendors that have not already been announced.
  3. Posts each newly detected vendor to a Telegram chat with inline buttons to Approve, Reject, or open the vendor profile in wp-admin.
  4. When Approve is clicked, receives the webhook request, validates the shared token, and sets the vendor status to active in Dokan.
  5. When Reject is clicked, receives the webhook request, validates the shared token, and sets the vendor status to inactive in Dokan.
  6. After an approval or rejection, clears the saved de-duplication entry so the vendor can be re-announced if they return to pending, sends a confirmation message to Telegram, and returns an HTML response to close the browser tab.

Setup

  1. Create an application password (or Basic Auth user) in WordPress with manage_woocommerce permission and add it as an n8n HTTP Basic Auth credential for the Dokan API requests.
  2. Create a Telegram bot and provide its bot token, then set your target Telegram chat/channel ID in the Telegram sendMessage requests.
  3. Replace https://your-marketplace.com with your Dokan site URL in the Dokan API requests and the wp-admin “View profile” button link.
  4. Replace https://your-n8n-instance.com in the Telegram inline button URLs with your public n8n base URL.
  5. Set YOUR_APPROVAL_TOKEN to a long random string and ensure it matches the token query parameter used in the Approve/Reject button URLs.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Sticky Note

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 2 - Sticky Note1

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 3 - Sticky Note2

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 4 - Sticky Note3

Type / Role
n8n-nodes-base.stickyNote - stickyNote
Config choices
Version 1

Block 5 - Every 15 minutes

Type / Role
n8n-nodes-base.scheduleTrigger - scheduleTrigger
Config choices
Version 1.1

Block 6 - Fetch pending vendors

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 7 - Skip already-announced

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 8 - Approve clicked

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 9 - Verify token (approve)

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 10 - Activate vendor

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 11 - Clear dedupe (approve)

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 12 - Confirm approval (Telegram)

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 13 - Reject clicked

Type / Role
n8n-nodes-base.webhook - webhook
Config choices
Version 2

Block 14 - Verify token (reject)

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2

Block 15 - Mark inactive

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 16 - Clear dedupe (reject)

Type / Role
n8n-nodes-base.code - code
Config choices
Version 2

Block 17 - Confirm rejection (Telegram)

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 18 - Post to Telegram channel

Type / Role
n8n-nodes-base.httpRequest - httpRequest
Config choices
Version 4.2

Block 19 - Respond: approved

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.1

Block 20 - Respond: rejected

Type / Role
n8n-nodes-base.respondToWebhook - respondToWebhook
Config choices
Version 1.1

3. Summary Table

Workflow Approve or reject Dokan marketplace vendors from Telegram
Complexity advanced
Nodes 20
Categories HR
Author Dokan
Published 10 Jun 2026

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/16246/16246.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Frequently asked questions

What does Approve or reject Dokan marketplace vendors from Telegram do?

Quick Overview This workflow polls your Dokan marketplace for vendors awaiting approval and posts each new pending vendor to Telegram with Approve/Reject actions, then updates the vendor status in ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your HR use case.