Skip to main content

Route equipment requests to Procurement with manager approval via Gmail

Workflow preview

Workflow preview
100%
Route equipment requests to Procurement with manager approval via Gmail preview
Open on n8n.io

Important notice

This workflow is provided as-is. Please review and test before using in production.

1. Workflow Overview

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, ...

Best for

  • HR automation workflows
  • AI Chatbot automation workflows
  • advanced n8n builders looking for reusable templates

Tools used

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

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Gabriel Santos.

Original n8n.io source

1.1 Workflow description

Title
Route equipment requests to Procurement with manager approval via Gmail
Workflow name
Route equipment requests to Procurement with manager approval via Gmail

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 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.

Who’s it for

HR/IT/Operations teams that handle equipment requests, need a lightweight approval flow, and want clean, professional emails without manual drafting.

How it works

  1. Employee submits their enrollment number.

  2. Workflow fetches employee (and manager, if any).

  3. Employee describes the requested item(s).

  4. If a manager exists → an approval email (double opt-in) is sent to the manager.

    • Approved → notify employee and forward a polished request to Procurement.
    • Denied → notify employee.
  5. If the requester is a manager → skip approval and send directly to Procurement.

  6. End pages confirm the outcome.

Requirements

  • MySQL (or compatible DB) with an employees table (id, name, email, enrollment_number, manager).
  • Gmail credentials (OAuth) in n8n.
  • LLM provider (OpenAI or compatible) for message polishing.

How to customize

  • Replace the Procurement NoOp nodes with your email, helpdesk, or ERP integration.
  • Adjust email copy and tone in the LLM prompt nodes.
  • Add tracking IDs, SLA text, or CCs for auditing.
  • Style the forms with your brand (CSS blocks provided).

1.2 Logical Blocks

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.

2. Block-by-Block Analysis

Block 1 - Question form

Type / Role
n8n-nodes-base.formTrigger - formTrigger
Config choices
Version 2.3

Block 2 - If

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 3 - Return Employee not found

Type / Role
n8n-nodes-base.form - form
Config choices
Version 2.3

Block 4 - Get request information

Type / Role
n8n-nodes-base.form - form
Config choices
Version 2.3

Block 5 - OpenAI Chat Model

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 6 - Get Employee

Type / Role
n8n-nodes-base.mySql - mySql
Config choices
Version 2.5

Block 7 - Employee data

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 8 - Is approval required?

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 9 - Get Manager

Type / Role
n8n-nodes-base.mySql - mySql
Config choices
Version 2.5

Block 10 - Employee and Manager

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 11 - Set Manager field

Type / Role
n8n-nodes-base.set - set
Config choices
Version 3.4

Block 12 - Merge Employee data and request

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 13 - Approval request message

Type / Role
n8n-nodes-base.if - if
Config choices
Version 2.2

Block 14 - Create approval message

Type / Role
@n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices
Version 1.7

Block 15 - Data and message

Type / Role
n8n-nodes-base.merge - merge
Config choices
Version 3.2

Block 16 - End employee request

Type / Role
n8n-nodes-base.form - form
Config choices
Version 2.3

Block 17 - Structured Output Parser

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 18 - Notify approved request

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 19 - Notify denied request

Type / Role
n8n-nodes-base.gmail - gmail
Config choices
Version 2.1

Block 20 - OpenAI Chat Model1

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 21 - Structured Output Parser1

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Block 22 - Create request message

Type / Role
@n8n/n8n-nodes-langchain.chainLlm - chainLlm
Config choices
Version 1.7

Block 23 - OpenAI Chat Model2

Type / Role
@n8n/n8n-nodes-langchain.lmChatOpenAi - lmChatOpenAi
Config choices
Version 1.2

Block 24 - Structured Output Parser2

Type / Role
@n8n/n8n-nodes-langchain.outputParserStructured - outputParserStructured
Config choices
Version 1.3

Showing the first 24 of 55 workflow blocks. Download the JSON for the full node graph.

3. Summary Table

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

4. Reproducing the Workflow from Scratch

  1. 1. Download the workflow JSON

    Use the JSON export at /data/workflows/8728/8728.json as the source template for this automation.

  2. 2. Import the template into n8n

    Open n8n, import the downloaded JSON, and review each node before activating the workflow.

  3. 3. Configure credentials and variables

    Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.

  4. 4. Test with sample data

    Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.

  5. 5. Activate and monitor

    Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

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.

Frequently asked questions

What does Route equipment requests to Procurement with manager approval via Gmail do?

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, ...

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

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.