Can Lyro upload a document or run an extraction in AlgoDocs?

No. All three actions are reads - Get Current User, List document data extractors and List folders. Uploading files and running extraction jobs happens in AlgoDocs; this integration answers questions about the configuration around them.

What credential does this integration need?

An AlgoDocs API key. List folders only works once a key is in place, and Get Current User verifies which account that key resolves to before any ID it returns is acted on.

What are the extractor and folder IDs useful for?

Every AlgoDocs API call has to reference them. List document data extractors returns each extractor's identifier and name and List folders returns folder IDs with their hierarchy, so Lyro can tell you exactly which extractor or folder a job should point at.

How is this different from wiring AlgoDocs into Zapier?

A Zapier workflow fires a fixed sequence when a trigger matches. Lyro reads the current setup while a conversation is open - which extractors exist, how folders nest, which account is connected - and answers from that, or hands off to a human agent with the detail attached.

Algodocs MCP integration

Lists the extractors configured on an account with their IDs, returns the folder hierarchy, and confirms which AlgoDocs user the key belongs to.

Connect Algodocs See all integrations

3actions available

Three actions you can hand over today

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

Get current user
Lyro retrieves details of the authenticated user in AlgoDocs, confirming identity and available features. Needed for permission checks.
List document data extractors
Lyro shows all available data extraction templates in AlgoDocs, helping you pick the right parser for a document type. Essential for setup and configuration.
List folders
Lyro displays all folders in your AlgoDocs workspace, making it easy to navigate and organize documents. Useful for finding where to store new uploads.

See all 3 actions

How businesses use Algodocs + Lyro

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

Check how document extraction is set up
Lyro verifies the identity behind the API key, lists every data extractor with its ID and name, and returns the folder IDs and hierarchy documents are filed into.
Get Current UserList Document Data ExtractorsList Folders

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 Algodocs actions it has and picks the ones a request needs.

01
Connect Algodocs
Authorize the Algodocs 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 Algodocs 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

Algodocs · Lyro

Everything else about Algodocs

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

No. All three actions are reads - Get Current User, List document data extractors and List folders. Uploading files and running extraction jobs happens in AlgoDocs; this integration answers questions about the configuration around them.