Templates / Track parcel returns and refunds with Google Drive, Gmail, and Kontoflux

Track parcel returns and refunds with Google Drive, Gmail, and Kontoflux

Unknown

by Florian · 17 views · created 2026-09-29 · Invoice Processing, AI RAG

Unknown. 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.

What this workflow does

This AI workflow has 46 nodes and runs on Google Drive events (file created) (plus 2 other triggers). Along the way it connects Google Drive, HTTP Request, Data table and Gmail and 3 more. It also calls api-eu.dhl.com and api.kontoflux.io over HTTP.

How it runs

Trigger: On Google Drive events (file created) (plus 2 other triggers).

Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
today > excected delivery date (Data table): get
today > expected refund date (Data table): get
download receipt scan (Google Drive): download
Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
Loop Over Items (Loop Over Items (Split in Batches)): loops over the items in batches
extract text from scan (Mistral OCR) (Mistral AI): uses Mistral AI
is DHL? (If): checks a condition and branches into true / false
Refund Agent (AI Agent): runs an AI agent, with model: Qwen 3.8 27B (Adacor) for Refund, Claude Claude Sonnet 4.6 (1NCE AI); 11 tools (Send an update, refund complete?, web search (Firecrawl), send friendly reminder?…)
Extract key data from markdown (Basic LLM Chain): sends a prompt to an LLM, with model: Claude 3 Haiku (1NCE AI), Mistral 3 (Adacor) for Extraction; output parser: carrier, tracking id, recipient, date

…plus 4 more steps. See the full node list below.

Services it uses

Google Drive HTTP Request Data table GmailGmail HitlOpenAI Chat ModelFirecrawl (community)

HTTP calls to: api-eu.dhl.com, api.kontoflux.io

Before you upgrade to n8n 3.0

We can't fully verify this one: it relies on 1 community package, and n8n 3.0 turns unverified community packages off by default (N8N_UNVERIFIED_PACKAGES_ENABLED=false).

Check that @mendable/n8n-nodes-firecrawl is verified or supports 3.0 (used in web search (Firecrawl), read web page (Firecrawl)).

Rarely used nodes in this template: n8n-nodes-base.gmailHitlTool

Nodes used (17)

Google Drive Triggern8n-nodes-base.googleDriveTrigger
Google Driven8n-nodes-base.googleDrive
Structured Output Parser@n8n/n8n-nodes-langchain.outputParserStructured
Loop Over Items (Split in Batches)n8n-nodes-base.splitInBatches
Http Request Tooln8n-nodes-base.httpRequestTool
Data Table Tooln8n-nodes-base.dataTableTool
Gmail Tooln8n-nodes-base.gmailTool
Gmail Hitl Tooln8n-nodes-base.gmailHitlTool
Firecrawl Tool@mendable/n8n-nodes-firecrawl.firecrawlTool
OpenAI Chat Model@n8n/n8n-nodes-langchain.lmChatOpenAi
Data tablen8n-nodes-base.dataTable
AI Agent@n8n/n8n-nodes-langchain.agent
Schedule Triggern8n-nodes-base.scheduleTrigger
Gmailn8n-nodes-base.gmail
Ifn8n-nodes-base.if
Basic LLM Chain@n8n/n8n-nodes-langchain.chainLlm
Mistral AIn8n-nodes-base.mistralAi

From the author

Quick overview This workflow tracks return shipments and refunds by extracting data from scanned return receipts in Google Drive, enriching it via Gmail and Kontoflux, storing everything in an n8n Data Table, and then monitoring DHL delivery status and refund…
Excerpt from Florian's description on n8n.io.

View the original on n8n.io → Check your own copy

Track parcel returns and refunds with Google Drive, Gmail, and Kontoflux

What this workflow does

How it runs

Services it uses

Before you upgrade to n8n 3.0

Nodes used (17)

From the author

Get the weekly “what broke” email