Gmailtrigger Workflow — AI Product | Success.
Gmailtrigger Workflow Gmailtrigger Workflow — free, ready-to-import n8n workflow (40 nodes, Email Gmail).
AI Product Reusable license
from $0
Understand this workflow before you use it.
Structure unavailable 1 to review Health 86/100 Workflow structure could not be fully reconstructed from the source file The source file lists the steps but not how they connect. Steps, integrations and security checks are analyzed; execution order and structure-based checks are not. This is a limitation of the file, not necessarily a problem with the workflow.
This workflow starts from Webhook and works with an HTTP response to its caller, custom code and email.
Steps 33
Integrations 0
Connections Unavailable
Complexity Advanced
Technical health 86/100
Security 1 to review Sale models Live demo Payments run through a deterministic mock provider in this environment — no real money moves.
**Gmailtrigger Workflow**
Category: Email Gmail · 40 nodes
Nodes/integrations used: aggregate, gmailTrigger, httpRequest, limit, respondToWebhook, webhook
How to use: download the JSON below, then in n8n choose Import from File (or open the demo link, copy the JSON, and paste with Ctrl+V into the n8n canvas). Add your own credentials and activate.
Source: Zie619/n8n-workflows (MIT). Credentials were removed and files modified for redistribution — see the library's ATTRIBUTION_AND_LICENSES.md for full license text.
Workflow structure Steps and detected references (no diagram)
Execution order can't be reliably reconstructed from this file, so no diagram is shown. Here is what the workflow contains.
25 × Logic 4 × Code 2 × HTTP 1 × Webhook Gmail Trigger · Gmail Trigger Gmail - Extract Received Headers · Code Gmail - Extract Original From IP · Set Gmail - Original IP Found? · If Gmail - Query IP Quality Score API · HTTP Request Gmail - Query IP API · HTTP Request Gmail - Authentication-Results Header? · If Gmail - Received-SPF Header? · If Gmail - Extract Authentication-Results Header · Code Gmail - Extract Received-SPF Header · Code Gmail - Determine Auth Values · Set Gmail - Set SPF Value · Set Gmail - No SPF Found · Set Gmail - Format Output · Set Gmail - DKIM Signature Found · Set Gmail - DKIM-Signature Header? · If Gmail - No DKIM Signature Found · Set Gmail - Set DMARC Value · Set Gmail - Extract DMARC Header · Code Gmail - DMARC Header? · If Gmail - No DMARC Header · Set Set Gmail Headers Here · Set Format Individual Auth Outputs1 · Set Format Combined Auth Output1 · Set Gmail - Webhook · Webhook Gmail - Remove Extra Received Headers · Limit Gmail - Merge · Merge Gmail - Aggregate · Aggregate Gmail - Set Headers · Set Gmail - Respond to Webhook · Respond to Webhook Aggregate Received-SPF Headers1 · Aggregate Set Gmail Webhook Headers Here · Set Skip IP Check · No-Op Detected references These steps name another step whose data they read. That shows a data dependency, not the order the steps run in.
Gmail - Extract Received Headers reads data from Gmail - Set Headers Gmail - Authentication-Results Header? reads data from Gmail - Set Headers Gmail - Received-SPF Header? reads data from Gmail - Set Headers Gmail - Extract Authentication-Results Header reads data from Gmail - Set Headers Gmail - Extract Received-SPF Header reads data from Gmail - Set Headers Gmail - DKIM-Signature Header? reads data from Gmail - Set Headers Gmail - Extract DMARC Header reads data from Gmail - Set Headers Gmail - DMARC Header? reads data from Gmail - Set Headers Format Individual Auth Outputs1 reads data from Gmail - Extract Original From IP Format Individual Auth Outputs1 reads data from Gmail - Query IP API Format Individual Auth Outputs1 reads data from Gmail - Query IP Quality Score API Format Combined Auth Output1 reads data from Security 1 note(s) to review 0 Critical0 High1 Medium0 Low0 InfoMedium Webhook accepts unauthenticated requests
Anyone who learns the webhook URL can trigger this workflow with arbitrary data.
Confidence: medium · Heuristic
Suggested fix: Enable header or basic auth on the Webhook node, or verify a signature from the sending service.
Health How the technical score is made up Overall 86/100 .
Technical hygiene signals detected statically from the workflow file. Not a guarantee of correctness or fitness for a particular use.
Execution profile What one run touches Starts from: Webhook
HTTP requests 2
Custom code steps 4 Loops and branching can't be measured without the workflow's connections.
Documentation Generated from the workflow's structure What it does This workflow starts from Webhook and works with an HTTP response to its caller, custom code and email.
This description is generated from the workflow's node types and wiring. It does not interpret each node's configuration.
Inputs Data enters through the trigger(s) below.
Some steps read fields from the incoming request body, query or headers.
Gmail - Webhook (Webhook) Main flow This file does not contain its real connections, so the execution order cannot be documented.
It contains: 25 × logic, 4 × code, 2 × http, 1 × webhook.
Some steps name another step whose data they read. This shows data dependencies only, not the order steps run in:
Gmail - Extract Received Headers (Code) reads data from Gmail - Set Headers (Set) Gmail - Authentication-Results Header? (If) reads data from Gmail - Set Headers (Set) Gmail - Received-SPF Header? (If) reads data from Gmail - Set Headers (Set) Gmail - Extract Authentication-Results Header (Code) reads data from Gmail - Set Headers (Set) Gmail - Extract Received-SPF Header (Code) reads data from Gmail - Set Headers (Set) Gmail - DKIM-Signature Header? (If) reads data from Gmail - Set Headers (Set) Gmail - Extract DMARC Header (Code) reads data from Gmail - Set Headers (Set) Gmail - DMARC Header? (If) reads data from Gmail - Set Headers (Set) Format Individual Auth Outputs1 (Set) reads data from Gmail - Extract Original From IP (Set) Format Individual Auth Outputs1 (Set) reads data from Gmail - Query IP API (HTTP Request) Outputs Without connection data, final outputs can't be identified precisely. These nodes write to external services:
Requirements No credentials appear to be required.
Setup Import the JSON file into n8n (Workflows → Import from File). Set environment variable(s): BASE_URL. Reconnect the nodes in the n8n editor: this file's original connections are missing. Run it once manually with test data before activating. Important considerations No node is configured to retry or continue on failure.
There is no Error Trigger in this workflow.
No error handling around external calls Generated automatically from the workflow's structure. Verify behaviour in n8n before relying on it.
Automated static analysis (engine 1.1.0). Nothing was executed. Not a guarantee of correctness or safety.
The seller has not attached downloadable files yet.
Uploaded by the seller and security-scanned before any buyer can download them.
Documentation
LeadBot 24h — WhatsApp AI Lead Qualification Bot — free, ready-to-import n8n workflow (6 nodes, WhatsApp).
AI Product Reusable
Gmail - Extract Original From IP
Format Combined Auth Output1 reads data from Gmail - Query IP API
Format Combined Auth Output1 reads data from Gmail - Query IP Quality Score API Be the first to review this product.
