On this page
01What it becomes
Typed server-side functions in src/server/api-connector.ts. Every call you configured in the API Connector becomes a server-side function. Calls used as data become data reads; calls used as actions become workflow steps. Private keys, headers and parameters move to environment variables, so they never reach the browser.
No extra npm package: the generated code uses React, Next.js and browser APIs only.
02What converts
- Calls used as Data (“Get data from an external API”) and as Action (workflow steps)
- Parameters, headers and bodies, with dynamic values from your app
- Results of a call, used in later steps or on the page
- Requests are pinned to the call’s own host
03What you set up
- Copy the private keys and headers listed in .env.example into your hosting’s environment variables.
04About this plugin
API Connector is made by Bubble itself (API wrapper / data source + actions). See its page in the Bubble manual.
Questions
- Does the API Connector plugin work outside Bubble?
- Not as it is: Bubble plugins only run inside Bubble. In a Next.js app it is replaced by generated code — Typed server-side functions in src/server/api-connector.ts.
- Will my API Connector settings carry over?
- Yes. deBub reads the plugin’s settings, conditions and workflows from your .bubble export and converts all of the plugin’s parts. Secret keys are the exception: you add them as environment variables.