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: enescingoz/awesome-n8n-templates (CC-BY-4.0). 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.
Arrows are real connections from the workflow file.
Select a step to see what it is and how it fits in.
Security2 note(s) to review
0 Critical
0 High
1 Medium
1 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.
LowUser-influenced URL path in HTTP request
The request host is fixed, but part of the path/query is built from data that can originate from a public entry point. Path injection is possible; full SSRF is not.
Confidence: medium · Heuristic · Via real connections
Suggested fix: Validate the target against an allow-list of hosts before the request, and block private/loopback/link-local ranges on the n8n host.
HealthHow the technical score is made up
Overall 88/100.
Security86/100
−10: Webhook accepts unauthenticated requests
−4: User-influenced URL path in HTTP request
Structural100/100
Data flow100/100
Error handling40/100
−60: No error handling around external calls
Maintainability100/100
Integration risk100/100
Execution complexity100/100
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
HTTP requests
2
Cost
No AI model usage detected
Other services may still bill under your own plans.
Simulation
Safe simulation available
A mock walk-through with placeholder data. Nothing real is run or contacted.
DocumentationGenerated from the workflow's structure
What it does
This workflow starts from Webhook and works with an HTTP response to its caller.
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.
POST /generate-song (Webhook)
Main flow
The longest path runs through 5 steps:
POST /generate-song (Webhook)
Tunova: start generation (HTTP Request)
Wait for render (Wait)
Tunova: get result (HTTP Request)
Return audio URL (Respond to Webhook)
Outputs
Return audio URL (Respond to Webhook)
Requirements
No credentials appear to be required.
Setup
Import the JSON file into n8n (Workflows → Import from File).
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.
