Capture LINE receipt expenses with Gemini, Google Drive and Google Sheets
Ready for 3.0What this workflow does
This workflow has 17 nodes and runs when an HTTP POST request hits its webhook URL. Along the way it connects Google Drive and Google Sheets. It also calls api.line.me and generativelanguage.googleapis.com over HTTP.
How it runs
Trigger: When an HTTP POST request hits its webhook URL.
- Set LINE Message Data (Edit Fields (Set)): sets 5 fields: messageType, messageId, replyToken…
- If: checks a condition and branches into true / false
- Fetch LINE Image Content (HTTP Request): calls an HTTP API
- Reply with Text Guide (HTTP Request): calls api.line.me (POST)
- Store Receipt in Google Drive (Google Drive): uses Google Drive
- Convert Image to Base (Code): runs custom JavaScript code
- Merge: merges the data from its input branches
- Submit to Gemini for Analysis (HTTP Request): calls generativelanguage.googleapis.com (POST)
- Check for Invoice Number (If): checks a condition and branches into true / false
- Extract Receipt Details (Code): runs custom JavaScript code
…plus 6 more steps. See the full node list below.
Services it uses
HTTP calls to: api.line.me, generativelanguage.googleapis.com
Before you upgrade to n8n 3.0
Nothing in this workflow is removed in n8n 3.0, so it should import and run after the upgrade.
Nodes used (8)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Google Drive
n8n-nodes-base.googleDrive - Code
n8n-nodes-base.code - Google Sheets
n8n-nodes-base.googleSheets - Merge
n8n-nodes-base.merge
From the author
Quick overview This workflow receives receipt images from LINE, uses Google Gemini to extract structured expense data, verifies Japanese invoice T-numbers via the NTA Web-API, archives the image in Google Drive, logs the expense to Google Sheets, and replies…