January 22, 2026

Google Drive to Google Sheets, expense claims logged

Lisa Granqvist Partner Workflow Automation Expert

Get a free AI assessment → ⬇️ Use template

Expense claims fall apart in the boring parts. Receipts get buried in inboxes, totals don’t match what’s on the PDF, and finance ends up chasing people for missing fields.

If you run ops or finance, you already feel it. Team admins cleaning up after trips feel it too. This Drive Sheets expenses setup turns “send me the receipt” into a clean log and a clear summary, without the endless follow-ups.

Below you’ll see the exact automation, what it fixes, and how to roll it out without turning your reimbursement process into a new project.

How This Automation Works

The full n8n workflow, from trigger to final output:

n8n Workflow Template: Google Drive to Google Sheets, expense claims logged

Click to explore

flowchart LR

    subgraph sg0["On form submission Flow"]
        direction LR
        n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/form.svg' width='40' height='40' /></div><br/>On form submission"]
        n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Transform Output"]
        n2@{ icon: "mdi:cog", form: "rounded", label: "Upload file", pos: "b", h: 48 }
        n3@{ icon: "mdi:cog", form: "rounded", label: "Extract from File", pos: "b", h: 48 }
        n4@{ icon: "mdi:robot", form: "rounded", label: "DocClaim Assistant Agent", pos: "b", h: 48 }
        n5@{ icon: "mdi:database", form: "rounded", label: "Append row in sheet", pos: "b", h: 48 }
        n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Transform invoice record"]
        n7@{ icon: "mdi:robot", form: "rounded", label: "Structured Output Parser", pos: "b", h: 48 }
        n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Create HTML Email Template"]
        n9@{ icon: "mdi:message-outline", form: "rounded", label: "Send trip expense request to..", pos: "b", h: 48 }
        n10["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/code.svg' width='40' height='40' /></div><br/>Handle multiple files"]
        n11@{ icon: "mdi:brain", form: "rounded", label: "GPT", pos: "b", h: 48 }
        n11 -.-> n4
        n2 --> n6
        n1 --> n8
        n3 --> n4
        n0 --> n10
        n10 --> n2
        n10 --> n3
        n4 --> n1
        n7 -.-> n4
        n6 --> n5
        n8 --> n9
    end

    %% Styling
    classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
    classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
    classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
    classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
    classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
    classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
    classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
    classDef disabled stroke-dasharray: 5 5,opacity: 0.5
    class n0 trigger
    class n4,n7 ai
    class n11 aiModel
    class n5 database
    class n1,n6,n8,n10 code
    classDef customIcon fill:none,stroke:none
    class n0,n1,n6,n8,n10 customIcon

The Problem: Expense Claims Create Busywork (and Errors)

Manual expense claims feel simple until you do them at scale. One person submits three PDFs, another sends a blurry screenshot, and someone else forgets the trip dates entirely. Then finance has to interpret receipts, retype totals, guess tax, and reconcile it all against company policy. That’s not “admin.” It’s a recurring data-entry job with real consequences: wrong reimbursements, messy audit trails, and a constant drip of Slack pings and email threads that never quite die.

It adds up fast. Here’s where it usually breaks down.

Receipts arrive in different formats, so someone must normalize them before they’re usable.
Totals and tax get typed by hand, which means small mistakes become awkward reimbursement conversations.
There’s no single source of truth, so finance ends up building a “shadow spreadsheet” anyway.
Missing context (purpose, dates, department) forces follow-ups that delay payouts and reporting.

The Solution: Auto-Save Receipts, Extract Totals, Log to Sheets, Notify Finance

This workflow turns a trip claim into a repeatable, trackable intake process. An employee submits a form with trip details (name, department, purpose, dates) and uploads one or more receipt PDFs. Each file gets stored in a dedicated Google Drive folder for record-keeping. Then the workflow reads the PDF text and sends it to an AI agent (powered by an OpenAI chat model) that extracts structured fields like vendor, date, total, and tax. Finally, n8n formats the data into a clean claim record, appends one row per receipt into Google Sheets, and generates a readable HTML summary that gets emailed to finance so they can approve and pay without hunting for context.

The workflow starts at the form submission. It splits multiple uploads into individual receipts, processes each PDF, then merges the results into two outcomes: a tidy spreadsheet log and a finance-ready email summary. No extra tools for employees to learn, and no manual rekeying for finance.

What You Get: Automation vs. Results

What This Workflow Automates

Results You’ll Get

Saves every uploaded receipt PDF into a Google Drive folder automatically.
Extracts vendor, date, total, and tax from each PDF using an AI agent.
Formats each receipt into a standardized claim row for Google Sheets.
Builds and sends a finance-friendly HTML email summary of the whole trip.

Most teams reclaim about 2–5 hours a week that used to go to retyping receipts.
Fewer “what’s this charge?” messages because the trip context is included up front.
A clean audit trail in Drive, with a matching row in Sheets for every receipt.
More consistent tax and total capture, which reduces payout mistakes.
Faster month-end and easier reporting by department, trip, or employee.

Example: What This Looks Like

Say a consultant submits one trip with 6 receipt PDFs. Manually, finance usually spends about 8 minutes per receipt to open the file, find the total and tax, and type it into a sheet, plus another 10 minutes emailing questions. That’s roughly an hour per claim. With this workflow, the employee submits the form in about 5 minutes, n8n processes the PDFs in the background, and finance gets a single email summary and a pre-filled Google Sheet log. The “finance time” often drops to a quick review.

What You’ll Need

n8n instance (try n8n Cloud free)
Self-hosting option if you prefer (Hostinger works well)
Google Drive for storing uploaded receipt PDFs.
Google Sheets to log one row per expense.
OpenAI API key (get it from the OpenAI dashboard)

Skill level: Intermediate. You’ll connect Google credentials, add an API key, and tweak a couple of mapping fields to match your sheet columns.

Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).

How It Works

Form submission kicks everything off. An employee enters trip details and uploads one or more receipt PDFs via the n8n form trigger.

Receipts are split and stored. If multiple files are uploaded, n8n breaks them into individual items, then saves each PDF into the right Google Drive folder so nothing gets lost later.

The workflow reads each PDF and extracts the numbers. It pulls text from the file, then the AI agent (using an OpenAI chat model plus a structured output parser) returns consistent fields like vendor, total, tax, and date.

Two outputs are produced for finance. One path appends a clean row into Google Sheets per receipt. The other compiles the trip context and receipt breakdown into an HTML email and sends it to the finance inbox.

You can easily modify the fields captured on the form to match your policy, then adjust the sheet columns to fit your reporting. See the full implementation guide below for customization options.

Step-by-Step Implementation Guide

Step 1: Configure the Form Trigger

Set up the intake form that captures employee trip details and receipt uploads.

Add and open Form Intake Trigger.
Set Form Title to Business Trip Claim Submission.
Set Form Description to Submit your business trip expense claim by providing trip details and uploading all related invoices or receipts..
Confirm the form fields include Employee Name, Department, Trip Purpose, From Date, To Date, and a file upload labeled Receipts / Invoices restricted to .pdf.
Connect Form Intake Trigger to Split Uploaded Files.

Step 2: Connect Google Drive and Sheets

Store uploaded receipts in Drive and log metadata in Sheets.

Open Store File to Drive and set Name to =invoice-{{ $now.toFormat("yyyyLLdd-HHmmss") }}-{{$binary.data.fileName}}.
Choose the target Drive and folder in Store File to Drive (the folder ID currently uses [YOUR_ID]).
Credential Required: Connect your googleDriveOAuth2Api credentials in Store File to Drive.
Open Append Sheet Record, set Operation to append, and select the spreadsheet and sheet (currently [YOUR_ID] and Sheet1).
Credential Required: Connect your googleSheetsOAuth2Api credentials in Append Sheet Record.

Split Uploaded Files outputs to both Store File to Drive and Parse PDF Text in parallel.

Step 3: Set Up File Processing and Mapping

Split multiple uploads, map Drive metadata into a sheet row, and ensure receipt text extraction is enabled.

In Split Uploaded Files, keep the JavaScript that filters binary keys starting with Receipts___Invoices_ and outputs one file per item.
In Parse PDF Text, set Operation to pdf.
In Map Claim Row, keep Mode as runOnceForEachItem and map fields like EmployeeName, Department, and TripPurpose from Form Intake Trigger.
Ensure Store File to Drive connects to Map Claim Row, then to Append Sheet Record.

Step 4: Configure AI Receipt Extraction and Summary Build

Extract structured receipt data with AI, assemble claim data, and build an HTML summary.

In Receipt Analysis Agent, keep the prompt text and ensure Has Output Parser is enabled.
Open Structured Parsing Helper and verify the JSON schema example used for structured outputs (do not add credentials here).
Open OpenAI Mini Model and confirm the model is set to gpt-4.1-mini.
Credential Required: Connect your openAiApi credentials in OpenAI Mini Model.
In Assemble Claim Data, keep the JavaScript that builds the employee object and expenses array from the AI output.
In Build HTML Summary, keep the HTML generator script that formats the summary tables.

OpenAI Mini Model is connected as the language model for Receipt Analysis Agent — ensure credentials are added to OpenAI Mini Model, not the agent or Structured Parsing Helper.

Step 5: Configure the Email Output

Email the finance team a formatted summary after the HTML is built.

Open Email Finance Summary and set HTML to ={{ $json.html }}.
Set Subject to =Expense Claim Request - {{ $('Assemble Claim Data').item.json.employee.name }} – {{ $('Assemble Claim Data').item.json.employee.department }} - {{ $('Assemble Claim Data').item.json.employee.tripPurpose }}.
Credential Required: Connect your smtp credentials in Email Finance Summary.
Confirm Build HTML Summary connects to Email Finance Summary.

Step 6: Test and Activate Your Workflow

Validate the end-to-end process before turning it on for production use.

Click Test workflow and submit a sample form through Form Intake Trigger with one or more PDF receipts.
Verify the workflow runs both branches: files are uploaded by Store File to Drive and parsed by Parse PDF Text.
Confirm a new row appears in the spreadsheet from Append Sheet Record and the email is sent by Email Finance Summary.
When satisfied, toggle the workflow to Active for production use.

🔒

Unlock Full Step-by-Step Guide

Get the complete implementation guide + downloadable template

Common Gotchas

Google Drive credentials can expire or need specific permissions. If things break, check the Google connection inside n8n Credentials and confirm the Drive folder is accessible to that account first.
PDF text extraction can be messy when receipts are scans. If the AI output looks wrong, the issue is often the “Parse PDF Text” step returning incomplete text, not the model itself.
Default AI prompts are generic. Add your expense categories, tax rules, and preferred date format early or you will keep “fixing” rows in Google Sheets by hand.

Frequently Asked Questions

How long does it take to set up this Drive Sheets expenses automation?

About 30–60 minutes if your Google accounts are ready.

Do I need coding skills to automate Drive Sheets expenses logging?

No. You’ll mostly connect accounts and paste in an API key. You might do light field mapping if your Google Sheet columns differ.

Is n8n free to use for this Drive Sheets expenses workflow?

Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in OpenAI API usage, which is usually small per receipt but depends on how long your PDFs are.

Where can I host n8n to run this automation?

Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.

Can I customize this Drive Sheets expenses workflow for manager approval before finance?

Yes, and it’s a common tweak. You can route the “Build HTML Summary” output to a manager first, then only send “Email Finance Summary” if the manager approves. Teams also customize the agent prompt to auto-tag categories (travel, meals, accommodation) and to enforce policy rules like “no alcohol” or max daily meal totals.

Why is my Google Drive connection failing in this workflow?

Usually it’s permissions. The Google account connected in n8n must have access to the target Drive folder, and the OAuth consent can lose scope if the credential was edited. Reconnect the Google Drive credential in n8n, then retry with a single test receipt to confirm the folder path is correct.

How many receipts can this Drive Sheets expenses automation handle?

Plenty for normal business use. On n8n Cloud, your limit is mainly your monthly execution allowance, and each submitted claim can trigger multiple executions if there are multiple PDFs. If you self-host, there’s no execution cap, but throughput depends on your server and how quickly the AI and Google APIs respond.

Is this Drive Sheets expenses automation better than using Zapier or Make?

Often, yes, because this workflow benefits from multi-file handling, structured parsing, and custom code/mapping in the middle. n8n also gives you self-hosting, which keeps costs predictable when volume grows, and branching logic without making every extra step feel “premium.” Zapier or Make can still be fine for very simple receipt logging, but AI extraction plus email summaries gets complex fast. If you want a second opinion on tool choice, Talk to an automation expert.

Once this is running, receipts land where they should, numbers show up where you need them, and finance gets a summary that’s actually actionable. Set it up once, then let the workflow do the clerical work.

Need Help Setting This Up?

Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.

Lisa Granqvist

Workflow Automation Expert

Expert in workflow automation and no-code tools.

{
"id": null,
"meta": {
"instanceId": "26a750fe49587f6ae3183250c0ebf13bbb496f7bfcf73fd7518f2ed5295824f6",
"templateId": null,
"templateCredsSetupCompleted": null
},
"name": "Automated Expense Claim Processing System",
"tags": [],
"nodes": [
{
"id": "flowpast-topbar-6896",
"name": "Flowpast Branding",
"type": "n8n-nodes-base.stickyNote",
"position": [
0,
20
],
"parameters": {
"color": 7,
"width": 800,
"height": 80,
"content": "## Flowpast.com | Automation Workflow Library\n**\ud83d\udcd6 Full tutorial & setup guide:** flowpast.com"
},
"typeVersion": 1
},
{
"id": "6c4e9c64-e684-45c3-b979-b7de198df9b8",
"name": "Form Intake Trigger",
"type": "n8n-nodes-base.formTrigger",
"position": [
10,
125
],
"webhookId": "d2b90e45-460e-416f-8e8f-00cb2d370d9d",
"parameters": {
"options": [],
"formTitle": "Business Trip Claim Submission",
"formFields": {
"values": [
{
"fieldLabel": "Employee Name",
"placeholder": "Your full name",
"requiredField": true
},
{
"fieldType": "dropdown",
"fieldLabel": "Department",
"fieldOptions": {
"values": [
{
"option": "Sales"
},
{
"option": "Engineering"
},
{
"option": "HR"
},
{
"option": "Executive"
}
]
},
"requiredField": true
},
{
"fieldLabel": "Trip Purpose",
"placeholder": "Client meeting with ABC Corp",
"requiredField": true
},
{
"fieldType": "date",
"fieldLabel": "From Date",
"requiredField": true
},
{
"fieldType": "date",
"fieldLabel": "To Date",
"requiredField": true
},
{
"fieldType": "file",
"fieldLabel": "Receipts / Invoices",
"requiredField": true,
"acceptFileTypes": ".pdf"
}
]
},
"formDescription": "Submit your business trip expense claim by providing trip details and uploading all related invoices or receipts."
},
"typeVersion": 2.2
},
{
"id": "97927e98-c5b0-4a7c-a183-88e47919b050",
"name": "Split Uploaded Files",
"type": "n8n-nodes-base.code",
"position": [
250,
175
],
"parameters": {
"jsCode": "const data = $input.item.json;\nconst binaryData = $input.item.binary;\n\nlet output = [];\n\nObject.keys(binaryData)\n  .filter(label => label.startsWith(\"Receipts___Invoices_\"))\n  .forEach(label => {\n    output.push({\n      json: data,\n      binary: { data: binaryData[label] }\n    });\n  });\n\nreturn output;"
},
"typeVersion": 2
},
{
"id": "2d99c9cf-842c-4fec-af66-c87291a39383",
"name": "Store File to Drive",
"type": "n8n-nodes-base.googleDrive",
"position": [
480,
120
],
"parameters": {
"name": "=invoice-{{ $now.toFormat(\"yyyyLLdd-HHmmss\") }}-{{$binary.data.fileName}}",
"driveId": {
"__rl": true,
"mode": "list",
"value": "My Drive"
},
"options": [],
"folderId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://drive.google.com/drive/folders/1IPcko8bzogO3W4mxhrW2Q017QA0Lc5MI",
"cachedResultName": "SmartSales"
}
},
"credentials": {
"googleDriveOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 3
},
{
"id": "ac2f4a6e-d950-4aa8-b0b3-072eac9fbe0d",
"name": "Map Claim Row",
"type": "n8n-nodes-base.code",
"position": [
700,
185
],
"parameters": {
"mode": "runOnceForEachItem",
"jsCode": "const claimForm = $('Form Intake Trigger').first().json;\nreturn {\n      EmployeeName: claimForm[\"Employee Name\"],\n      Department: claimForm[\"Department\"],\n      TripPurpose: claimForm[\"Trip Purpose\"],\n      FromDate: claimForm[\"From Date\"],\n      ToDate: claimForm[\"To Date\"],\n      FileName: $json.name,\n      DownloadURL: $json.webContentLink,\n      Size: $json.size,\n      SubmittedAt: claimForm[\"submittedAt\"]\n    }"
},
"typeVersion": 2
},
{
"id": "ca934b9b-3c6a-45e3-8df6-90593691a6e3",
"name": "Append Sheet Record",
"type": "n8n-nodes-base.googleSheets",
"position": [
480,
325
],
"parameters": {
"columns": {
"value": [],
"schema": [
{
"id": "EmployeeName",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "EmployeeName",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Department",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "Department",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "TripPurpose",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "TripPurpose",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "FromDate",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "FromDate",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "ToDate",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "ToDate",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "FileName",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "FileName",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "DownloadURL",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "DownloadURL",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "Size",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "Size",
"defaultMatch": false,
"canBeUsedToMatch": true
},
{
"id": "SubmittedAt",
"type": "string",
"display": true,
"removed": false,
"required": false,
"displayName": "SubmittedAt",
"defaultMatch": false,
"canBeUsedToMatch": true
}
],
"mappingMode": "autoMapInputData",
"matchingColumns": [],
"attemptToConvertTypes": false,
"convertFieldsToString": false
},
"options": [],
"operation": "append",
"sheetName": {
"__rl": true,
"mode": "list",
"value": "gid=0",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/1qk6OebcuZkIRorf1k235ew88oZ-UlUJSyiHFqZYDbaU/edit#gid=0",
"cachedResultName": "Sheet1"
},
"documentId": {
"__rl": true,
"mode": "list",
"value": "[YOUR_ID]",
"cachedResultUrl": "https://docs.google.com/spreadsheets/d/1qk6OebcuZkIRorf1k235ew88oZ-UlUJSyiHFqZYDbaU/edit?usp=drivesdk",
"cachedResultName": "Invoices Tracking"
}
},
"credentials": {
"googleSheetsOAuth2Api": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 4.6
},
{
"id": "e8937db3-e66b-4638-84b1-06c847440628",
"name": "Parse PDF Text",
"type": "n8n-nodes-base.extractFromFile",
"position": [
450,
375
],
"parameters": {
"options": [],
"operation": "pdf"
},
"typeVersion": 1
},
{
"id": "36c4ad16-9720-4a79-b112-81b7836234be",
"name": "Receipt Analysis Agent",
"type": "@n8n/n8n-nodes-langchain.agent",
"position": [
220,
310
],
"parameters": {
"text": "=Extract all relevant information from thisreceipt or invoice below:\n---\n{{ $json.text }}\n---\nI need the output in a structured format suitable for generating a business expense claim report. Include fields like vendor name, invoice or receipt number, date, total amount, tax, payment method, currency, and item descriptions.",
"options": {
"systemMessage": "You are a document extraction assistant specialized in parsing receipts and invoices. Your role is to read and extract all relevant financial and business information from uploaded PDF files. Focus on identifying fields commonly used in expense claim reports, such as vendor name, invoice number, receipt number, date of issue, total amount, tax amount, currency, payment method, and itemized descriptions. Return the data in a clean, structured format. Do not include unnecessary text or decorative content. If some fields are missing, leave them blank. Maintain consistency in field naming and format."
},
"promptType": "define",
"hasOutputParser": true
},
"typeVersion": 2.1
},
{
"id": "5cd08389-4b62-41e8-845b-c321361e03d2",
"name": "OpenAI Mini Model",
"type": "@n8n/n8n-nodes-langchain.lmChatOpenAi",
"position": [
220,
485
],
"parameters": {
"model": {
"__rl": true,
"mode": "list",
"value": "gpt-4.1-mini",
"cachedResultName": "gpt-4.1-mini"
},
"options": []
},
"credentials": {
"openAiApi": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 1.2
},
{
"id": "4ab39a13-3479-40d8-b782-201416bb4cc8",
"name": "Structured Parsing Helper",
"type": "@n8n/n8n-nodes-langchain.outputParserStructured",
"position": [
440,
485
],
"parameters": {
"jsonSchemaExample": "{\n  \"expense_type\": \"Hotel\",\n  \"vendor_name\": \"Grand Central Hotel\",\n  \"invoice_number\": \"INV-20250802-001\",\n  \"receipt_number\": \"RCPT-56789\",\n  \"issue_date\": \"2025-08-02\",\n  \"total_amount\": 150.00,\n  \"tax_amount\": 15.00,\n  \"currency\": \"USD\",\n  \"payment_method\": \"Credit Card\",\n  \"location\": \"Hanoi, Vietnam\",\n  \"trip_purpose\": \"Client Meeting\",\n  \"trip_dates\": {\n    \"from\": \"2025-08-02\",\n    \"to\": \"2025-08-03\"\n  },\n  \"itemized_descriptions\": [\n    {\n      \"category\": \"Accommodation\",\n      \"description\": \"1 night stay - Deluxe Room\",\n      \"quantity\": 1,\n      \"unit_price\": 120.00,\n      \"line_total\": 120.00\n    },\n    {\n      \"category\": \"Service Charge\",\n      \"description\": \"Hotel service fee\",\n      \"quantity\": 1,\n      \"unit_price\": 10.00,\n      \"line_total\": 10.00\n    },\n    {\n      \"category\": \"Tax\",\n      \"description\": \"VAT 10%\",\n      \"quantity\": 1,\n      \"unit_price\": 15.00,\n      \"line_total\": 15.00\n    }\n  ],\n  \"notes\": \"\"\n}"
},
"typeVersion": 1.3
},
{
"id": "fca9ee73-d2da-4420-a541-8b641a70b097",
"name": "Assemble Claim Data",
"type": "n8n-nodes-base.code",
"position": [
0,
385
],
"parameters": {
"jsCode": "// Static or dynamic employee information\nconst profile = $('Form Intake Trigger').first().json;\nconst employee = {\n  name: profile[\"Employee Name\"],\n  department: profile[\"Department\"],\n  tripPurpose: profile[\"Trip Purpose\"],\n  fromDate: profile[\"From Date\"],\n  toDate: profile[\"To Date\"],\n};\n\n// Collect parsed expense outputs\nconst items = $input.all();\nconst expenses = items.map((item, index) => {\n  const data = item.json.output;\n\n  return {\n    index: index + 1,\n    expenseType: data.expense_type || \"\",\n    vendor: data.vendor_name || \"\",\n    invoiceNumber: data.invoice_number || \"\",\n    receiptNumber: data.receipt_number || \"\",\n    issueDate: data.issue_date || \"\",\n    totalAmount: data.total_amount || 0,\n    currency: data.currency || \"\",\n    taxAmount: data.tax_amount || 0,\n    paymentMethod: data.payment_method || \"\",\n    location: data.location || \"\",\n    notes: data.notes || \"\",\n    items: data.itemized_descriptions || []\n  };\n});\n\nreturn [\n  {\n    json: {\n      employee,\n      expenses\n    }\n  }\n];"
},
"typeVersion": 2
},
{
"id": "8ae7f569-3bb0-4d3b-91a2-fd0ae82649bc",
"name": "Build HTML Summary",
"type": "n8n-nodes-base.code",
"position": [
220,
565
],
"parameters": {
"jsCode": "const data = $input.first().json;\n\nconst { employee, expenses } = data;\n\n// Helper to generate expense summary rows\nconst expenseSummaryRows = expenses.map(expense => `\n  <tr>\n    <td>${expense.index}</td>\n    <td>${expense.expenseType}</td>\n    <td>${expense.vendor}</td>\n    <td>${expense.issueDate}</td>\n    <td>${expense.totalAmount}</td>\n    <td>${expense.currency}</td>\n    <td>${expense.taxAmount}</td>\n    <td>${expense.paymentMethod}</td>\n  </tr>\n`).join(\"\");\n\n// Helper to generate detailed tables for each expense\nconst expenseDetailSections = expenses.map(expense => {\n  const itemRows = (expense.items || []).map(item => `\n    <tr>\n      <td>${item.category}</td>\n      <td>${item.description}</td>\n      <td>${item.quantity}</td>\n      <td>${item.unit_price}</td>\n      <td>${item.line_total}</td>\n    </tr>\n  `).join(\"\");\n\n  return `\n    <div style=\"margin-top:32px;\">\n      <h4>Details for Expense #${expense.index} - ${expense.expenseType}</h4>\n      <p><strong>Vendor:</strong> ${expense.vendor}</p>\n      <p><strong>Invoice No.:</strong> ${expense.invoiceNumber}</p>\n      <p><strong>Receipt No.:</strong> ${expense.receiptNumber}</p>\n      <p><strong>Location:</strong> ${expense.location}</p>\n      <p><strong>Notes:</strong> ${expense.notes}</p>\n      <table border=\"1\" cellpadding=\"6\" cellspacing=\"0\" width=\"100%\" style=\"border-collapse:collapse;margin-top:10px;\">\n        <thead>\n          <tr style=\"background-color:#f4f4f4;\">\n            <th>Category</th>\n            <th>Description</th>\n            <th>Qty</th>\n            <th>Unit Price</th>\n            <th>Line Total</th>\n          </tr>\n        </thead>\n        <tbody>${itemRows}</tbody>\n      </table>\n    </div>\n  `;\n}).join(\"\");\n\nconst html = `\n<!DOCTYPE html>\n<html>\n<head>\n  <meta charset=\"UTF-8\" />\n  <style>\n    body { font-family: Arial, sans-serif; color: #333; }\n    h2 { color: #0077b6; }\n    table { width: 100%; border-collapse: collapse; margin-bottom: 24px; }\n    th, td { padding: 8px; border: 1px solid #ddd; font-size: 14px; }\n    th { background-color: #f4f4f4; text-align: left; }\n    h4 { margin-bottom: 5px; margin-top: 30px; color: #444; }\n  </style>\n<link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/104241.webp"><link rel="preload" as="image" href="https://flowpast.s3.eu-north-1.amazonaws.com/featured_blog_images/104241.webp"></head>
\n<body>\n\n  <h2>Expense Claim Request</h2>\n\n  <p><strong>Employee Name:</strong> ${employee.name}</p>\n  <p><strong>Department:</strong> ${employee.department}</p>\n  <p><strong>Trip Purpose:</strong> ${employee.tripPurpose}</p>\n  <p><strong>Trip Dates:</strong> ${employee.fromDate} to ${employee.toDate}</p>\n\n  <h3>Expense Summary</h3>\n  <table>\n    <thead>\n      <tr>\n        <th>#</th>\n        <th>Type</th>\n        <th>Vendor</th>\n        <th>Issue Date</th>\n        <th>Total</th>\n        <th>Currency</th>\n        <th>Tax</th>\n        <th>Payment</th>\n      </tr>\n    </thead>\n    <tbody>\n      ${expenseSummaryRows}\n    </tbody>\n  </table>\n\n  ${expenseDetailSections}\n\n  <p style=\"margin-top:32px;\">Thank you,<br/>${employee.name}</p>\n\n</body>\n</html>\n`;\n\nreturn [{ json: { html } }];"
},
"typeVersion": 2
},
{
"id": "c3755330-96b8-4aa6-9463-8bb77a6c178c",
"name": "Email Finance Summary",
"type": "n8n-nodes-base.emailSend",
"position": [
450,
540
],
"webhookId": "0ed7153b-1dbc-45af-8509-511e3478c079",
"parameters": {
"html": "={{ $json.html }}",
"options": [],
"subject": "=Expense Claim Request - {{ $('Assemble Claim Data').item.json.employee.name }} \u2013 {{ $('Assemble Claim Data').item.json.employee.department }} - {{ $('Assemble Claim Data').item.json.employee.tripPurpose }}"
},
"credentials": {
"smtp": {
"id": "credential-id",
"name": ""
}
},
"typeVersion": 2.1
}
],
"active": false,
"pinData": [],
"settings": {
"executionOrder": "v1"
},
"versionId": null,
"connections": {
"OpenAI Mini Model": {
"ai_languageModel": [
[
{
"node": "Receipt Analysis Agent",
"type": "ai_languageModel",
"index": 0
}
]
]
},
"Store File to Drive": {
"main": [
[
{
"node": "Map Claim Row",
"type": "main",
"index": 0
}
]
]
},
"Assemble Claim Data": {
"main": [
[
{
"node": "Build HTML Summary",
"type": "main",
"index": 0
}
]
]
},
"Parse PDF Text": {
"main": [
[
{
"node": "Receipt Analysis Agent",
"type": "main",
"index": 0
}
]
]
},
"Form Intake Trigger": {
"main": [
[
{
"node": "Split Uploaded Files",
"type": "main",
"index": 0
}
]
]
},
"Split Uploaded Files": {
"main": [
[
{
"node": "Store File to Drive",
"type": "main",
"index": 0
},
{
"node": "Parse PDF Text",
"type": "main",
"index": 0
}
]
]
},
"Receipt Analysis Agent": {
"main": [
[
{
"node": "Assemble Claim Data",
"type": "main",
"index": 0
}
]
]
},
"Structured Parsing Helper": {
"ai_outputParser": [
[
{
"node": "Receipt Analysis Agent",
"type": "ai_outputParser",
"index": 0
}
]
]
},
"Map Claim Row": {
"main": [
[
{
"node": "Append Sheet Record",
"type": "main",
"index": 0
}
]
]
},
"Build HTML Summary": {
"main": [
[
{
"node": "Email Finance Summary",
"type": "main",
"index": 0
}
]
]
}
}
}