What does Lyro see for each PDF-API.io template?

The template's metadata: its name, the fields it requires, and the variants it offers - enough to identify the right one and know what information to collect before generating a document.

Can Lyro generate the PDF itself?

Not from this connection - it lists the templates and their required fields so the right one is chosen. Document generation happens through PDF-API.io itself.

What happens if a template needs a field the customer hasn't provided?

Because Lyro checks each template's required fields upfront, it can ask for anything missing in the conversation instead of the document generation failing later.

Does listing templates work the same for every PDF-API.io account?

Lyro lists whatever templates exist on the connected account - the results reflect that account's own designer, not a shared or default template set.

Pdf api io MCP integration

Lists PDF-API.io templates with their required fields and variants, right inside the conversation.

Connect Pdf api io See all integrations

1actions available

What your agent can do with Pdf api io

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

List templates
Lyro retrieves all PDF-API.io templates available in the account. Support selects the right template for customer document generation requests.

See all 1 actions

How businesses use Pdf api io + Lyro

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

Pick the right template for a request
When a customer needs a specific document, Lyro lists the templates on the PDF-API.io account and matches one by name and type before anything gets generated.
List TemplatesCheck Required Fields
Confirm what information a document needs
Before a document is generated, Lyro checks the required fields for that template so the conversation collects exactly what's needed, nothing more.
List TemplatesCheck Required Fields
Explain the difference between template variants
When a template has more than one variant, Lyro can list what's available so a customer picks the right version instead of guessing.
List TemplatesCheck Required Fields
Answer a document question without a support ticket
Instead of routing a template question to a person, Lyro checks the PDF-API.io account's template list directly and answers from there.
List TemplatesCheck Required Fields

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

01
Connect Pdf api io
Authorize the Pdf api io 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 Pdf api io 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

Pdf api io · Lyro

Everything else about Pdf api io

Setup, permissions, and the limits of what Lyro can do inside Pdf api io.

The template's metadata: its name, the fields it requires, and the variants it offers - enough to identify the right one and know what information to collect before generating a document.