N8n's MCP server - are you using it to create workflows?

Overall, workflow generation has been quite impressive. For straightforward automations, it gets very close to what I’d build manually.

However, for more complex flows (branching logic, error handling, or multi-step integrations), I still end up tweaking quite a bit after generation.

A few things I noticed:

  • Node configurations are usually correct, but edge cases (like pagination or retries) are often missing
  • Credentials handling sometimes needs manual correction
  • Complex IF / Switch logic can become slightly messy in generated workflows
  • Still, it saves a lot of initial setup time, which is a big win

Tips & Tricks

What worked better for me:

  • Being very explicit about input/output structure for each step
  • Breaking down requests into smaller workflows instead of one big prompt
  • Mentioning error handling requirements upfront (like retries, fallback paths) improves results a lot
  • Asking for “production-ready workflow with logging + error handling” gives noticeably better output

Skills Suggestions

Would love to see:

  • Built-in error handling templates (retry patterns, dead-letter flows, etc.)
  • Better testing / dry-run mode for generated workflows
  • Automatic workflow documentation generation (very useful for teams)
  • Stronger support for complex branching logic + state management

Also, a “validation step” before creation (like checking for missing credentials or invalid node configs) would be super helpful.

2 Likes