Reads the workspace document list with each document's signing type, status, and timestamps, so signature chasing is answered on the spot.
1actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro retrieves all documents stored in a BoloForms workspace, showing status, metadata, and content. Essential for finding and auditing submitted forms.
Each card is one request a support team gets, and the Boloforms actions Ayro runs to close it.
Ayro reads the BoloForms document list and answers from the status it finds there, instead of anyone emailing to ask.
The list carries each document's timestamps, so Ayro can answer when something was sent and how long it has sat unsigned.
When a request names a document loosely, Ayro pulls the workspace list and matches it to the real entry before answering.
Because the list covers the whole workspace, Ayro can summarise which documents are still unsigned rather than checking them one by one.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Boloforms actions it has and picks the ones a request needs.
Authorize the Boloforms 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 Boloforms 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 freeBoloforms · Ayro
What can you do in Boloforms 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 Boloforms.
One thing, and it does it live: it retrieves the document list for a connected workspace, with each document's name, signing type, status, and timestamps. That is enough to answer status and waiting-time questions without opening BoloForms.
All 1 actions your agent can call on Boloforms, straight from the live MCP connection.
Retrieves a list of documents from a BoloForms workspace.
Same connection, same setup. Pick the next one your team already uses.
Lists the extractors configured on an account with their IDs, returns the folder hierarchy, and confirms which AlgoDocs user the key belongs to.
Imports files from a URL, converts PDFs to DOCX or images, runs long jobs asynchronously, and confirms a format pair is supported.
Confirms the connected account, lists existing workspace folders, and creates the folder a set of generated documents should land in.
Configures extraction and classification jobs, retrieves batch results with their processing status, and clears jobs and credits down after.
Searches file contents for the document someone means, files attachments into the right folder, issues scoped sharing links, and restores deleted items.
Runs GROQ queries and fetches documents by ID, audits project roles and service accounts, and manages custom user attributes.

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