OpenRuna
Sign in
← Workflows

Extract spend details (template)

24 nodes · gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini

Engine
n8n
Nodes
24
Trigger
scheduled/triggered
Source file
1443_Splitout_Extractfromfile_Automation_Triggered.json

Workflow flow

IntegrationsGmailExtractFromFileHtmlSplit OutOutputParserStructuredLmChatGoogleGeminiGoogle SheetsSwitchLmChatGroqChainLlm@n8n/n8n-nodes-langchain.outputParserStructured@n8n/n8n-nodes-langchain.lmChatGoogleGemini+4 more
100%
TRIGGER

Get invoice

Gmail

TRIGGER

Get payment

Gmail

Structured Output Parser1

@n8n/n8n-nodes-langchain.outputParserStructured

Google Gemini Chat Model1

@n8n/n8n-nodes-langchain.lmChatGoogleGemini

Groq Chat Model

@n8n/n8n-nodes-langchain.lmChatGroq

Structured Output Parser

@n8n/n8n-nodes-langchain.outputParserStructured

Extract invoice

ExtractFromFile

Extract payment

ExtractFromFile

Invoice data

Set

Payment data

Set

Switch

Switch

HTML

Html

Set data 1

Set

Set data 2

Set

Split Out

Split Out

Extract details1

@n8n/n8n-nodes-langchain.chainLlm

Set data 0

Set

Send1

Google Sheets

Merge

Merge

Extract details

@n8n/n8n-nodes-langchain.chainLlm

Send

Google Sheets

21 steps · flows top to bottom, branches left to right

Browse by integration

gmailextractFromFilehtmlsplitOutoutputParserStructuredlmChatGoogleGeminigoogleSheetsswitchlmChatGroqchainLlm
Browse all integrations →
Download n8n JSONDownload sanitized JSONDownload flow graph

Import into n8n

  1. Download the n8n JSON file (full or sanitized).
  2. In n8n: Workflows → Import from file.
  3. Open each node and reconnect credentials to your accounts.
  4. Test with manual execution before enabling triggers.

Sanitized JSON removes credential IDs — safer for sharing. Flow graph JSON is OpenRuna's lightweight format for diagrams and other tools, not n8n import.

View source corpus ↗

Overview

Free n8n workflow: Extract spend details (template). 24 nodes across gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini, googleSheets, switch, with a downloadable JSON and a visual flow diagram on OpenRuna.

What this workflow does

Built in n8n, "Extract spend details (template)" chains 24 nodes to move data between gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini, googleSheets, switch. 24 nodes · gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini A scheduled/triggered entry point kicks it off, and each node passes data to the next until the run completes. OpenRuna renders the node graph and offers the JSON export so you can import and adapt it in minutes. Use it to learn integration patterns, fork it for your own use case, or deploy it quickly after reconnecting credentials.

Use cases

  • Fork it to add error handling, retries, or a notification step without designing the 24-node flow from scratch.
  • Benchmark it against your current gmail integration to spot missing steps or redundant nodes.
  • Study how data moves from gmail to extractFromFile before building your own variant.
  • Share it with your team as a documented reference for scheduled/triggered automations in the gmail stack.

Example output

Imported into n8n, "Extract spend details (template)" exposes 24 configured nodes. Trigger type: scheduled/triggered. Integrations: gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini, googleSheets, switch. Open each node after import to map credentials to your own gmail and extractFromFile accounts. Run it once in test mode to verify any branch logic (Switch/IF nodes) before enabling production triggers.

Tips by platform

Claude

Ask Claude to turn the "Extract spend details (template)" JSON into a plain-English runbook, node by node. It can flag where gmail rate limits or missing retries might bite before you go live.

ChatGPT

Drop the workflow JSON or this OpenRuna page URL into ChatGPT and ask for a step-by-step runbook: triggers, branches, and which fields to customise for gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini, googleSheets, switch. Handy for onboarding teammates new to n8n.

Cursor

In Cursor, ask Agent mode to parameterise "Extract spend details (template)" — extract gmail IDs and secrets into environment variables without changing the 24-node structure.

Frequently asked questions

How do I import "Extract spend details (template)" into n8n?
Click Download n8n JSON on this page, then in n8n choose Workflows → Import from file and select the downloaded file. Reconnect credentials on each node — the export carries credential IDs from the original author's instance, not working secrets.
Which integrations does "Extract spend details (template)" use?
It uses: gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini, googleSheets, switch. The flow diagram above shows how each service connects across the 24 nodes. Filter OpenRuna by integration to find related workflows and tools.
Can I import a sanitized export without credentials?
Yes. Use "Download sanitized JSON" to strip credential references before sharing internally. You will still add your own gmail and extractFromFile credentials in n8n after import.
What trigger type does "Extract spend details (template)" use?
Trigger type: scheduled/triggered. After import, confirm the trigger node (webhook, schedule, or app event) matches your environment, then activate the workflow when you are ready to run it.
Is "Extract spend details (template)" free to use?
OpenRuna catalogs community n8n workflows under open licenses. Check the source corpus link for the original license; commercial use may require verifying the third-party API terms for gmail, extractFromFile, html, splitOut, outputParserStructured, lmChatGoogleGemini, googleSheets, switch.

Related resources