Route expense reimbursement approvals with forms and Duo Security
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
What this workflow does
This workflow has 7 nodes and runs when someone submits an n8n form (“Expense reimbursement request”). Along the way it connects Duo (community).
How it runs
Trigger: When someone submits an n8n form (“Expense reimbursement request”).
- Set Approval Context (Edit Fields (Set)): sets 1 field: managerUsername
- Check Manager Access (Duo Security): uses Duo Security
- Request Manager Approval (Duo Security): uses Duo Security
- Manager Approved? (If): checks a condition and branches into true / false
- Mark Expense Approved (Edit Fields (Set)): sets 2 fields: status, nextAction
- Record Expense Rejection (Edit Fields (Set)): sets 2 fields: status, nextAction
Services it uses
Before you upgrade to n8n 3.0
We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
- Check that n8n-nodes-duo is verified or supports 3.0 (used in Check Manager Access, Request Manager Approval).
Nodes used (4)
- n8n Form Trigger
n8n-nodes-base.formTrigger - Edit Fields (Set)
n8n-nodes-base.set - Duo Security
n8n-nodes-duo.duoSecurity - If
n8n-nodes-base.if
From the author
Quick overview A Duo Security Node Example Workflow This workflow collects an expense reimbursement request via an n8n form and uses Duo Security Push authentication to get a manager’s explicit approval or denial, then routes the request to approved or…