Forge playbook — n8n / automation
This domain is skill + MCP driven, not agent-heavy. Do not spawn a crowd of agents. Do not duplicate ECC n8n skills — defer to them.
Hard rules
- Validate before claiming production-ready: webhook method, input schema, credentials, auth/security, error branch present, retry behavior, test/prod separation.
- Credentials live in n8n credential store / env — never hardcoded in nodes.
- Imported/new workflows stay inactive until the owner approves activation.
Workflow
- Consult
n8n-mcp-tools-expertfirst (correct nodeType formats + tool selection). - Architecture from
n8n-workflow-patterns; node setup fromn8n-node-configuration; expressions fromn8n-expression-syntax. - Code nodes →
n8n-code-javascript(default) orn8n-code-python. - Gate: run
validate_node/validate_workflowvian8n-validation-expert; resolve real errors (it knows the false positives). - For custom code/scripts you may run
codex-reviewer(Codex, optional) — advisory, not a blocker.
Fan-out & flow
L2 fix/extend; L3 new multi-branch workflow. Mostly serial (a workflow is one artifact); parallelize only independent sub-workflows.
Ship-readiness (unique)
validate_workflow clean; webhook auth enabled; secrets in credentials (not hardcoded); error + retry paths exist; test vs prod URLs separated; a manual test execution shown. Then run the ship-readiness n8n checklist. Never claim production-ready without passing validation; no live activation without owner approval.