Block 1 - Question form
- Type / Role
- n8n-nodes-base.formTrigger - formTrigger
- Config choices
- Version 2.3
This workflow is provided as-is. Please review and test before using in production.
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, ...
n8n-nodes-base.formtrigger, n8n-nodes-base.if, n8n-nodes-base.form, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.mysql, n8n-nodes-base.set, n8n-nodes-base.merge, @n8n/n8n-nodes-langchain.chainllm
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Gabriel Santos.
Original n8n.io sourceThis 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 manager) or routes the request directly to Procurement (if the requester is a manager). All messages are written in a professional tone using an LLM, and emails are sent via Gmail with a built-in approve/deny step for managers.
HR/IT/Operations teams that handle equipment requests, need a lightweight approval flow, and want clean, professional emails without manual drafting.
Employee submits their enrollment number.
Workflow fetches employee (and manager, if any).
Employee describes the requested item(s).
If a manager exists → an approval email (double opt-in) is sent to the manager.
If the requester is a manager → skip approval and send directly to Procurement.
End pages confirm the outcome.
employees table (id, name, email, enrollment_number, manager).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.
Showing the first 24 of 55 workflow blocks. Download the JSON for the full node graph.
| Workflow | Route equipment requests to Procurement with manager approval via Gmail |
|---|---|
| Complexity | advanced |
| Nodes | 55 |
| Categories | HR, AI Chatbot |
| Author | Gabriel Santos |
| Published | 18 Sept 2025 |
Use the JSON export at /data/workflows/8728/8728.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.
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, ...
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, AI Chatbot use case.