N8n Workflow Automation 1.0.0
PassAudited by ClawScan on May 1, 2026.
Overview
This instruction-only skill coherently generates inactive n8n workflow designs, with sensible safeguards, but users should review generated automations before importing or activating them.
Before using a generated workflow, inspect the JSON in n8n, confirm it is inactive until you are ready, verify credential names and API scopes, and test with safe sample data before enabling writes, emails, or database updates.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If a user activates a generated workflow without review, it could send emails or write records to connected services.
Generated n8n workflows may write to external systems after a user imports and activates them. This is purpose-aligned and bounded by safeguards such as explicit JSON requests, inactive workflows, and credential review.
Targets: where to write results (email/Drive/Sheet/DB) and required fields.
Review all generated nodes, destinations, credential names, and scopes before importing or activating the workflow in n8n.
This does not show unsafe behavior, but it makes provenance slightly less tidy for users who rely on owner or slug metadata.
The registry metadata in the prompt lists a different owner ID and a versioned slug, so the packaged _meta.json is not fully consistent with the registry metadata.
"ownerId": "kn7crzxy2455jgg7b1swy21gtn7zd7c2", "slug": "n8n-workflow-automation"
Verify the publisher/source if provenance matters before installing, especially because the source and homepage are not provided.