Overview
n8n workflows are deployed via the REST API athttps://hab.so1.io/api/v1/workflows/{id}. Workflow JSON files are untracked in git by preference.
API Details
| Field | Value |
|---|---|
| Base URL | https://hab.so1.io |
| Auth header | X-N8N-API-KEY |
| TOMMY workflow ID | MasflGBKdowUZwpJ |
| FORGE workflow ID | mSJmBzpIcuCKz1WT |
Deployment Protocol
Step 1: Build Clean Payload
The n8n PUT API accepts only:name, nodes, connections, settings
Step 2: Strip Duplicate Nodes (FORGE only)
FORGE JSON may contain duplicate nodes with1 suffix. Remove them:
Step 3: Push via PUT
Step 4: Verify
node_count matches (TOMMY: 34, FORGE: 43), active: true.
Step 5: Re-bind Credentials (MANDATORY)
The n8n PUT API detaches credential bindings even though IDs are preserved. After pushing:- Open workflow in n8n UI at
hab.so1.io - Open each node that uses credentials
- Re-select the credential from the dropdown
- Save the workflow
Quick Reference Commands
Push TOMMY
Trigger TOMMY (dry run)
Trigger FORGE (manual mode)
Timeout Chain
| Layer | Timeout | Configurable? |
|---|---|---|
| Vercel proxy | 300s (maxDuration) | Yes, via export |
| BFF n8n adapter | timeoutMs, default 120s | Yes, per-request |
| n8n node-level | Per HTTP Request node | Yes, in workflow JSON |
| FORGE → TOMMY | 600s | Yes, in node config |