Awesome-omni-skill n8n-builder
Expert n8n workflow builder that creates, deploys, and manages n8n workflows programmatically via the n8n REST API. Use when asked to create n8n workflows, automate n8n tasks, build automations, design workflow pipelines, connect services via n8n, or manage existing n8n workflows. Handles webhook flows, scheduled tasks, AI agents, database syncs, conditional logic, error handling, and any n8n node configuration.
git clone https://github.com/diegosouzapw/awesome-omni-skill
T=$(mktemp -d) && git clone --depth=1 https://github.com/diegosouzapw/awesome-omni-skill "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/development/n8n-builder" ~/.claude/skills/diegosouzapw-awesome-omni-skill-n8n-builder && rm -rf "$T"
skills/development/n8n-builder/SKILL.mdn8n Workflow Builder
Setup
Requires two environment variables:
— n8n instance URL (e.g.N8N_URL
)https://your-n8n.example.com
— n8n API key (Settings → API → Create API Key)N8N_API_KEY
Workflow
-
Understand the automation — Clarify trigger (webhook/schedule/manual), data sources, processing logic, outputs, and error handling needs.
-
Design the workflow JSON — Build valid n8n workflow JSON following the schema in
. Use patterns fromreferences/workflow-schema.md
as templates.references/workflow-patterns.md -
Deploy via API — Use
or pipe JSON toscripts/n8n-api.sh create <file>
.scripts/n8n-api.sh create-stdin -
Activate — Use
for trigger-based workflows.scripts/n8n-api.sh activate <workflow_id> -
Verify — List workflows to confirm deployment:
.scripts/n8n-api.sh list
API Script Reference
# List all workflows scripts/n8n-api.sh list # Create workflow from JSON file scripts/n8n-api.sh create /tmp/workflow.json # Create from stdin echo '{"name":"Test",...}' | scripts/n8n-api.sh create-stdin # Get, activate, deactivate, delete, execute scripts/n8n-api.sh get <id> scripts/n8n-api.sh activate <id> scripts/n8n-api.sh deactivate <id> scripts/n8n-api.sh delete <id> scripts/n8n-api.sh execute <id> # List credentials and tags scripts/n8n-api.sh credentials scripts/n8n-api.sh tags
Building Workflow JSON
Every workflow needs:
name, nodes[], connections{}, settings{}.
Every node needs:
id, name, type, typeVersion, position, parameters.
Connections use source node display name as key, mapping outputs to target nodes.
For full schema, node types, and expression syntax → read
references/workflow-schema.md
For complete workflow examples (webhook, schedule, AI agent, DB sync, error handling) → read references/workflow-patterns.md
Key Rules
- Always set
in settings"executionOrder": "v1" - Node names must be unique within a workflow
- Node IDs must be unique — use descriptive slugs like
,webhook1code1 - Position nodes starting at
, spacing ~200px horizontally[250, 300] - IF nodes have two outputs: index 0 = true, index 1 = false
- Webhook workflows need
node ifrespondToWebhook
isresponseModeresponseNode - Credentials must exist in n8n before activation — check with
scripts/n8n-api.sh credentials - Test before activating — use
for manual trigger workflowsscripts/n8n-api.sh execute <id> - Use
on risky HTTP/API nodes, then check for errors downstreamcontinueOnFail: true
Common Real Estate Workflows
- Lead intake: Webhook → validate → dedupe → insert DB → notify Slack/SMS
- Call follow-up: Schedule → query DB for completed calls → send SMS/email based on outcome
- Drip campaign: Schedule → query leads by stage → send stage-appropriate email/SMS
- CRM sync: Webhook → transform → update HubSpot/Salesforce + internal DB
- Property alerts: Schedule → scrape/API listings → filter new → notify leads
- AI qualification: Webhook → AI Agent (classify lead intent) → route to appropriate pipeline