Automate travel expense extraction with OCR, Mistral AI and Supabase
Travel Reimbursement - OCR & Expense Extraction Workflow
Overview
This is a lightweight n8n workflow that accepts chat input and uploaded receipts, runs OCR, stores parsed results in Supabase, and uses an AI agent to extract structured travel expense data and compute totals. Designed for zero retention operation and fast integration.
Workflow Structure
- Frontend: Chat UI trigger that accepts text and file uploads.
- Preprocessing: Binary normalization + per-file OCR request.
- Storage: Store OCR-parsed blocks in Supabase
temp_table. - Core AI: Travel reimbursement agent that extracts fields, infers missing values, and calculates totals using the Calculator tool.
- Output: Agent responds to the chat with a concise expense summary and breakdowns.
Chat Trigger (Frontend)
- Trigger node:
When chat message receivedpublic: true,allowFileUploads: true, sessionId used to tie uploads to the chat session.- Custom CSS + initial messages configured for user experience.
Binary Presence Check
- Node:
CHECK IF BINARY FILE IS PRESENT OR NOT(IF)- Checks whether incoming payload contains
files. - If files present -> route to
Split Out->NORMALIZE binary file->OCR (ANY OCR API)->STORE OCR OUTPUT->Merge. - If no files -> route directly to
Merge->Travel reimbursement agent.
- Checks whether incoming payload contains
Binary Normalization
- Node:
Split OutandNORMALIZE binary file(Code)Split Outextracts binary entries into adatafield.NORMALIZE binary filepicks the first binary key and rewrites payload tobinary.datafor consistent downstream shape.
OCR
- Node:
OCR (ANY OCR API )(HTTP Request)- Sends multipart/form-data to OCR endpoint, expects JSONL or JSON with
blocks. - Body includes
mode=single,output_type=jsonl,include_images=false.
- Sends multipart/form-data to OCR endpoint, expects JSONL or JSON with
Store OCR Output
- Node:
STORE OCR OUTPUT(Supabase)- Upserts into
temp_tablewithsession_id, parsedblocks, andfile_name. - Used by agent to fetch previously uploaded receipts for same session.
- Upserts into
Memory & Tooling
- Nodes:
Simple MemoryandSimple Memory1(memoryBufferWindow)- Keep last 10 messages for session context.
- Node:
Calculator1(toolCalculator)- Used by agent to sum multiple charges, handle currency arithmetic and totals.
Travel Reimbursement Agent (Core)
- Node:
Travel reimbursement agent(LangChain agent)- Model:
Mistral Cloud Chat Model(mistral-medium-latest) - Behavior:
- Parse OCR
blocksand non-file chat input. - Extract required fields:
vendor_name,category,invoice_date,checkin_date,checkout_date,time,currency,total_amount,notes,estimated. - When fields are missing, infer logically and mark
estimated: true. - Use Calculator tool to sum totals across multiple receipts.
- Fetch stored OCR entries from Supabase when user asks for session summaries.
- Always attempt extraction; never reply with "unclear" or ask for a reupload unless user requests audit-grade precision.
- Parse OCR
- Final output: Clean expense table and Grand Total formatted for chat.
- Model:
Data Flow Summary
- User sends chat message plus or minus file.
- IF file present -> Split Out -> Normalize -> OCR -> Store OCR output -> Merge with chat payload.
- Travel reimbursement agent consumes merged item, extracts fields, uses Calculator tool for sums, and replies with a formatted expense summary.
Integrations Used
| Service | Purpose | Credential |
|---------|---------|-----------|
| Mistral Cloud | LLM for agent | Mistral account |
| Supabase | Store parsed OCR blocks and session data | Supabase account |
| OCR API | Text extraction from images/PDFs | Configurable HTTP endpoint |
| n8n Core | Flow control, parsing, editing | Native |
Agent System Prompt Summary
> You are a Travel Expense Extraction and Calculation AI. Extract vendor, dates, currency, category, and total amounts from uploaded receipts, invoices, hotel bills, PDFs, and images. Infer values when necessary and mark them as estimated. When asked, fetch session entries from Supabase and compute totals using the Calculator tool. Respond in a concise business professional format with a category wise breakdown and a Grand Total. Never reply "unclear" or ask for a reupload unless explicitly asked.
Required final response format example:
Key Features
- Zero retention friendly design: OCR output stored only to
temp_tableper session. - Robust extraction with inference when OCR quality is imperfect.
- Session aware: agent retrieves stored receipts for consolidated totals.
- Calculator integration for accurate numeric sums and currency handling.
- Configurable OCR endpoint so you can swap providers without changing logic.
Setup Checklist
- Add Mistral Cloud and Supabase credentials.
- Configure OCR endpoint to accept multipart uploads and return
blocks. - Create
temp_tableschema withsession_id,file,file_name. - Test with single receipts, multipage PDFs, and mixed uploads.
- Validate agent responses and Calculator totals.
Summary
A practical n8n workflow for travel expense automation: accept receipts, run OCR, store parsed data per session, extract structured fields via an AI agent, compute totals, and return clean expense summaries in chat. Built for reliability and easy integration.
Need Help or More Workflows?
We can integrate this into your environment, tune the agent prompt, or adapt it for different OCR providers.
We can help you set it up for free β from connecting credentials to deploying it live.
Contact: shilpa.raju@digitalbiz.tech
Website: https://www.digitalbiz.tech
LinkedIn: https://www.linkedin.com/company/digital-biz-tech/
You can also DM us on LinkedIn for any help.
Automate Travel Expense Extraction with OCR, Mistral AI, and Supabase
This n8n workflow automates the process of extracting travel expense details from receipts using OCR, processing them with Mistral AI, and storing the structured data in Supabase. It simplifies expense management by converting unstructured receipt images into actionable data.
What it does
- Listens for Chat Messages: The workflow is triggered when a chat message is received, likely containing a prompt or an uploaded receipt.
- Initial HTTP Request: It makes an HTTP request, potentially to an OCR service or an internal API to process the incoming data (e.g., an uploaded image URL).
- Conditional Processing: An "If" node checks a condition, possibly to determine if the OCR extraction was successful or if further AI processing is needed.
- AI Agent with Mistral Cloud:
- If the condition is met, an "AI Agent" node (likely a LangChain agent) takes over.
- It uses a "Simple Memory" to maintain context during the conversation or processing.
- A "Calculator" tool is provided to the AI agent, suggesting it might perform calculations related to expenses (e.g., currency conversion, total calculations).
- The "Mistral Cloud Chat Model" acts as the large language model for the AI Agent, interpreting the OCR results and structuring the expense data.
- Code Execution: A "Code" node is present, which could be used for custom data manipulation, formatting, or validation of the extracted expense details before storage.
- Split Out Data: A "Split Out" node prepares the data for insertion into Supabase, potentially splitting an array of items into individual records.
- Store in Supabase: The processed and structured expense data is then inserted into a Supabase database.
- Merge Data: A "Merge" node combines data streams, likely to consolidate results from different branches of the "If" node or to prepare a final output.
Prerequisites/Requirements
- n8n Instance: A running n8n instance.
- Mistral AI Account: An API key for the Mistral Cloud Chat Model.
- Supabase Account: Access to a Supabase project with a configured database table for storing expense data.
- OCR Service (Implicit): Although not explicitly shown as a dedicated node, the "HTTP Request" and subsequent AI processing strongly imply the use of an OCR service to extract text from receipt images. You might need credentials or an endpoint for your chosen OCR solution.
- LangChain Credentials (if applicable): Depending on your LangChain setup, you might need specific credentials.
Setup/Usage
- Import the Workflow: Download the provided JSON and import it into your n8n instance.
- Configure Credentials:
- Mistral Cloud Chat Model: Configure the "Mistral Cloud Chat Model" node with your Mistral AI API key.
- Supabase: Set up a Supabase credential in n8n and configure the "Supabase" node to connect to your database and the relevant table for expenses.
- HTTP Request: Configure the "HTTP Request" node with the endpoint and any necessary authentication for your OCR service or initial data processing API.
- Configure Chat Trigger: Set up the "When chat message received" trigger according to your chat platform (e.g., Telegram, Slack, custom webhook) to receive incoming messages and attachments (receipts).
- Customize "If" Node: Adjust the conditions in the "If" node based on your specific requirements for processing OCR results.
- Customize "Code" Node: Modify the JavaScript code in the "Code" node to transform and validate the extracted expense data to match your Supabase table schema.
- Activate the Workflow: Once configured, activate the workflow.
The workflow will now automatically process incoming chat messages, extract expense details, and store them in Supabase.
Related Templates
AI multi-agent executive team for entrepreneurs with Gemini, Perplexity and WhatsApp
This workflow is an AI-powered multi-agent system built for startup founders and small business owners who want to automate decision-making, accountability, research, and communication, all through WhatsApp. The βvirtual executive team,β is designed to help small teams to work smarter. This workflow sends you market analysis, market and sales tips, It can also monitor what your competitors are doing using perplexity (Research agent) and help you stay a head, or make better decisions. And when you feeling stuck with your start-up accountability director is creative enough to break the barrier π― Core Features π§βπΌ 1. President (Super Agent) Acts as the main controller that coordinates all sub-agents. Routes messages, assigns tasks, and ensures workflow synchronization between the AI Directors. π 2. Sales & Marketing Director Uses SerpAPI to search for market opportunities, leads, and trends. Suggests marketing campaigns, keywords, or outreach ideas. Can analyze current engagement metrics to adjust content strategy. π΅οΈββοΈ 3. Business Research Director Powered by Perplexity AI for competitive and market analysis. Monitors competitor moves, social media engagement, and product changes. Provides concise insights to help the founder adapt and stay ahead. β° 4. Accountability Director Keeps the founder and executive team on track. Sends motivational nudges, task reminders, and progress reports. Promotes consistency and discipline β key traits for early-stage success. ποΈ 5. Executive Secretary Handles scheduling, email drafting, and reminders. Connects with Google Calendar, Gmail, and Sheets through OAuth. Automates follow-ups, meeting summaries, and notifications directly via WhatsApp. π¬ WhatsApp as the Main Interface Interact naturally with your AI team through WhatsApp Business API. All responses, updates, and summaries are delivered to your chat. Ideal for founders who want to manage operations on the go. βοΈ How It Works Trigger: The workflow starts from a WhatsApp Trigger node (via Meta Developer Account). Routing: The President agent analyzes the incoming message and determines which Director should handle it. Processing: Marketing or sales queries go to the Sales & Marketing Director. Research questions are handled by the Business Research Director. Accountability tasks are assigned to the Accountability Director. Scheduling or communication requests are managed by the Secretary. Collaboration: Each sub-agent returns results to the President, who summarizes and sends the reply back via WhatsApp. Memory: Context is maintained between sessions, ensuring personalized and coherent communication. π§© Integrations Required Gemini API β for general intelligence and task reasoning Supabase- for RAG and postgres persistent memory Perplexity API β for business and competitor analysis SerpAPI β for market research and opportunity scouting Google OAuth β to connect Sheets, Calendar, and Gmail WhatsApp Business API β for message triggers and responses π Benefits Acts like a team of tireless employees available 24/7. Saves time by automating research, reminders, and communication. Enhances accountability and strategy consistency for founders. Keeps operations centralized in a simple WhatsApp interface. π§° Setup Steps Create API credentials for: WhatsApp (via Meta Developer Account) Gemini, Perplexity, and SerpAPI Google OAuth (Sheets, Calendar, Gmail) Create a supabase account at supabase Add the credentials in the corresponding n8n nodes. Customize the system prompts for each Director based on your startupβs needs. Activate and start interacting with your virtual executive team on WhatsApp. Use Case You are a small organisation or start-up that can not afford hiring; marketing department, research department and secretar office, then this workflow is for you π‘ Need Customization? Want to tailor it for your startup or integrate with CRM tools like Notion or HubSpot? You can easily extend the workflow or contact the creator for personalized support. Consider adjusting the system prompt to suite your business
π How to transform unstructured email data into structured format with AI agent
This workflow automates the process of extracting structured, usable information from unstructured email messages across multiple platforms. It connects directly to Gmail, Outlook, and IMAP accounts, retrieves incoming emails, and sends their content to an AI-powered parsing agent built on OpenAI GPT models. The AI agent analyzes each email, identifies relevant details, and returns a clean JSON structure containing key fields: From β senderβs email address To β recipientβs email address Subject β email subject line Summary β short AI-generated summary of the email body The extracted information is then automatically inserted into an n8n Data Table, creating a structured database of email metadata and summaries ready for indexing, reporting, or integration with other tools. --- Key Benefits β Full Automation: Eliminates manual reading and data entry from incoming emails. β Multi-Source Integration: Handles data from different email providers seamlessly. β AI-Driven Accuracy: Uses advanced language models to interpret complex or unformatted content. β Structured Storage: Creates a standardized, query-ready dataset from previously unstructured text. β Time Efficiency: Processes emails in real time, improving productivity and response speed. *β Scalability: Easily extendable to handle additional sources or extract more data fields. --- How it works This workflow automates the transformation of unstructured email data into a structured, queryable format. It operates through a series of connected steps: Email Triggering: The workflow is initiated by one of three different email triggers (Gmail, Microsoft Outlook, or a generic IMAP account), which constantly monitor for new incoming emails. AI-Powered Parsing & Structuring: When a new email is detected, its raw, unstructured content is passed to a central "Parsing Agent." This agent uses a specified OpenAI language model to intelligently analyze the email text. Data Extraction & Standardization: Following a predefined system prompt, the AI agent extracts key information from the email, such as the sender, recipient, subject, and a generated summary. It then forces the output into a strict JSON structure using a "Structured Output Parser" node, ensuring data consistency. Data Storage: Finally, the clean, structured data (the from, to, subject, and summarize fields) is inserted as a new row into a specified n8n Data Table, creating a searchable and reportable database of email information. --- Set up steps To implement this workflow, follow these configuration steps: Prepare the Data Table: Create a new Data Table within n8n. Define the columns with the following names and string type: From, To, Subject, and Summary. Configure Email Credentials: Set up the credential connections for the email services you wish to use (Gmail OAuth2, Microsoft Outlook OAuth2, and/or IMAP). Ensure the accounts have the necessary permissions to read emails. Configure AI Model Credentials: Set up the OpenAI API credential with a valid API key. The workflow is configured to use the model, but this can be changed in the respective nodes if needed. Connect the Nodes: The workflow canvas is already correctly wired. Visually confirm that the email triggers are connected to the "Parsing Agent," which is connected to the "Insert row" (Data Table) node. Also, ensure the "OpenAI Chat Model" and "Structured Output Parser" are connected to the "Parsing Agent" as its AI model and output parser, respectively. Activate the Workflow: Save the workflow and toggle the "Active" switch to ON. The triggers will begin polling for new emails according to their schedule (e.g., every minute), and the automation will start processing incoming messages. --- Need help customizing? Contact me for consulting and support or add me on Linkedin.
Send WooCommerce discount coupons to customers via WhatsApp using Rapiwa API
Who is this for? This workflow is ideal for WooCommerce store owners who want to automatically send promotional WhatsApp messages to their customers when new coupons are created. Itβs designed for marketers and eCommerce managers looking to boost engagement, streamline coupon sharing, and track campaign performance effortlessly through Google Sheets. Overview This workflow listens for WooCommerce coupon creation events (coupon.created) and uses customer billing data to send promotional WhatsApp messages via the Rapiwa API. The flow formats the coupon data, cleans phone numbers, verifies WhatsApp registration with Rapiwa, sends the promotional message when verified, and logs each attempt to Google Sheets (separate sheets for verified/sent and unverified/not sent). What this Workflow Does Listens for new coupon creation events in WooCommerce via the WooCommerce Trigger node Retrieves all customer data from the WooCommerce store Processes customers in batches to control throughput Cleans and formats customer phone numbers for WhatsApp Verifies if phone numbers are valid WhatsApp accounts using Rapiwa API Sends personalized WhatsApp messages with coupon details to verified numbers Logs all activities to Google Sheets for tracking and analysis Handles both verified and unverified numbers appropriately Key Features Automated coupon distribution: Triggers when new coupons are created in WooCommerce Customer data retrieval: Fetches all customer information from WooCommerce Phone number validation: Verifies WhatsApp numbers before sending messages Personalized messaging: Includes customer name and coupon details in messages Dual logging system: Tracks both successful and failed message attempts Rate limiting: Uses batching and wait nodes to prevent API overload Data formatting: Structures coupon information for consistent messaging Google Sheet Column Structure A Google Sheet formatted like this β€ sample The workflow uses a Google Sheet with the following columns to track coupon distribution: | name | number | email | address1 | couponCode | couponTitle | couponType | couponAmount | createDate | expireDate | validity | status | | ----------- | ------------- | --------------------------------------------------- | --------- | ---------- | -------------- | ---------- | ------------ | ------------------- | ------------------- | ---------- | -------- | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | unverified | not sent | | Abdul Mannan | 8801322827799 | contact@spagreen.net | mirpur-DOHS | 62dhryst | eid offer 2025 | percent | 20.00 | 2025-09-11 06:08:02 | 2025-09-15 00:00:00 | verified | sent | Requirements n8n instance with the following nodes: WooCommerce Trigger, Code, SplitInBatches, HTTP Request, IF, Google Sheets, Wait WooCommerce store with API access Rapiwa account with API access for WhatsApp verification and messaging Google account with Sheets access Customer phone numbers in WooCommerce (stored in billing.phone field) Important Notes Phone Number Format: The workflow cleans phone numbers by removing all non-digit characters. Ensure your WooCommerce phone numbers are in a compatible format. API Rate Limits: Rapiwa and WooCommerce APIs have rate limits. Adjust batch sizes and wait times accordingly. Data Privacy: Ensure compliance with data protection regulations when sending marketing messages. Error Handling: The workflow logs unverified numbers but doesn't have extensive error handling. Consider adding error notifications for failed API calls. Message Content: The current message template references the first coupon only (coupons[0]). Adjust if you need to handle multiple coupons. Useful Links Dashboard: https://app.rapiwa.com Official Website: https://rapiwa.com Documentation: https://docs.rapiwa.com Support & Help WhatsApp: Chat on WhatsApp Discord: SpaGreen Community Facebook Group: SpaGreen Support Website: https://spagreen.net Developer Portfolio: Codecanyon SpaGreen