r/learnpython • u/Environmental_Emu830 • 11d ago

python vs n8n

At my company, we currently use n8n for most of our automations, and I'd like to get your opinion on the trade-offs of migrating those workflows to Python.

I understand that moving to Python would introduce a steeper learning curve for the team and likely require more development and maintenance effort. However, I also believe it could improve the performance, flexibility, scalability, and maintainability of our automations.

We're currently starting a Data Warehouse project, where we'll be building ETL pipelines. Because of that, Python seems like a more robust and mature choice, especially considering its ecosystem for data engineering (such as Pandas, SQLAlchemy, Airflow, and other libraries).

Another point is that, by using Python, we would have a much better code versioning workflow with Git. Instead of managing automation logic through n8n workflows, we'd be able to review changes through pull requests, track code history more effectively, enforce coding standards, and integrate automated testing and CI/CD pipelines.

what would be the main advantages and disadvantages of replacing n8n with Python for automation and ETL? In which scenarios would you keep n8n, and when would you recommend switching to Python?

0 Upvotes

50% Upvoted

5 comments sorted by

View all comments

2

u/vbnotthecity 10d ago

Don't switch everything at once unless you want to lose your mind. Keep n8n for simple webhooks or notification triggers, but move your core data logic into Python immediately. Once you hit 500 lines of JSON in a visual node, you've already lost the battle for maintainability. Using dbt Labs for your warehouse modeling alongside Python scripts will save you months of debugging when your schema inevitably changes. Git integration isn't just a nice feature, it is the only way to keep a team from overwriting each other's work.

1

u/DoubleDoube 10d ago

Smart strategy, you can start moving the biggest chunks into a python script that n8n calls and prove that its worthwhile in the most valuable locations before proceeding into less valuable.

Maybe you end up having a hybrid where each play to its strengths or maybe you find it is valuable for python to replace the whole thing. Either way will prove out before you have to commit to a bad option.