Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
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 ...
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
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Dokan.
Original n8n.io sourceThis 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.
inactive status via the Dokan REST API and keeps only vendors that have not already been announced.active in Dokan.inactive in Dokan.manage_woocommerce permission and add it as an n8n HTTP Basic Auth credential for the Dokan API requests.https://your-marketplace.com with your Dokan site URL in the Dokan API requests and the wp-admin “View profile” button link.https://your-n8n-instance.com in the Telegram inline button URLs with your public n8n base URL.YOUR_APPROVAL_TOKEN to a long random string and ensure it matches the token query parameter used in the Approve/Reject button URLs.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.
| Workflow | Approve or reject Dokan marketplace vendors from Telegram |
|---|---|
| Complexity | advanced |
| Nodes | 20 |
| Categories | HR |
| Author | Dokan |
| Published | 10 Jun 2026 |
Use the JSON export at /data/workflows/16246/16246.json as the source template for this automation.
Open n8n, import the downloaded JSON, and review each node before activating the workflow.
Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.
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.
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 ...
Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.
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.