Route vendor invoices for AP review with Jev Classification, Google Sheets, Gmail, Telegram, and OpenAI
UnknownUnknown. This template uses community nodes we can't verify statically. Uses community nodes that can't be verified statically (unverified community packages are off by default in 3.0). Static check, last run 2026-10-19.
Community nodes
These come from third-party npm packages. In n8n 3.0 unverified community packages are off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).
n8n-nodes-jev-classification(Jev Ask Intake Questions)
Nodes used (12)
- Webhook
n8n-nodes-base.webhook - Edit Fields (Set)
n8n-nodes-base.set - If
n8n-nodes-base.if - Gmail
n8n-nodes-base.gmail - Jev Classification
n8n-nodes-jev-classification.jevClassification - Switch
n8n-nodes-base.switch - Google Sheets
n8n-nodes-base.googleSheets - Telegram
n8n-nodes-base.telegram - Schedule Trigger
n8n-nodes-base.scheduleTrigger - Summarize
n8n-nodes-base.summarize - AI Agent
@n8n/n8n-nodes-langchain.agent - OpenAI Chat Model
@n8n/n8n-nodes-langchain.lmChatOpenAi
What it does
Quick Overview This workflow receives vendor invoice submissions via webhook, uses Jev Classification to assess invoice completeness, logs the routing outcome to Google Sheets, and notifies Accounts Payable via Gmail and Telegram, plus sends a daily backlog brief generated with OpenAI. How it works 1. Receives an invoice submission via a POST webhook containing invoiceid, vendorname, and invoicetext. 2. Rejects submissions with missing or empty invoicetext and emails the AP team in Gmail with the reason. 3. Sends usable invoicetext to Jev Classification to answer intake questions (PO/reference present, amount present, vendor identity present, bank details present, currency, and an overall completeness score). 4. Parses Jev’s answers to derive a missing-details list, confidence gates, and a routing decision. 5. Routes invoices to either ready for payment run, vendor follow-up, or human AP review, and appends the invoice and decision details to the “Invoice Intake” Google Sheets tab. 6. For the ready route, checks Google Sheets for duplicate invoiceid entries and either alerts AP in Telegram (duplicate) or emails AP in Gmail to queue the invoice for three-way match. 7. On a daily 17:00 schedule, reads the Google Sheets log, summarizes invoice counts by route, uses OpenAI (via a LangChain agent) to draft a short backlog brief, and emails it to the AP team. Setup 1. Configure the source system to POST to the workflow webhook URL with invoiceid, vendorname, and invoicetext in the request body. 2. Add credentials for Jev Classification (TypeSafe), Google Sheets OAuth2, Gmail OAuth2, Telegram, and OpenAI. 3. Update the Google Sheets document ID and ensure it contains an “Invoice Intake” sheet with columns matching the logged fields (for example invoiceid, vendorname, route, status, and routedat). 4. Replace placeholder email addresses ([email protected] and [email protected]) and the Telegram chat ID with your real recipients.