Block 1 - Overview Note
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
Quick Overview This workflow receives purchase order requests via webhook, validates and enriches them, emails the correct approver through Gmail based on spend tier, checks department budgets in G...
n8n-nodes-base.stickynote, n8n-nodes-base.webhook, n8n-nodes-base.code, n8n-nodes-base.if, n8n-nodes-base.slack, n8n-nodes-base.set, n8n-nodes-base.switch, n8n-nodes-base.gmail
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Avkash Kakdiya.
Original n8n.io sourceThis workflow receives purchase order requests via webhook, validates and enriches them, emails the correct approver through Gmail based on spend tier, checks department budgets in Google Sheets, sends budget warnings to Slack, logs each PO to a tracker sheet, and confirms submission to the requester.
finance/purchase-order.YOUR_GOOGLE_SHEET_ID, and ensure the “PO Tracker” sheet has columns matching the fields the workflow appends (for example PO ID, Amount, Department, Status, Approver, and SLA).Monthly Cap and Current Spend fields and that the lookup is configured to match your department value.YOUR_FINANCE_SLACK_CHANNEL_ID, and select the channel that should receive invalid-submission and budget-breach alerts.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.
| Workflow | Route purchase order approvals and budget alerts with Gmail, Slack and Sheets |
|---|---|
| Complexity | advanced |
| Nodes | 18 |
| Categories | Document Extraction |
| Author | Avkash Kakdiya |
| Published | 16 Jun 2026 |
Use the JSON export at /data/workflows/16404/16404.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.
Quick Overview This workflow receives purchase order requests via webhook, validates and enriches them, emails the correct approver through Gmail based on spend tier, checks department budgets in G...
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 Document Extraction use case.