n8n was my training wheels: it taught me the flows, then I shipped leaner without it

说明与用途

作者使用n8n进行原型设计和生产，但遇到隐藏错误和差异跟踪问题。迁移到使用cron的纯Python提供了更清晰的代码、更好的版本控制和更可靠的错误处理。

问题

Relying on n8n for production automation led to hidden failures, lack of diffs, and obscured logic, making maintenance difficult.

结果

Switching from n8n to lean Python scripts reduced maintenance overhead, exposed failures, and improved code readability and version control.

工作流

• Prototype flow in n8n to visualize trigger‑fetch‑transform‑branch‑act pattern
• Export or manually translate the flow into a Python script
• Implement fetch, transform, and act logic using standard libraries
• Add error handling to let exceptions surface
• Store script in git for version control
• Schedule script with cron or a scheduler
• Monitor execution and review logs for failures

证据

It makes the shape of a flow visible.

来源

The flows were right. The theory I'd learned on the canvas was sound.

来源

It fails loudly by default. An error is an exception, an exception is a non‑zero exit.

来源