Reconcile trade mismatches in Google Sheets with Groq/OpenAI and Gmail alerts

Workflow preview

100%

Open on n8n.io

$20/month : Unlimited workflows

2500 executions/month

Try free

THE #1 IN WEB SCRAPING

Scrape any website without limits

Try free

HOSTINGER

Early Deal
DISCOUNT 20%

Self-hosted n8n

Unlimited workflows - from $4.99/mo

Try free

#1 hub for scraping, AI & automation

6000+ actors - $5 credits/mo

Try free

1. Workflow Overview

Trade Break Reconciliation Assistant This workflow automates trade reconciliation between internal and external systems using Google Sheets. It detects mismatches (price, quantity, amount, etc.), u...

Best for

Document Extraction automation workflows
AI Summarization automation workflows
advanced n8n builders looking for reusable templates

Tools used

@n8n/n8n-nodes-langchain.lmchatgroq, n8n-nodes-base.manualtrigger, n8n-nodes-base.googlesheets, n8n-nodes-base.merge, n8n-nodes-base.code, n8n-nodes-base.set, @n8n/n8n-nodes-langchain.agent, n8n-nodes-base.if

Source and attribution

This workflow is cataloged by N8N Workflows and links back to its original n8n.io source page by WeblineIndia.

Original n8n.io source

1.1 Workflow description

Title: Reconcile trade mismatches in Google Sheets with Groq/OpenAI and Gmail alerts
Workflow name: Reconcile trade mismatches in Google Sheets with Groq/OpenAI and Gmail alerts

Trade Break Reconciliation Assistant

This workflow automates trade reconciliation between internal and external systems using Google Sheets. It detects mismatches (price, quantity, amount, etc.), uses AI to generate insights, updates records and sends email alerts. This eliminates manual effort and improves accuracy.

Quick Implementation Steps

Connect your Google Sheets (Internal & External Trades)
Ensure both sheets contain a common trade_id
Connect Groq/OpenAI model in n8n
Configure Gmail for alerts
Run the workflow manually or schedule it
Monitor updates and alerts in real-time

What It Does

This workflow automates the reconciliation of trade data between two systems — internal and external — stored in Google Sheets. It compares records using trade_id and identifies mismatches such as differences in price, quantity, amount, side, currency or status.

Once mismatches are detected, the workflow classifies their severity and uses AI to generate meaningful insights, including the likely reason, explanation and recommended action. This transforms raw data into actionable intelligence.

Additionally, it updates both sheets with reconciliation results, handles missing trades by inserting records and sends detailed email alerts to ensure quick resolution of issues.

Who It's For

Finance & Operations teams
Trade reconciliation analysts
Back-office teams in trading firms
FinTech automation engineers
Anyone managing dual-system trade data

Requirements

n8n account (self-hosted or cloud)
Google Sheets account (with Internal & External trade data)
Groq/OpenAI API credentials
Gmail account (for alerts)
Proper sheet structure with fields like:
trade_id
price, quantity, amount
currency, status

How It Works & Setup Guide

1. Trigger

Workflow starts using Manual Trigger

2. Fetch Data

Fetch Internal Trades (Google Sheets)
Fetch External Trades (Google Sheets)

3. Merge Data

Uses SQL-based FULL OUTER JOIN on trade_id

4. Detect Mismatches

Compares:
Price
Quantity
Amount
Side
Currency
Status
Flags missing records

5. Classify Severity

High → Price/Amount issues
Medium → Quantity issues
Low → Other mismatches

6. AI Insight Generation

Sends trade data to AI model
Returns:
Reason
Explanation
Action

7. Data Update

Updates Internal & External Sheets
Fields updated:
mismatch
reason
severity
action

8. Handle Missing Trades

Inserts missing records if trade exists only in one system

9. Notifications

Sends email alerts:
Trade mismatch alerts
Missing trade alerts

How To Customize Nodes

Merge Node: Modify SQL logic for additional fields
Code Node (Detect Trade Breaks): Add/remove comparison conditions
AI Node: Customize prompt for deeper analysis
Severity Logic: Adjust classification rules
Google Sheets Nodes: Change column mappings
Email Node: Customize message format and recipients

Add-ons

Add Slack/Teams notifications
Schedule workflow (cron trigger)
Dashboard using Google Data Studio
Store logs in database (MySQL/PostgreSQL)
Add approval workflow before updating sheets

Use Case Examples

Daily trade reconciliation between broker and internal system
Detecting missing trades in financial systems
Identifying pricing discrepancies in trading operations
Automating audit-ready reconciliation reports
Real-time monitoring of trade data consistency

Troubleshooting Guide

Issue	Possible Cause	Solution
No data fetched	Wrong Sheet ID	Verify Google Sheets connection
Merge not working	Missing trade_id	Ensure both sheets have trade_id
AI output error	Invalid JSON response	Check AI prompt format
Emails not sent	Gmail not configured	Reconnect Gmail credentials
Wrong severity	Logic mismatch	Update severity code logic

Need Help?

If you need help setting up this workflow, customizing nodes or building advanced automation, feel free to reach out our n8n automation experts.

We can help you:

Customize this workflow for your business.
Add advanced features and integrations.
Build scalable automation systems.

1.2 Logical Blocks

This catalog entry is organized from the workflow JSON. The node-level section below shows the executable blocks available for review before importing the template.

2. Block-by-Block Analysis

Block 1 - Groq Chat Model

Type / Role: @n8n/n8n-nodes-langchain.lmChatGroq - lmChatGroq
Config choices: Version 1

Block 2 - Starting Trigger

Type / Role: n8n-nodes-base.manualTrigger - manualTrigger
Config choices: Version 1

Block 3 - Fetch Internal Trades

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 4 - Fetch External Trades

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 5 - Merge Internal & External Trades

Type / Role: n8n-nodes-base.merge - merge
Config choices: Version 3.2

Block 6 - Detect Trade Breaks

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 7 - Classify Severity

Type / Role: n8n-nodes-base.code - code
Config choices: Version 2

Block 8 - Prepare Trade Data

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 9 - Generate AI Reconciliation Insight

Type / Role: @n8n/n8n-nodes-langchain.agent - agent
Config choices: Version 3.1

Block 10 - Extract AI Output

Type / Role: n8n-nodes-base.set - set
Config choices: Version 3.4

Block 11 - Check Valid Row

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 12 - Check Trade Mismatch

Type / Role: n8n-nodes-base.if - if
Config choices: Version 2.3

Block 13 - Update Internal Trades Sheet

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 14 - Update External Trades Sheet

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 15 - Insert Missing Internal Trade

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 16 - Insert External Trade Record

Type / Role: n8n-nodes-base.googleSheets - googleSheets
Config choices: Version 4.7

Block 17 - Send Trade Break Alert Email

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.2

Block 18 - Send Missing Trade Alert Email

Type / Role: n8n-nodes-base.gmail - gmail
Config choices: Version 2.2

Block 19 - Sticky Note

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 20 - Sticky Note1

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 21 - Sticky Note2

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 22 - Sticky Note3

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 23 - Sticky Note4

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

Block 24 - Sticky Note5

Type / Role: n8n-nodes-base.stickyNote - stickyNote
Config choices: Version 1

3. Summary Table

Workflow	Reconcile trade mismatches in Google Sheets with Groq/OpenAI and Gmail alerts
Complexity	advanced
Nodes	24
Categories	Document Extraction, AI Summarization
Author	WeblineIndia
Published	20 May 2026

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

Use the JSON export at /data/workflows/15856/15856.json as the source template for this automation.
2. Import the template into n8n

Open n8n, import the downloaded JSON, and review each node before activating the workflow.
3. Configure credentials and variables

Replace placeholder credentials, API keys, webhook URLs, account IDs, and environment-specific values with your own settings.
4. Test with sample data

Run the workflow manually or in a staging workspace, inspect node output, and confirm downstream systems receive the expected data.
5. Activate and monitor

Enable the workflow only after testing, then monitor executions, errors, and rate limits during the first production runs.

5. General Notes & Resources

Review imported nodes carefully before activation. This catalog entry is intended to help you inspect the workflow structure, understand required services, and find related templates faster.

Node names, credentials, schedules, webhook paths, and external service limits may need adjustment for your workspace.

Download workflow JSON Original n8n.io source Document Extraction workflows AI Summarization workflows

Frequently asked questions

What does Reconcile trade mismatches in Google Sheets with Groq/OpenAI and Gmail alerts do?

What do I need before importing this workflow?

Review the workflow JSON, configure any required credentials in n8n, and test the automation in a safe workspace before using it in production.

Can I customize this workflow?

Yes. Use the block-by-block analysis and the downloadable JSON to inspect each node, then adjust credentials, prompts, schedules, filters, or destinations for your Document Extraction, AI Summarization use case.

WeblineIndia

216 workflows

Nodes

@n8n/n8n-nodes-langchain.lmchatgroq n8n-nodes-base.manualtrigger n8n-nodes-base.googlesheets n8n-nodes-base.merge n8n-nodes-base.code n8n-nodes-base.set @n8n/n8n-nodes-langchain.agent n8n-nodes-base.if

Complexity

advanced

Published 20 May 2026

Likes 0

View on n8n.io Download Workflow

Install path: /data/workflows/15856/15856.json

Share Your Workflow

Have a useful automation to share? Publish it and help the community.

Submit Your Template How to Submit

Related Workflows

Detect semantic duplicate website pages with Google Drive, Postgres and Ollama

## Quick overview This workflow scans HTML files in a Google Drive folder, extracts and stores page text in Postgres, generates local vector embeddings with Ollama, and uses PGVector similarity searches to produce CSV reports that flag semantically duplicate website pages. ## How it works 1. Starts manually and clears the existing PGVector embeddings table and the scraped page text table in Postgres. 2. Lists files in a specified Google Drive folder, filters to the target documents, and processes them in batches. 3. Downloads each HTML file from Google Drive, extracts the main body text, cleans it, and upserts the results into a Postgres table for scraped pages. 4. Reads the scraped page text back from Postgres in batches, splits it into overlapping chunks, and attaches page metadata (sheet_id, file_name, file_url) to each chunk. 5. Generates embeddings locally with Ollama and inserts the chunk vectors and metadata into Postgres (PGVector), deduplicating already-processed pages. 6. Builds an HNSW index in Postgres, computes chunk-to-chunk similarity matches and a pairwise page report, and exports the results as a CSV file. 7. Computes page-level centroid embeddings, finds highly similar page pairs, and exports a page-level duplicate report as a CSV file. ## Setup 1. Add Google Drive OAuth2 credentials and set the Google Drive folder URL/ID used to scan for your HTML files. 2. Add Postgres credentials for a database with the pgvector extension enabled and permissions to create/alter tables and indexes (including HNSW indexes). 3. Add an Ollama credential and ensure the embedding model mxbai-embed-large:latest is available on your Ollama instance. 4. Confirm your source files are HTML documents and that the workflow’s text extraction and similarity thresholds match your content and desired duplicate sensitivity. ## Requirements - Working instance of n8n, either self-hosted or on the cloud. Remember, this workflow can be computationally expensive. - Google Drive API (with OAuth setup in n8n credentials section) - Ollama (for open source models) or any Embedding model API - PostgreSQL with PGVector or any other vector database - PgAdmin (for PostgreSQL) or your interface to access database tables via SQL for troubleshooting (optional). ## Additional info Limitations and Enhancements: Physical system memory mxbai-embed-large Running through Ollama is free and private, but the embedding generation speed depends entirely on your hardware. The more system memory you have, the more data you can process in batches in the loop node. Similarity threshold and boilerplate content The cosine distance used in this workflow is 0.15 for chunk-level matching. And 0.05 (similarity above 95%) of the threshold is used for page-level centroid matching. This is only the starting point. Once you have the data, and especially if your data has more noise, you might need to tweak these thresholds for better matching. This workflow needs HTML files to extract text This workflow doesn't crawl a website or fetch pages by entering a URL. You need to download HTML files (rendered or source) for consumption. Use parallel processing and Cloud APIs Two sub-processes take the most time: Downloading HTML files from Google Drive Creating vector embeddings If you can use parallel processing in n8n and execute these sub-processes in parallel, the process will be done much faster. Additionally, if you can use cloud APIs for embedding, it may save some you some processing time as well. Use efficient SQL queries Since I am from a non-tech background and not a coder, I used a mix of Gemini, Perplexity and Claude to create SQL codes for this workflow. If you're better at it, you can run computationally efficient queries that would help you achieve better results with less computation expense and time.

View

Generate monthly BigQuery KPI PDF reports with Claude, Google Docs, Outlook and Teams

## Quick overview This workflow runs monthly to query KPI data from Google BigQuery, generates a narrative with Anthropic Claude, fills a Google Docs report template, exports it as a PDF, archives it to OneDrive, emails it via Microsoft Outlook, and posts a summary to Microsoft Teams. ## How it works 1. A schedule trigger fires on the 1st of every month at 07:00 and calculates the start and end dates of the previous full calendar month. 2. Four parallel BigQuery queries fetch revenue KPIs, top product categories, weekly sales trend, and top customers for that period. Each result set is tagged with a source label before merging. 3. All tagged rows are combined and aggregated into a single structured report payload containing KPI summaries, ranked tables, and company metadata. 4. The payload is split across two concurrent branches: one sends it to a Claude Sonnet LLM chain to generate an executive narrative with five sections (summary, revenue analysis, category insights, customer insights, and recommendation), and the other creates a named copy of a Google Docs template in your reports folder. 5. Once both branches complete, the narrative is merged into the report payload and the replacement requests for all template placeholders are constructed. 6. The Google Docs node applies all replacements in a single batchUpdate call, then the file is exported as a PDF via Google Drive. 7. The finished PDF is archived to OneDrive, emailed via Outlook with the report attached, and a formatted KPI summary card is posted to a Microsoft Teams channel. ## Setup 1. Set the following n8n environment variables before activating: GCP_PROJECT_ID, BQ_DATASET, GDOCS_TEMPLATE_FILE_ID, GDRIVE_REPORTS_FOLDER_ID, ONEDRIVE_REPORTS_FOLDER_ID, REPORT_RECIPIENTS, TEAMS_TEAM_ID, and TEAMS_CHANNEL_ID. 2. Connect a Google BigQuery credential and update the four SQL queries to match your dataset, table name, and column names. 3. Connect an Anthropic API credential to the Claude Chat Model sub-node, then manually wire its output to the ai_languageModel input (bottom connector) of the Create AI Narrative with Claude node on the canvas. 4. Connect Google Drive and Google Docs OAuth2 credentials. In Google Drive, create a master report template Doc containing the placeholder strings listed in the Customization section, note its file ID from the URL, and set GDOCS_TEMPLATE_FILE_ID accordingly. 5. Connect Microsoft OneDrive, Outlook, and Teams OAuth2 credentials. Retrieve your Teams team ID and channel ID using the Microsoft Graph Explorer and set the corresponding environment variables. ## Requirements - Google Cloud project with BigQuery enabled and an orders table matching the SQL schema in the workflow - Google Workspace account (Drive and Docs OAuth2 access) - Anthropic API key - Microsoft 365 account with OneDrive, Outlook, and Teams access ## Customization - To change the reporting cadence, update the cron expression in the schedule trigger: 0 7 * * 1 for weekly or 0 7 * * * for daily. - To adapt the SQL queries to your schema, replace orders, order_total, customer_id, is_new_customer, created_at, and product_category with your actual column names. - To change the AI model, update the model field in the Claude Chat Model sub-node. - To add more KPI sections, extend the SQL queries, the aggregation code in Consolidate BigQuery Data, and the replacements array in Construct Replacement Requests.

View

Ingest and search Cloudflare R2 media with Gemini, Groq Whisper, and Supabase

## Quick overview This workflow ingests images, PDFs, and videos from a Cloudflare R2 folder, uses Google Gemini to view pdfs, images and videos, Groq stt (Whisper) for video transcriptst - to generate searchable descriptions and tags, stores embeddings in a Supabase pgvector table. ## How it works 1. Receives a webhook request containing a Cloudflare R2 bucket and folder URL, then lists the objects in that folder. 2. Filters to supported file types, builds public CDN URLs and timestamps, and routes each item as an image, PDF, or video. 3. For images, calls Google Gemini with the image URL to generate structured metadata (summary, detailed description, tags, and scores). 4. For PDFs, calls Google Gemini to analyze the document URL and return the same structured metadata. 5. For videos, downloads each file locally, extracts representative frames with FFmpeg for Google Gemini visual analysis, extracts audio, transcribes it with Groq Whisper, and tags transcript chunks with Groq Llama. 6. Normalizes results into a single text “content” field plus JSON metadata, generates Google Gemini embeddings, and inserts the vectors into Supabase (pgvector). 7. Receives a separate webhook query, retrieves the most similar items from Supabase using embeddings, and returns ranked matches in the webhook response. ## Setup 1. Create a Cloudflare R2 bucket with publicly accessible object URLs, and add Cloudflare R2 credentials in n8n. 2. Set up a Supabase project with pgvector enabled and a table named `vec10`, then add Supabase credentials in n8n. 3. Add Google Gemini credentials (Google PaLM/Gemini API) for embeddings and provide an HTTP Header Auth credential for the Gemini HTTP requests. 4. Set the `GROQ_API_KEY` environment variable for the Groq Whisper transcription and Llama tag extraction calls. 5. If you enable video processing, install `curl`, `ffmpeg`, and `ffprobe` on the n8n host and update the local directory paths (temp root, frames directory, and video directory) in the workflow inputs. 6. Copy the ingest webhook (`/vector-ingest`) and query webhook (`/vector-query`) URLs and configure your upstream app to send the expected JSON payloads. ## Additional info Video: FFmpeg code nodes cut videos smartly into "video_frames" items and "video_transcripts" for easy handling and pgvector storage. Exposed webhook to vector query flow allows Voice Agent to find and display the full video, pulled from Cloudflare bucket, by the referenced matching video_frames or video_transcripts returned from vector query.

View

Need Custom Automation?

Get help designing a custom n8n workflow that connects your stack and fits your process.

Reconcile trade mismatches in Google Sheets with Groq/OpenAI and Gmail alerts

Workflow preview

1. Workflow Overview

Best for

Tools used

Source and attribution

1.1 Workflow description

Trade Break Reconciliation Assistant

Quick Implementation Steps

What It Does

Who It's For

Requirements

How It Works & Setup Guide

1. Trigger

2. Fetch Data

3. Merge Data

4. Detect Mismatches

5. Classify Severity

6. AI Insight Generation

7. Data Update

8. Handle Missing Trades

9. Notifications

How To Customize Nodes

Add-ons

Use Case Examples

Troubleshooting Guide

Need Help?

1.2 Logical Blocks

2. Block-by-Block Analysis

Block 1 - Groq Chat Model

Block 2 - Starting Trigger

Block 3 - Fetch Internal Trades

Block 4 - Fetch External Trades

Block 5 - Merge Internal & External Trades

Block 6 - Detect Trade Breaks

Block 7 - Classify Severity

Block 8 - Prepare Trade Data

Block 9 - Generate AI Reconciliation Insight

Block 10 - Extract AI Output

Block 11 - Check Valid Row

Block 12 - Check Trade Mismatch

Block 13 - Update Internal Trades Sheet

Block 14 - Update External Trades Sheet

Block 15 - Insert Missing Internal Trade

Block 16 - Insert External Trade Record

Block 17 - Send Trade Break Alert Email

Block 18 - Send Missing Trade Alert Email

Block 19 - Sticky Note

Block 20 - Sticky Note1

Block 21 - Sticky Note2

Block 22 - Sticky Note3

Block 23 - Sticky Note4

Block 24 - Sticky Note5

3. Summary Table

4. Reproducing the Workflow from Scratch

1. Download the workflow JSON

2. Import the template into n8n

3. Configure credentials and variables

4. Test with sample data

5. Activate and monitor

5. General Notes & Resources

Frequently asked questions