The flow
Starts it 5Logic 5Service 6
The steps in the order they run, from what starts it.
- 1Every 15 minutesSchedule triggerStarts it
- 2Approve clickedWebhookStarts it
- 3Reject clickedWebhookStarts it
- 4Fetch pending vendorsHttp RequestService
- 5Verify token (approve)IfLogic
- 6Verify token (reject)IfLogic
- 7Skip already-announcedCodeLogic
- 8Activate vendorHttp RequestService
- 9Mark inactiveHttp RequestService
- 10Post to Slack channelSlackService
- 11Clear dedupe (approve)CodeLogic
- 12Clear dedupe (reject)CodeLogic
- 13Confirm approval (Slack)SlackService
- 14Confirm rejection (Slack)SlackService
- 15Respond: approvedRespond To WebhookStarts it
- 16Respond: rejectedRespond To WebhookStarts it
How it's built
- Starts on
- Another system calling it
- Steps
- 16, with 2 branches
- Size
- Medium: a working afternoon
- Connects to
- Slack
- Model
- None. This is plumbing, not judgement
Questions
What does it need to run?
An n8n account, plus your own Slack account. You connect your own accounts after importing it; none are included.
What starts it?
It starts on another system calling it.
Does it use AI?
No. Every step is fixed logic or a call to a service, so it does the same thing every time.
How long does it take to set up?
Plan an afternoon. 16 steps is enough that you should read each one before running it.
How do I import it?
Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.
Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 16 steps before you point it at anything that matters.