n8n-workflow-builder

Files (1)

• SKILL.md

SKILL.md (first lines)

# ⚙️ N8N Workflow Builder — Visual Automation Design
*Design complete n8n workflows with node mapping, data transformations, error handling, and importable JSON.*

## Activation

When this skill activates, output:

`⚙️ N8N Workflow Builder — Designing your automation workflow...`

| Context | Status |
|---------|--------|
| **User says "n8n workflow", "build a workflow", "automation"** | ACTIVE |
| **User wants to connect services with trigger → process → output** | ACTIVE |
| **User mentions n8n nodes, credentials, or workflow JSON** | ACTIVE |
| **User wants a webhook endpoint (not a full workflow)** | DORMANT — see webhook-designer |
| **User wants a cron job (not n8n scheduled)** | DORMANT — see cron-scheduler |
| **User wants an API-to-API integration (not visual workflow)** | DORMANT — see api-integration |

## Protocol

### Step 1: Gather Inputs

Ask the user for:
- **Trigger event**: What starts the workflow? (webhook, schedule, app event, manual)
- **Data source**: Where does input data come from? (API, database, email, file, form)
- **Desired output**: What should happen at the end? (send email, update database, post to Slack, create record)
- **Integrations needed**: Which services? (Google Sheets, Slack, Stripe, GitHub, Notion, Airtable, etc.)
- **Frequency**: One-time, on-demand, or recurring? If recurring, how often?

### Step 2: Design Workflow Nodes

Map the workflow as a node chain:

```
┌──────────────┐    ┌──────────────┐    ┌──────────────┐    ┌──────────────┐
│   TRIGGER    │───→│   PROCESS    │───→│  TRANSFORM   │───→│    OUTPUT    │
│              │    │              │    │              │    │              │
│ [node type]  │    │ [node type]  │    │ [node type]  │    │ [node type]  │
└──────────────┘    └──────────────┘    └──────────────┘    └──────────────┘
```

For each node, specify:

| Node | Type | Purpose | Config |
|------|------|---------|--------|
| 1. Trigger | [Webhook/Schedule/App Trigger] | [what starts it] | [settings] |
| 2. Fetch | [HTTP Request/App Node] | [get data] | [endpoint, auth] |
| 3. Process | [Code/Set/IF/Switch] | [transform/filter] | [logic] |
| 4. Output | [App Node/HTTP Request] | [deliver result] | [settings] |

Include branching where needed:
- **IF nodes**: For conditional paths (e.g., if status === 'paid', send receipt; else send reminder)
- **Switch nodes**: For multi-path routing
- **Merge nodes**: For combining parallel branches

### Step 3: Map Data Transformations

For each connection between nodes, define the field mapping:

```
── Node 1 → Node 2 ────────────────────────
Source Field          →  Target Field          Transform
─────────────────────────────────────────────
{{ $json.email }}     →  to                    direct
{{ $json.name }}      →  subject               template: "Hello {{ $json.name }}"
{{ $json.amount }}    →  price                 Number: {{ $json.amount / 100 }}
{{ $json.created }}   →  date                  Format: {{ DateTime.fromISO($json.created).toFormat('yyyy-MM-dd') }}
```

Common transformations:
- **String**: `.toLowerCase()`, `.trim()`, template literals
- **Number**: Division (cents to dollars), rounding, formatting
- **Date**: ISO parse, format conversion, timezone handling
- **Array**: `.map()`, `.filter()`, `.reduce()` in Code node
- **Object**: Spread, pick fields, rename keys

### Step 4: Error Handling

Design failure paths for each critical node:

```
┌──────────────┐    ┌──────────────┐
│  Main Node   │──✗─│ Error Branch │
│              │    │              │
│  [action]    │    │ • Log error  │
│              │    │ • Notify     │
│              │    │ • Retry/Skip │
└──────────────┘    └──────────────┘
```

**Error handling strategy per node:**

| Node | On Failure | Retry? | Fallback |
|------|-----------|--------|----------|
| HTTP Request | Log + retry | 3x with 5s backoff | Send alert, skip item |
| Database | Log + alert | 1x | Queue for manual review |
| External API | Log + retry | 3x with exponential | Use cached data |
| Webhook delivery | Log + retry | 5x with backoff | Dead letter queue |

**Error notification node** (add to every workflow):
- Send to Slack channel, email, or webhook on any unhandled error
- Include: workflow name, node that failed, error message, input data

### Step 5: Credential Setup

For each integration, provide setup guidance:

```
── CREDENTIALS NEEDED ─────────────────────

1. [Service Name]
   Type: [API Key / OAuth2 / Basic Auth]
   Setup:
     a. Go to [URL]
     b. Create [API key / OAuth app]
     c. Copy [key/secret/token]
     d. In n8n: Settings → Credentials → Add → [Service]
     e. Paste credentials

From jtucker9/mystuff, MIT.

More from jtucker9/mystuff