4 ms·

This is so helpful, thank you. I've been evaluating n8n as a way to build things quickly for clients, but I do wonder about what happens when they want to turn

This is so helpful, thank you. I've been evaluating n8n as a way to build things quickly for clients, but I do wonder about what happens when they want to turn the automation into a full app. I wish there was a first-party way to export an n8n workflow as a plain Python script or set of scripts. Have you ever had to migrate a project from n8n to code?

hirako2000 1y ago
Yes I migrated workflows which I felt should be promoted as critical/production. Also because I wanted to scale that independently. https://applycreatures.com https://applycreatures.com started as product backed by n8n. It enabled rapid backend tweaks to focus on the frontend. Once MVP was completed, it was time to migrate. I had the code in JavaScript so the core logic could simply be moved over, but a lot of boilerplate code had to be written to create a full fledged nodejs API. It confirmed that n8n was a good decision for early, prototyping the solution. Most of my workflows remained in n8n, those that are unimportant or turned out unnecessary to the application. It saved me days for each, not having to build an app backend and cicd for those.