Can Lyro create or update records in Project Bubble?

No. All three connected actions - Data API Get Data Type Fields, Data API Get Objects, and Get Record By ID - are reads, so Lyro can look data up and report it accurately but cannot change anything. Edits stay with your team in Project Bubble.

What happens if a record is outside the connected account's permissions?

Get Record By ID returns an error when the record does not exist or the connection is not permitted to read it, so Lyro says it cannot access that record rather than filling the gap with a guess. What it can reach follows the API credentials you connect.

How does Lyro find a record when nobody knows its ID?

It starts with Data API Get Objects, applying filters and sorting to the relevant data type to shortlist candidates, then uses the ID from that result with Get Record By ID to pull the full record.

How is this different from a Zapier lookup step?

A Zapier lookup runs one predefined query on a trigger. Lyro inspects the data type's schema first, chooses which filters make sense for what was actually asked, and can run several lookups in one exchange before answering.

Project bubble MCP integration

Reads field schemas, lists filtered records, and pulls a single record by ID so project questions get answered from live data.

Connect Project bubble See all integrations

3actions available

What your agent can do with Project bubble

Every action runs live through MCP. Nothing to build, nothing to maintain.

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

See all 3 actions

How businesses use Project bubble + Lyro

Each card is one request a support team gets, and the Project bubble actions Lyro runs to close it.

Answer a status question from the live record
Lyro fetches the project or task by its ID and reads back the current field values along with the created and modified dates, so nobody has to open the board to check where something stands.
Get Record By IDData API Get Objects
Narrow a vague request down to one record
Lyro lists the objects for a data type with filters, sorting, and pagination applied, then opens the match by ID, turning a half-remembered project name into the actual record.
Data API Get ObjectsGet Record By ID
Check what a data type stores before querying it
Lyro reads the field schema for a data type - field names, types, and which ones are required - so a lookup asks for fields that exist rather than guessing at the structure.
Data API Get Data Type FieldsData API Get Objects
Hand an agent the record, not the question
When a request needs a human, Lyro passes on the matching record and its fields with the conversation history, so the agent picks up from the data instead of running the same search again.
Get Record By IDData API Get Objects

How it works

Get started in 3 steps

Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Project bubble actions it has and picks the ones a request needs.

01
Connect Project bubble
Authorize the Project bubble account your team already uses — one consent screen, no API keys, no mapping tables. Lyro can only do what you granted that account, and you can disconnect it at any time.
02
Tell your agent what you need
Describe the job the way you would hand it to a teammate. Lyro maps it to the Project bubble actions that close it and chains as many as the request needs.
03
Watch it work
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started free

Project bubble · Lyro

Everything else about Project bubble

Setup, permissions, and the limits of what Lyro can do inside Project bubble.

No. All three connected actions - Data API Get Data Type Fields, Data API Get Objects, and Get Record By ID - are reads, so Lyro can look data up and report it accurately but cannot change anything. Edits stay with your team in Project Bubble.

Every action available in Project bubble

All 3 actions your agent can call on Project bubble, straight from the live MCP connection.

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
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).