n8n2py.me

n8n2py.me - Own Your Automations - Convert n8n Workflows into Python APIs in Seconds

Comment

🌟 Inspiration

Every time I came across posts about "100-step" workflows on n8n, Zapier, or Make.com automating entire businesses, I noticed one big red flag — nobody talks about where the data goes.

As someone who cares about ownership, privacy, and control, I knew I wanted to solve this. That's what led to n8n2py.me – a tool that helps you convert your no-code n8n workflows into fully self-hostable Python FastAPI services, so you’re not locked into third-party platforms.

⚙️ What it does

n8n2py.me is a web app that allows users to:

  • * Upload exported n8n workflows (in JSON format)

  • * Instantly convert them into clean, readable Python FastAPI code

  • * Self-host their automations on Render, Replit, Docker, or their own servers

  • * Retain full control over their business logic, API endpoints, and logs

It's perfect for professionals and teams dealing with sensitive data – like law firms, clinics, or enterprise backends – who want the power of automation without sacrificing privacy.

🛠️ How I built it

As a solo builder, I built everything from scratch:

  • * Frontend: Developed using React with Vite for fast performance and Tailwind CSS + shadcn/ui for styling and consistent components.

  • * Authentication & Database: Integrated Supabase for user authentication and PostgreSQL-based backend storage.

  • * Code Generation Engine: I wrote a custom parser in TypeScript that reads n8n JSON and converts supported nodes like HTTP, If, Delay, Set, etc., into Python code using FastAPI conventions.

  • * Hosting: The frontend is hosted on Vercel, and the generated code is structured to work out-of-the-box on platforms like Replit, Render, or Fly.io.

  • * Development Tool: I built and shipped the entire platform on Bolt.new, which made it incredibly fast to iterate, test, and deploy.

From UI design to logic architecture to auth and deployment, I handled every step myself in under a week.

🧱 Challenges I ran into

  • * Figuring out how to accurately map n8n’s node structure (especially conditional flows and variable scopes) into clean Python logic

  • * Designing code output that’s not just functional but readable and customizable

  • * Staying within token limits on Bolt.new while still supporting dynamic workflows

  • * Balancing speed of development with code quality, since I was building solo

🏆 Accomplishments that I'm proud of

  • * Successfully built and launched a working product in under 7 days

  • * Converted real n8n workflows into Python microservices with no manual rewriting

  • * Got interest from law firms and private clinics who want to self-host sensitive automations

  • * Registered and launched on a custom domain: https://n8n2py.me

  • * Maintained clean design, functional UX, and technical depth as a solo maker

📚 What I learned

  • * How to reverse-engineer and parse a no-code platform’s export format

  • * How to integrate Supabase for secure, scalable authentication and data storage

  • * The importance of writing clean, extendable code for future developers (not just myself)

  • * How to deliver a full-stack SaaS-like experience using Bolt.new quickly and efficiently

🚀 What's next for n8n2py.me

  • * ✅ Add support for more node types: Google Sheets, Notion, Slack, Discord, Webhooks

  • * 📡 Host and expose the generated APIs with custom subdomains (Pro plan)

  • * 🧠 Introduce AI-based suggestions to auto-fix broken workflows or improve logic

  • * ⚙️ Auto-generate requirements.txt, Dockerfile, and GitHub deployable bundles

  • * 🔍 Add a visual execution map with error handling and retry logic

  • * 👥 Enable team features, role-based permissions, and shared workflows
  • can paste directly from Word or other rich text sources.

Built With

Share this project:

Updates