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

Description and use

The author used n8n for prototyping and production, but faced hidden failures and diffing issues. Moving to plain Python with cron provided clearer code, better version control, and more reliable error handling.

Problem

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

Outcome

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

Workflow

• 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

Evidence

It makes the shape of a flow visible.

Source

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

Source

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

Source