Sponsor Suno AI Music arrow_forward
Slash Command

N8n Builder

Generate complete n8n workflow JSON files

Type
Slash Command
GitHub stars
2.8k
License
MIT
Repo last updated
Sep 27, 2026

What N8n Builder is

N8n Builder is a slash command published in the jeremylongshore/tons-of-skills-marketplace repository on GitHub, which has about 2.8k stars. The repository describes itself as: “Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com.”

A slash command is a reusable prompt saved as a markdown file and run by typing its name after a slash. In Claude Code, custom commands have been merged into skills: a file in .claude/commands/ and a skill folder in .claude/skills/ both create the same kind of command, and existing command files keep working.

N8n Builder gives you a repeatable way to run the same instructions without retyping them, optionally with arguments.

How to install N8n Builder

Claude Code

  1. Download n8n-builder.md from the repository.
  2. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md.
  3. Run it by typing / followed by its name.

Claude Cowork

  1. Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it.
  2. In Customize → Skills, click +, then upload the ZIP.
  3. Run it from any task with / and the skill name.

New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.

Inside the source file

An excerpt from plugins/ai-agency/n8n-workflow-designer/commands/n8n-builder.md, shared under the repository's MIT license. Read the full file on GitHub.

Generate production-ready n8n workflow JSON files.

Usage

When the user requests an n8n workflow, analyze their requirements and create a complete, importable workflow JSON file.

Workflow Templates

1. AI Email Responder

{
  "name": "AI Email Auto-Responder",
  "nodes": [
    {
      "parameters": {
        "pollTimes": {
          "item": [
            {
              "mode": "everyMinute"
            }
          ]
        },
        "simple": true,
        "filters": {
          "labelIds": ["INBOX"]
        }
      },
      "id": "1",
…

2. Data Processing Pipeline

{
  "name": "CSV to Database with AI Enhancement",
  "nodes": [
    {
      "parameters": {
        "fileFormat": "csv",
        "options": {}
      },
      "id": "1",
      "name": "Read CSV",
      "type": "n8n-nodes-base.spreadsheetFile",
      "typeVersion": 2,
      "position": [250, 300]
    },
    {
      "parameters": {
        "batchSize": 10,
        "options": {}
…

3. Content Pipeline

{
  "name": "RSS to Social Media with AI",
  "nodes": [
    {
      "parameters": {
        "url": "https://example.com/feed.xml",
        "options": {}
      },
      "id": "1",
      "name": "RSS Feed",
      "type": "n8n-nodes-base.rssFeedRead",
      "typeVersion": 1,
      "position": [250, 300]
    },
    {
      "parameters": {
        "conditions": {
          "dateTime": [
…

4. Lead Qualification

{
  "name": "Lead Scoring and Routing",
  "nodes": [
    {
      "parameters": {
        "path": "lead-webhook",
        "options": {}
      },
      "id": "1",
      "name": "Webhook",
      "type": "n8n-nodes-base.webhook",
      "typeVersion": 2,
      "position": [250, 300]
    },
    {
      "parameters": {
        "model": "gpt-4",
        "messages": {
…

Features

  • Complex branching logic
  • Loops and iterations
  • Error handling and retries
  • Custom code nodes
  • 200+ integrations
  • Self-hostable
  • AI model integration
  • Database operations
  • API calls and webhooks

Best Practices

  1. Always add error handling - Use error workflows or try-catch nodes
  2. Test with small datasets first - Validate before processing large volumes
  3. Use environment variables for secrets - Never hardcode API keys
  4. Implement logging for debugging - Add notes or database logging
  5. Version control your workflows - Export and commit to git
  6. Monitor resource usage - Watch execution times and API costs
  7. Use descriptive node names - Make workflows self-documenting
  8. Implement rate limiting - Respect API limits with Wait nodes
  9. Batch processing for scale - Use Split in Batches for large datasets
  10. Regular backups - Export workflows regularly

Output Format

When generating a workflow, provide:

  1. Workflow Name - Clear, descriptive name
  2. Architecture Diagram - Visual flow of nodes
  3. Complete JSON - Importable workflow file
  4. Setup Instructions - Credentials, settings needed
  5. Testing Steps - How to validate the workflow
  6. Deployment Notes - Self-hosted vs cloud considerations
  7. Cost Estimation - Expected API and resource costs

Example Response

# Workflow: AI Customer Support Automation

## Architecture

Ticket Created → Classify (AI) → Route by Priority → Draft Response (AI) → Human Review → Send


## Nodes
1. Webhook trigger for new tickets
2. OpenAI classification
3. IF node for routing
4. OpenAI response generation
5. Slack notification for review
6. Email send on approval

## Setup
1. Create webhook in your ticketing system
2. Add OpenAI API credentials
3. Configure Slack webhook
4. Set up email credentials
5. Test with sample ticket

## JSON
[Complete importable JSON here]
…

This workflow builder helps users create production-ready n8n automations with AI integration, error handling, and best practices built in.

Before you install

  • Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
  • Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
  • Try it in a test project or a copy of your files before pointing it at real work.
  • Pin the version you tested, and review changes before updating.
  • Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.

FAQ

What is N8n Builder?

N8n Builder is a slash command for Claude Code and Claude Cowork from the jeremylongshore/tons-of-skills-marketplace repository on GitHub. Generate complete n8n workflow JSON files

How do I install N8n Builder in Claude Code?

Download n8n-builder.md from the repository. Save it to ~/.claude/commands/ (all projects) or .claude/commands/ (one project). As a skill, you can instead save it as ~/.claude/skills/<name>/SKILL.md. Run it by typing / followed by its name.

Can I use N8n Builder in Claude Cowork?

Turn the command into a skill: create a folder with the file saved as SKILL.md and zip it. In Customize → Skills, click +, then upload the ZIP. Run it from any task with / and the skill name.

Is N8n Builder safe to install?

It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.

Similar resources

Browse all skills, subagents, and plugins →

Listing data comes from the public GitHub repository and was last checked in September 2026. Excerpts are © their authors and shared under MIT. This directory is independent and not affiliated with Anthropic or the resource's authors.