Verify billing-ready completion documents with OpenRouter and Google Sheets
Ready for 3.0What this workflow does
This workflow has 43 nodes and runs on Gmail events (plus 3 other triggers). Along the way it connects Gmail, Google Sheets and Google Drive. It also calls openrouter.ai over HTTP.
How it runs
Trigger: On Gmail events (plus 3 other triggers).
- Set Template Fields (Edit Fields (Set)): sets 16 fields: dispatchSheetId, dispatchSheetTab, podRegisterSheetTab…
- Set Audit Mode (Edit Fields (Set)): sets 1 field: executionType
- Set Reviewer Release Mode (Edit Fields (Set)): sets 1 field: executionType
- Identify Execution Type (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Prepare Email Attachments (Code): runs custom JavaScript code
- If: checks a condition and branches into true / false
- Build AI Request (Code): runs custom JavaScript code
- Read Audit Dispatches (Google Sheets): uses Google Sheets
- If: checks a condition and branches into true / false
…plus 29 more steps. See the full node list below.
Services it uses
HTTP calls to: openrouter.ai
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.
- Still check Gmail Trigger below v1.4 runs as v1.4 (drafts skipped, max emails per poll) (When Gmail Email Received).
Nodes used (10)
- Gmail Trigger
n8n-nodes-base.gmailTrigger - Webhook
n8n-nodes-base.webhook - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Edit Fields (Set)
n8n-nodes-base.set - Code
n8n-nodes-base.code - If
n8n-nodes-base.if - HTTP Request
n8n-nodes-base.httpRequest - Google Sheets
n8n-nodes-base.googleSheets - Google Drive
n8n-nodes-base.googleDrive - Gmail
n8n-nodes-base.gmail
From the author
Quick overview This workflow ingests proof-of-delivery and completion documents from Gmail or a webhook, extracts key fields with an OpenRouter vision model, reconciles them against Google Sheets dispatch data, archives evidence to Google Drive, and routes…