Block 1 - Sticky Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
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...
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.slack, 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 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.
status=inactive from the Dokan REST API.active (approve) or inactive (reject), posts a confirmation message to Slack, and returns an HTML response page to the button click.chat:write and set YOUR_SLACK_CHANNEL_ID in the Slack message and confirmation steps.your-marketplace.com with your Dokan site URL in the Dokan API URLs and the Slack “View profile” button.your-n8n-instance.com in the Slack Approve/Reject button URLs and set a long random YOUR_APPROVAL_TOKEN to secure the approve/reject webhooks.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 Slack |
|---|---|
| Complexity | advanced |
| Nodes | 20 |
| Categories | HR |
| Author | Dokan |
| Published | 03 Jun 2026 |
Use the JSON export at /data/workflows/16103/16103.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 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...
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.