Route equipment requests to Procurement with manager approval via Gmail
Ready for 3.0What this workflow does
This AI workflow has 30 nodes and runs when someone submits an n8n form (“Equipment Request Form”). Along the way it connects OpenAI Chat Model, MySQL and Gmail.
How it runs
Trigger: When someone submits an n8n form (“Equipment Request Form”).
- Get Employee (MySQL): select
- If: checks a condition and branches into true / false
- Return Employee not found (n8n Form): shows the next form page
- Employee data (Edit Fields (Set)): sets 5 fields: employee.enrollment_number, employee.name, employee.email…
- Get request information (n8n Form): shows the next form page
- Is approval required? (If): checks a condition and branches into true / false
- Merge: merges the data from its input branches
- Get Manager (MySQL): select
- Employee and Manager (Merge): merges the data from its input branches
- Approval request message (If): checks a condition and branches into true / false
…plus 11 more steps. See the full node list below.
Services it uses
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (11)
- n8n Form Trigger
n8n-nodes-base.formTrigger - If
n8n-nodes-base.if - n8n Form
n8n-nodes-base.form - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi - MySQL
n8n-nodes-base.mySql - Edit Fields (Set)
n8n-nodes-base.set - Merge
n8n-nodes-base.merge - Basic LLM Chain
@n8n/n8n-nodes-langchain.chainLlm - Structured Output Parser
@n8n/n8n-nodes-langchain.outputParserStructured - Gmail
n8n-nodes-base.gmail - No Operation, do nothing
n8n-nodes-base.noOp
From the author
This workflow streamlines how employees request equipment/items and how those requests reach the Procurement team. It validates the employee by enrollment number, detects whether a manager exists, and then either requests approval (if the requester has a…