Bubble DB Read Tool
The Bubble Database Read Tool lets your agent look things up in your app's database when it answers—so it can respond with real, live data instead of generic replies.
Read-only by design
The Bubble Database Read Tool has read-only access to your database. It can look up and read data to answer questions, but it cannot and will never update or delete anything in your Bubble database.
All of the fields below live in the Bubble Database Read Tool section of Agent Studio.
Step 1 — Enable the Data API in Bubble
Before your agent can read anything, you need to turn on the Data API in your Bubble app.
- In the Bubble editor, open Settings → API.
- Under the Public API Endpoints heading, tick Enable Data API.
- A list of your app's data types appears. Check the box next to each data type you want the agent to be able to read.
Only turn on the data types your agent actually needs. Anything you tick here becomes readable through the API, so leave sensitive types unchecked unless there's a clear reason to include them.
Step 2 — Generate an Admin API Token
Your agent authenticates to Bubble with an API token.
- Still under Settings → API, find the API Tokens section.
- Click Generate a new API token.
- Copy the token immediately and keep it somewhere safe.
This is an Admin token, so it can read every data type you turned on in Step 1. Treat it like a password.
Step 3 — Find Your Data API URL
Your Data API URL is the root address Pluto sends read requests to. It follows this shape:
Data API URL
Swap your-app for your app's name (or use your custom domain if you've set one). You can
confirm the exact root under Settings → API, next to the Data API settings.
Step 4 — Connect It in Agent Studio
Back in Agent Studio, open the Data Source section and fill in:
- Data API URL — the URL from Step 3.
- Data API Token — the Admin token from Step 2. Once saved, it's stored securely and shown
as
•••• Stored; use Replace if you ever need to rotate it.
Step 5 — Define Your Schema
The Schema section tells the agent which tables and columns it's allowed to query, and what each one means. For every table you want the agent to use:
- Add a Table name and a Table description ("what this table represents").
- Add each column with its name, type, and a short description.
These descriptions are how the agent understands your data, so make them meaningful—see Tips for Building for how to write them well.
Development vs. Production: Watch the version-test URL
Bubble runs two copies of your app—a development version and your live version—and the Data API URL is how you choose which database a read hits.
The development version's URL contains version-test in the path:
Development (version-test)
Removing version-test points the same URL at your live database:
Production (live)
Use the version-test URL for Test, and remove it for Live.
When version-test is removed, every read hits your live database with real customer
data. The tool gives you a separate Data Source for each environment for exactly this
reason: the version-test URL belongs in Data Source — Test, and the live URL in
Data Source — Live.