Two-Person Approval Change Requests with n8n Forms, Data Tables & Discord

Two-person approval change requests—automated in n8n with Forms, Data Tables, and Discord

This n8n workflow coordinates two-person approval change requests end-to-end: it collects requests via n8n Forms, notifies approvers through Discord webhooks, records every approval attempt in n8n Data Tables, and automatically marks each request as approved or expired when the time window closes.

What this workflow does

• One-time manual setup: creates three n8n Data Tables (approvers, requests, approval events), seeds two demo approvers, runs a self-test suite, and posts results to Discord.
• Receives a change request from an n8n Form and applies an approval policy (approval expiry window and required approver count). The workflow stores each new request as pending in the requests Data Table.
• Notifies approvers by sending a Discord message containing the request ID and details, then waits for the configured approval window to elapse.
• Validates second approver submissions via another n8n Form: it checks an approver secret against the approvers table and enforces rules such as “requester cannot approve” and “same approver cannot approve twice.”
• Records every attempt in the approval events Data Table and returns a form completion message confirming the record or explaining why it was refused.
• Finalizes outcomes when the window closes: counts distinct approvers from approval events, updates the request status to approved or expired, and shows the final result to the requester via the form completion page.

Use cases

• IT change management where every request needs two approvals within a defined time window.
• SaaS operations workflows requiring approval from two separate approvers to release or modify customer-impacting changes.
• Audit-friendly approval tracking for internal process governance using Data Tables and Discord notifications.

Technical details

• Integrations: n8n Forms, n8n Data Tables, Discord webhooks.
• Workflow nodes used: if, set, code, form, wait, discord.
• Core behavior: time-window enforcement, approver-secret validation against the approvers table, event logging to approval events Data Table, and status updates in the requests Data Table.