Bubble has started moving away from the old plugin-based API Connector, and the new editor-based version makes that direction very clear.
If you rely on APIs in Bubble—especially for AI, payments, or third-party services—this is not just a UI refresh. It changes how API configuration fits into the overall Bubble building experience.
In this article, I’ll explain what the new API Connector is, what actually changed, what stayed the same, and why it’s worth switching now. I’ll also reference a practical demo using OpenAI’s Text-to-Speech API.
The Problem with the Old Plugin-Based API Connector
The plugin-based API Connector worked, but it always felt slightly detached from the rest of the editor. You had to jump into the plugin tab, configure endpoints in isolation, then mentally map them back to your workflows.
As Bubble apps grew more complex, this separation became friction:
- API logic lived outside the main editor flow
- Managing large or multiple APIs became harder to reason about
- It didn’t feel like a core part of how Bubble wanted you to build long-term
Bubble’s new approach fixes that.
What the New Editor-Based API Connector Changes
The biggest improvement is where the API Connector lives.
It’s now part of the Bubble editor itself, which means API setup feels like a native step in building your app, not an add-on.
Key improvements include:
- A cleaner, more structured interface for endpoints, headers, and parameters
- Better visibility into how APIs fit into workflows
- Less context switching when building or debugging
- A setup that scales better as your app grows
It feels designed for serious apps, not just quick integrations.
What Stayed the Same
This is not a complete mental reset.
Most of the fundamentals still apply:
- You still define endpoints with URLs, headers, and parameters
- Authentication works largely the same way
- Calls still need to be initialized
- Responses are still reusable across workflows
If you’ve used the old API Connector before, you won’t feel lost.
Migrating from the Old Plugin
There’s currently no automatic migration from the plugin-based connector to the new editor-based one.
Migration is manual, but manageable:
- Recreate existing endpoints in the new connector
- Copy authentication, headers, and parameters
- Initialize the calls
- Update workflows to point to the new API actions
For most apps, this is more of a careful copy-and-verify process than a full rewrite.
Example: OpenAI Text-to-Speech with the New API Connector
To show how the new connector works in practice, I demonstrated calling an OpenAI Text-to-Speech endpoint directly from Bubble.
This example highlights a few important things:
- AI APIs fit very naturally into the new connector
- Configuration is clearer and easier to follow
- The setup works cleanly with Bubble workflows
If you’re building AI-powered features in Bubble, the new connector makes these integrations feel much more first-class.
Why You Should Switch Now
The old plugin still works, but it’s clearly no longer the focus.
The editor-based API Connector is:
- More integrated
- Easier to maintain
- Better aligned with modern Bubble apps
Switching early helps future-proof your projects and reduces technical debt later.
Watch the Full Walkthrough
I cover the full migration process, UI walkthrough, and OpenAI Text-to-Speech demo in this video:
If you build serious applications in Bubble and rely on APIs, this update is worth your attention.
Top comments (1)
Some comments may only be visible to logged-in visitors. Sign in to view all comments.