I’m not against that idea and I read your post- but I think it would slow down the build process. Bubble has many “gotchas” on the API connector and there’s less visibility on what’s actually going on.
n8n lays everything out beautifully - and they have easy access to tools i need (ocr image reader, pdf, google sheets, drive, etc) .
Speed is my priority at this MVP stage. Then I would consider switching to bubble for more control over debugging etc.
Hey Brad,
You’re spot on about n8n being faster for MVP development. I’ve built agent workflows both ways and the debugging visibility in n8n is a huge time saver. Those “gotchas” in Bubble’s API Connector have burned me too many times.
@georgecollier makes a fair point about keeping everything in one place, but for complex agentic stuff with OCR, PDFs, and multiple tool calls for example, n8n just flows better. Keep in mind that’s my opinion, given my experIence in development. I recognize that everything is a bit subjective depending on the tools that you are more comfortable with.
I actually use both approaches depending on the project - simpler API calls stay in Bubble, but anything with multiple steps or complex logic goes to n8n. Best of both worlds.
I would love to help accelerate n8n development for your Bubble app. I have experience creating API calls between Bubble and n8n, as well as building complex agentic workflows in n8n to automate processes efficiently. I’m ready to start immediately and can ensure seamless integration with your B2B app.