Brandedflow n8n-workflow-designer

Design n8n automation workflows. Map triggers, nodes, conditions, and outputs. Produces workflow blueprints and node configs. Use when designing or debugging n8n automations.

install
source · Clone the upstream repo
git clone https://github.com/JenCW/brandedflow
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/JenCW/brandedflow "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.cursor/skills/n8n-workflow-designer" ~/.claude/skills/jencw-brandedflow-n8n-workflow-designer-bb56a2 && rm -rf "$T"
manifest: .cursor/skills/n8n-workflow-designer/SKILL.md
source content

n8n Workflow Designer

When to Use

  • Designing a new n8n automation from scratch
  • Debugging a broken workflow
  • Optimizing an existing flow
  • Planning webhook → action → notification chains

BrandedFlow n8n Context

  • n8n instance:
    https://n8n-automation-r6iy.onrender.com
  • Airtable master base:
    appYXzdeB0MUlwqFN
  • MCP server:
    https://brandedflow.onrender.com
  • Database: Neon PostgreSQL (n8n internals + BF-Signal)

Design Process

  1. Define trigger — Webhook? Schedule? Airtable record? Form submission?
  2. Map the happy path — Step-by-step node sequence for the primary success case.
  3. Add conditions — IF nodes for branching logic (qualify, route, filter).
  4. Add error handling — Error trigger node + notification for failures.
  5. Document — Name each node clearly. Add sticky notes for context.

Common Node Patterns

Webhook → Set (normalize data) → HTTP Request (MCP) → Airtable → SMS/Email

Schedule → Airtable (read) → IF (filter) → HTTP Request → Slack/Email

Form → Webhook → Code (transform) → Airtable (upsert) → n8n Qualification → SMS

Lead Qualification Flow (existing)

POST /lead → MCP server → dual-write Airtable (master + client base)
→ n8n webhook → qualify-lead-with-claude (Claude API)
→ IF hot lead → send-sms-notification (Twilio)
→ ELSE → email nurture sequence

Output Format

Produce:

  1. Node map (text diagram)
  2. Per-node config (type, params, credentials needed)
  3. Test cases (happy path + edge cases)

End of Task

State: "END-OF-TASK: Directive [updated/N/A]. Self-annealing [applied/N/A]."