Productivity & Project Management

Connect Project Bubble to Your AI Agents

This integration gives WKIL agents read access to a Bubble.io app's Data API — inspecting a data type's field schema, listing its objects, and retrieving a specific record by ID, using a Bubble API key.

Authentication: API key

Build with Project Bubble

What you can do

Inspect a Bubble app's data schema — field names, types, and required status for a data type.
List objects for a data type and retrieve a single record by its ID.

Available capabilities may vary by authentication and workspace configuration.

Actions supported by the connector

Data API Get Data Type Fields

Retrieves the field schema for a specific Bubble data type, returning metadata about each field including its name, data type, and whether it's required.

Data API Get Objects

Tool to retrieve a list of objects for a specified data type.

Get Record By ID

Retrieves a single record by its unique ID from a specified data type (table/collection).

Practical agent use cases

A WKIL agent can look up a Bubble app's data type schema before mapping its fields into another system.
A support workflow can fetch a specific record by ID from a Bubble app's database to answer a customer question.

How it works with WKIL

1
Choose the integration
Add Project Bubble to your agent from inside the WKIL platform.
2
Grant the permissions it needs
Define precisely what the agent can access and perform.
3
Test, then run it
Test actions before they go live, with human approval where needed.

Permissions always stay in your control — you can scope access and require human approval before any sensitive action.

Related integrations

FAQ

What does the Project Bubble integration support?

The WKIL integration exposes 3 verified read-only actions against a Bubble.io app's Data API: retrieving a data type's field schema, listing objects for a data type, and getting a single record by ID.

Does WKIL need access to a Project Bubble account?

Yes. The integration requires a Bubble API key and should be scoped to the permissions your workflow needs.