Block 1 - Sticky Note5
- Type / Role
- n8n-nodes-base.stickyNote - stickyNote
- Config choices
- Version 1
This workflow is provided as-is. Please review and test before using in production.
Who’s it for This workflow is designed for employees who need to submit expense claims for business trips. It automates the process of extracting data from receipts/invoices, logging it to a Goo...
n8n-nodes-base.stickynote, n8n-nodes-base.code, n8n-nodes-base.googledrive, n8n-nodes-base.extractfromfile, n8n-nodes-base.googlesheets, @n8n/n8n-nodes-langchain.outputparserstructured, @n8n/n8n-nodes-langchain.lmchatopenai, n8n-nodes-base.gmail
This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by Jitesh Dugar.
Original n8n.io sourceThis workflow is designed for employees who need to submit expense claims for business trips. It automates the process of extracting data from receipts/invoices, logging it to a Google Sheet, and notifying the finance team via email.
Ideal users:
Create a form to capture:
Configure file upload node to store files in a specific Google Drive folder.
Set up DocClaim Agent using:
Transform extracted data into a structured claim record (Code Node).
Path 1: Save records to a Google Sheet (one row per expense).
Path 2:
Send Email node to notify the finance department (e.g., [email protected])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 | Automate employee trip expense processing with Jotform, OpenAI and Google Sheets |
|---|---|
| Complexity | advanced |
| Nodes | 17 |
| Categories | Invoice Processing, AI RAG |
| Author | Jitesh Dugar |
| Published | 13 Oct 2025 |
Use the JSON export at /data/workflows/9579/9579.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.
Who’s it for This workflow is designed for employees who need to submit expense claims for business trips. It automates the process of extracting data from receipts/invoices, logging it to a Goo...
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 Invoice Processing, AI RAG use case.