Générateur de workflows n8n

VérifiéPrudence

Génère des fichiers JSON de workflow n8n à partir de descriptions utilisateur, prêts à télécharger et importer. Permet de créer des automatisations sans coder manuellement la structure JSON. Utile lorsque l'utilisateur décrit un besoin d'automatisation et souhaite obtenir un fichier .json fonctionnel pour n8n.

Spar Skills Guide Bot
ProductiviteIntermédiaire
4002/06/2026
Claude CodeCursorWindsurfCopilotCodex
#n8n#workflow-automation#json-generation#low-code

Recommandé pour

Notre avis

Génère des fichiers JSON de workflow n8n à partir de descriptions utilisateur pour téléchargement et importation dans n8n.

Points forts

  • Génération minimaliste de nœuds
  • Modèles de nœuds prêts à l'emploi
  • Validation de la structure JSON
  • Facilité d'importation

Limites

  • Nécessite une configuration manuelle des identifiants
  • Pas de support pour les branchements complexes
  • Ne génère pas de logique conditionnelle avancée
Quand l'utiliser

Lorsque vous avez besoin d'un squelette de workflow n8n rapide basé sur une description simple.

Quand l'éviter

Lorsque vous avez besoin d'un workflow entièrement configuré avec des identifiants réels ou une gestion d'erreurs complexe.

Analyse de sécurité

Prudence
Score qualité90/100

The skill includes a command to run a Python script (n8n_generator.py) that is not reviewed, and the generated workflows can execute arbitrary code via Code nodes, requiring caution in deployment.

Points d'attention
  • Instructs execution of a Python script from a local file path, which could execute arbitrary code without sandboxing
  • Generated n8n workflows may include user-specified logic in Code nodes, which could introduce security risks when executed

Exemples

Weekly database backup to FTP
Create a weekly database backup workflow using a schedule trigger and a Postgres node, then save to FTP.
Webhook to Slack message
Set up a webhook that receives a POST request and sends a Slack message with the payload.
Form submission email notification
Build an email notification workflow triggered by a form submission via webhook.

name: generating-n8n-workflows description: Generates n8n workflow JSON files from user prompts for download and import. Use when user wants to create n8n automation, mentions workflow generation, or needs a .json file for n8n import.

n8n Workflow Generator

Generates clean, minimal n8n workflow JSON files based on user requirements.

When to use this skill

  • User wants to create an n8n workflow
  • User provides a prompt describing automation needs
  • User needs a downloadable .json file for n8n import
  • User mentions specific integrations (Slack, Email, HTTP, etc.)

Workflow

  • [ ] Parse user prompt for workflow requirements
  • [ ] Identify trigger type and action nodes needed
  • [ ] Generate minimal workflow JSON (no extra nodes)
  • [ ] Validate JSON structure against n8n schema
  • [ ] Provide download-ready .json file

Instructions

Step 1: Parse User Prompt

Extract from the user's description:

  • Trigger: What starts the workflow? (webhook, schedule, manual, trigger-node)
  • Actions: What should happen? (send email, HTTP request, database operation)
  • Integrations: Which services? (Slack, Gmail, PostgreSQL, etc.)
  • Data flow: How does data move between nodes?

Step 2: Node Selection Rules

CRITICAL: Generate ONLY necessary nodes. No extras.

| User Needs | Minimal Nodes | |------------|---------------| | "Send Slack message daily" | Schedule Trigger → Slack | | "HTTP webhook to save data" | Webhook → HTTP Request | | "Email on form submit" | Webhook → Send Email | | "Database backup weekly" | Schedule → Postgres → FTP |

Forbidden extras:

  • No debug nodes
  • No unnecessary Set nodes
  • No extra HTTP requests
  • No duplicate triggers
  • No unused credentials placeholders

Step 3: Generate Workflow JSON

Required structure:

{
  "name": "Workflow Name",
  "nodes": [
    {
      "id": "uuid",
      "name": "Trigger",
      "type": "n8n-nodes-base.webhook",
      "position": [250, 300],
      "parameters": {}
    },
    {
      "id": "uuid",
      "name": "Action",
      "type": "n8n-nodes-base.slack",
      "position": [450, 300],
      "parameters": {}
    }
  ],
  "connections": {
    "Trigger": {
      "main": [[{"node": "Action", "type": "main", "index": 0}]]
    }
  }
}

Step 4: Position Guidelines

  • Start trigger at [250, 300]
  • Each subsequent node: +200 on X axis
  • Keep Y at 300 for simple flows
  • Use [250, 200] and [250, 400] for branches

Step 5: Common Node Templates

Webhook Trigger:

{
  "id": "{{uuid}}",
  "name": "Webhook",
  "type": "n8n-nodes-base.webhook",
  "typeVersion": 1,
  "position": [250, 300],
  "webhookId": "{{random-id}}",
  "parameters": {
    "httpMethod": "POST",
    "path": "{{unique-path}}",
    "responseMode": "responseNode"
  }
}

HTTP Request:

{
  "id": "{{uuid}}",
  "name": "HTTP Request",
  "type": "n8n-nodes-base.httpRequest",
  "typeVersion": 4.1,
  "position": [450, 300],
  "parameters": {
    "method": "GET",
    "url": "",
    "sendBody": false
  }
}

Slack:

{
  "id": "{{uuid}}",
  "name": "Slack",
  "type": "n8n-nodes-base.slack",
  "typeVersion": 2,
  "position": [450, 300],
  "parameters": {
    "operation": "post",
    "channel": "",
    "text": ""
  }
}

Send Email:

{
  "id": "{{uuid}}",
  "name": "Send Email",
  "type": "n8n-nodes-base.emailSend",
  "typeVersion": 2,
  "position": [450, 300],
  "parameters": {
    "toEmail": "",
    "subject": "",
    "text": ""
  }
}

Schedule Trigger:

{
  "id": "{{uuid}}",
  "name": "Schedule Trigger",
  "type": "n8n-nodes-base.scheduleTrigger",
  "typeVersion": 1.1,
  "position": [250, 300],
  "parameters": {
    "rule": {
      "interval": [
        {
          "field": "hours",
          "hoursInterval": 1
        }
      ]
    }
  }
}

Code Node:

{
  "id": "{{uuid}}",
  "name": "Code",
  "type": "n8n-nodes-base.code",
  "typeVersion": 2,
  "position": [450, 300],
  "parameters": {
    "jsCode": "// Add your code here\nreturn items;"
  }
}

Step 6: Connection Rules

Format connections array:

{
  "connections": {
    "SourceNodeName": {
      "main": [
        [
          {
            "node": "TargetNodeName",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  }
}

For multiple outputs, increment the inner array index.

Scripts

Generate workflow using the helper:

python .agent/skills/generating-n8n-workflows/scripts/n8n_generator.py \
  --prompt "Send Slack message when webhook received" \
  --output workflow.json

Examples

Example 1: Simple Webhook to Slack

User Prompt: "When I send a webhook, post to Slack"

Generated Nodes: 2 (Webhook → Slack)

See: examples/webhook-slack-example.json

Example 2: Daily Email Report

User Prompt: "Send daily email at 9 AM"

Generated Nodes: 2 (Schedule → Email)

See: examples/schedule-email-example.json

Example 3: HTTP API Call

User Prompt: "Call an API every hour and save response"

Generated Nodes: 2 (Schedule → HTTP Request)

See: examples/schedule-http-example.json

Validation Checklist

Before returning JSON:

  • [ ] Only necessary nodes included
  • [ ] All nodes have unique UUIDs
  • [ ] All nodes have unique names
  • [ ] Connections reference existing node names
  • [ ] Positions are reasonable (no overlaps)
  • [ ] JSON is valid (no trailing commas)
  • [ ] No credential values hardcoded
  • [ ] Workflow name is descriptive

Resources

Skills similaires