Microsoftoutlooktrigger Workflow — AI Product | Success.
Microsoftoutlooktrigger Workflow Microsoftoutlooktrigger Workflow — free, ready-to-import n8n workflow (41 nodes, Email Gmail).
AI Product Reusable license
from $0
Understand this workflow before you use it.
Structure unavailable 1 to review Health 84/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 34
Integrations 0
Connections Unavailable
Complexity Advanced
Technical health 84/100
Security 1 to review Sale models Live demo Payments run through a deterministic mock provider in this environment — no real money moves.
**Microsoftoutlooktrigger Workflow**
Category: Email Gmail · 41 nodes
Nodes/integrations used: aggregate, httpRequest, limit, microsoftOutlookTrigger, 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 3 × HTTP 1 × Webhook Trigger on New Email · Microsoft Outlook Trigger Retrieve Headers of Email · HTTP Request Extract Received Headers · Code Remove Extra Received Headers · Limit Extract Original From IP · Set Query IP Quality Score API · HTTP Request Query IP API · HTTP Request Authentication-Results Header? · If Extract Authentication-Results Header · Code Received-SPF Header? · If DKIM-Signature Header? · If Set SPF Value · Set Extract Received-SPF Header · Code DKIM Signature Found · Set DMARC Header? · If No DMARC Header · Set Extract DMARC Header · Code Set DMARC Value · Set Original IP Found? · If No DKIM Signature Found · Set Determine Auth Values · Set No SPF Found · Set Merge · Merge Aggregate · Aggregate No Operation, do nothing · No-Op Format Webhook Output · Set Format Individual Auth Outputs · Set Format Combined Auth Output · Set Respond to Webhook · Respond to Webhook Webhook1 · Webhook Set Headers · Set Aggregate Received-SPF Headers · Aggregate Set Headers Here · Set Set Webhook Headers Here · Set Detected references These steps name another step whose data they read. That shows a data dependency, not the order the steps run in.
Extract Received Headers reads data from Set Headers Authentication-Results Header? reads data from Set Headers Extract Authentication-Results Header reads data from Set Headers Received-SPF Header? reads data from Set Headers DKIM-Signature Header? reads data from Set Headers Extract Received-SPF Header reads data from Set Headers DMARC Header? reads data from Set Headers Extract DMARC Header reads data from Set Headers Format Individual Auth Outputs reads data from Extract Original From IP Format Individual Auth Outputs reads data from Query IP API Format Individual Auth Outputs reads data from Query IP Quality Score API Format Combined Auth Output reads data from Extract Original From IP 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 84/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 3
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.
Main flow This file does not contain its real connections, so the execution order cannot be documented.
It contains: 25 × logic, 4 × code, 3 × http, 1 × webhook.
Some steps name another step whose data they read. This shows data dependencies only, not the order steps run in:
Extract Received Headers (Code) reads data from Set Headers (Set) Authentication-Results Header? (If) reads data from Set Headers (Set) Extract Authentication-Results Header (Code) reads data from Set Headers (Set) Received-SPF Header? (If) reads data from Set Headers (Set) DKIM-Signature Header? (If) reads data from Set Headers (Set) Extract Received-SPF Header (Code) reads data from Set Headers (Set) DMARC Header? (If) reads data from Set Headers (Set) Extract DMARC Header (Code) reads data from Set Headers (Set) Format Individual Auth Outputs (Set) reads data from Extract Original From IP (Set) Format Individual Auth Outputs (Set) reads data from 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
Format Combined Auth Output
Query IP API
Format Combined Auth Output reads data from Query IP Quality Score API Be the first to review this product.
