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 Gmail Trigger, Google Sheets Trigger, Calendly Trigger, Email Read Imap, Google Drive Trigger, Gumroad Trigger, Local File Trigger and Form Trigger (+6 more) and works with an HTTP response to its caller, batch loops, calendar events, content publishing, custom code and a database (+8 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.
54 × Logic
9 × Other
8 × Trigger
7 × AI component
4 × File
3 × Code
3 × Flow control
3 × App
2 × Storage
1 × HTTP
1 × Messaging
1 × Schedule
1 × Webhook
AI Agent · No-Op
OpenAI · No-Op
Basic LLM Chain · No-Op
Information Extractor · No-Op
Question and Answer Chain · No-Op
Sentiment Analysis · No-Op
Summarization Chain · No-Op
Text Classifier · No-Op
Chat Memory Manager · No-Op
Bitly App · Bitly
Dropbox App · Dropbox
Gmail App · Gmail
+ 57 more steps
Security2 note(s) to review
0 Critical
1 High
1 Medium
0 Low
0 Info
HighRuns shell commands on the n8n host
"Execute Command" executes commands.
Confidence: high · Definite match
Suggested fix: Make sure no user-supplied data can reach the command string, and run n8n with the least privileges possible.
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 76/100.
Security70/100
−20: Runs shell commands on the n8n host
−10: Webhook accepts unauthenticated requests
StructuralNot assessed
The workflow file contains no real node connections.
Data flow100/100
Error handling40/100
−60: No error handling around external calls
Maintainability100/100
Integration risk80/100
−20: 14 distinct external services: each one is a dependency that can fail or change
Execution complexity80/100
−20: 90 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: Gmail Trigger, Google Sheets Trigger, Calendly Trigger, Email Read Imap, Google Drive Trigger, Gumroad Trigger, Local File Trigger, Form Trigger, Schedule, Webhook
HTTP requests
1
File storage operations
2
Messages sent
1
Custom code steps
3
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 Gmail Trigger, Google Sheets Trigger, Calendly Trigger, Email Read Imap, Google Drive Trigger, Gumroad Trigger, Local File Trigger and Form Trigger (+6 more) and works with an HTTP response to its caller, batch loops, calendar events, content publishing, custom code and a database (+8 more).
Services involved: Calendly, Dropbox, Email Read Imap, Email Send Tool, Gmail, Google Calendar, Google Docs and Google Drive (+6 more).
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.
Gmail Trigger App (Gmail Trigger)
Google Sheets Trigger App (Google Sheets Trigger)
Calendly Trigger
Email Trigger (IMAP) (Email Read Imap)
Google Drive Trigger
Gumroad Trigger
Local File Trigger
On form submission (Form Trigger)
Schedule Trigger (Schedule)
Webhook
When clicking 'Test workflow' (Manual Trigger)
Workflow Input Trigger (Execute Workflow Trigger)
Gmail Trigger
Google Sheets Trigger
Main flow
This file does not contain its real connections, so the execution order cannot be documented.
