Reads field schemas, lists filtered records, and pulls a single record by ID so project questions get answered from live data.
3actions available
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).
Each card is one request a support team gets, and the Project bubble actions Ayro runs to close it.
Ayro 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.
Ayro 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.
Ayro 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.
When a request needs a human, Ayro 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.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Project bubble actions it has and picks the ones a request needs.
Authorize the Project bubble account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Project bubble actions that close it and chains as many as the request needs.
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 freeProject bubble · Ayro
What can you do in Project bubble without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro 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 Ayro can look data up and report it accurately but cannot change anything. Edits stay with your team in Project Bubble.
All 3 actions your agent can call on Project bubble, straight from the live MCP connection.
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.
Retrieve a list of objects for a specified data type.
Retrieves a single record by its unique ID from a specified data type (table/collection).
Same connection, same setup. Pick the next one your team already uses.
Opens tasks from a live conversation, reads task and doc content back to the person asking, and keeps checklists, tags, and fields current.
Provisions Workspace accounts and group membership, manages email aliases, and suspends or removes access on request.
Finds contacts by email or user ID, creates and updates audience records, and fires the events that trigger automated Loops emails.
Finds an order, reports its scheduled window and proof of delivery, books new stops, and runs the day's route optimisation.
Creates Storms, adds ideas and the connectors between them, posts and reads Storm chat, and invites participants by email.
Creates and edits sitemap configurations, switches their cron schedules on or off, and reports scraping job status and remaining page credits.

Authorize the account and your agent has all 3 actions from the first conversation.
