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, Form Trigger, Form Trigger, Schedule, Webhook and Webhook and works with an HTTP response to its caller, batch loops, custom code, a database, documents and email (+3 more).
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.
After you purchase
Every downloadable file is security-scanned before it becomes available to you — files stay locked until that check passes.
Delivery is via short-lived, authenticated download links issued only after your purchase is confirmed — never a public file address.
Workflow structureSteps 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.
82 × Logic
19 × Other
17 × Code
15 × App
12 × HTTP
11 × Database
6 × Flow control
3 × Webhook
2 × Trigger
1 × Messaging
1 × Schedule
Get projects · HTTP Request
Get sections · HTTP Request
Get Notion Databases · Notion
Prep Dropdown · Code
Prep Dropdown1 · Code
Generate config · Code
Choose Notion Database · Form
Choose Todoist Project · Form
Verify security token · If
Generate security token · Crypto
Store variables · Code
Get variables · Code
+ 134 more steps
Detected references
These steps name another step whose data they read. That shows a data dependency, not the order the steps run in.
Generate config reads data from Get sections
Generate config reads data from Get Notion Database ID
Generate config reads data from Get Todoist Project ID
Verify security token reads data from OAuth redirect
Store variables reads data from Todoist Webhook Setup Helper
Exchange Tokens reads data from OAuth redirect
Get Notion Database ID reads data from Get Notion Databases
Get Notion Database ID reads data from Choose Notion Database
Get Todoist Project ID reads data from Get projects
Get Todoist Project ID reads data from Choose Todoist Project
Todoist reads data from Globals
Notion reads data from Globals
Store Todoist ID reads data from Notion
Security3 note(s) to review
0 Critical
0 High
3 Medium
0 Low
0 Info
MediumWebhook 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.
MediumWebhook 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.
MediumWebhook 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.
HealthHow the technical score is made up
Overall 88/100.
Security70/100
−10: Webhook accepts unauthenticated requests
−10: Webhook accepts unauthenticated requests
−10: Webhook accepts unauthenticated requests
StructuralNot assessed
The workflow file contains no real node connections.
Data flow100/100
Error handling96/100
−4: Some external calls have no retry or fallback
Maintainability100/100
Integration risk100/100
Execution complexity80/100
−20: 174 executable nodes
Technical hygiene signals detected statically from the workflow file. Not a guarantee of correctness or fitness for a particular use.
Execution profileWhat one run touches
Starts from: Webhook, Form Trigger, Form Trigger, Schedule, Webhook, Webhook
HTTP requests
12
Database operations
11
Messages sent
1
Custom code steps
17
Counts are per-run minimums: loops and AI agents can repeat steps.
Loops and branching can't be measured without the workflow's connections.
Cost
No AI model usage detected
Other services may still bill under your own plans.
Simulation
Simulation unavailable for this workflow structure
The workflow file contains no real node connections.
DocumentationGenerated from the workflow's structure
What it does
This workflow starts from Webhook, Form Trigger, Form Trigger, Schedule, Webhook and Webhook and works with an HTTP response to its caller, batch loops, custom code, a database, documents and email (+3 more).
Services involved: Gmail, Notion and Redis.
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.
OAuth redirect (Webhook)
Notion-Todoist Sync Setup Helper (Form Trigger)
Todoist Webhook Setup Helper (Form Trigger)
Schedule Trigger (Schedule)
Notion Webhook (Webhook)
Todoist Webhook (Webhook)
Main flow
This file does not contain its real connections, so the execution order cannot be documented.
