Lists the available print queues, stages the file, and submits a PDF to the printer that should handle it.
3actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Lyro uploads PDFs to PrintAutopilot's queue directly from conversations. Documents reach the print system instantly without manual intervention.
Lyro lists available print queues to route jobs correctly. Support agents can verify which destinations are live before queuing documents.
Each card is one request a support team gets, and the Printautopilot actions Lyro runs to close it.
Lyro reads the queues configured on the account and matches the request to one of them, so a print job lands on a printer that exists rather than failing after the file is already uploaded.
Lyro stages the file it was handed and submits it as a base64 PDF to the chosen queue, so a label, packing slip, or signed form prints without an agent moving the file by hand.
Lyro uploads the file to the temporary staging bucket and holds it there until the right queue is settled, so nothing has to be re-attached or re-sent when the decision is made.
When someone asks for a duplicate invoice or a replacement shipping label, Lyro stages the PDF again and queues it to the printer that handles that paperwork.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Lyro reads the Printautopilot actions it has and picks the ones a request needs.
Authorize the Printautopilot 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.
Describe the job the way you would hand it to a teammate. Lyro maps it to the Printautopilot 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 freePrintautopilot · Lyro
What can you do in Printautopilot without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Lyro can do inside Printautopilot.
No. The connected toolkit exposes three actions - List Queues, Upload File, and Create Document - and none of them report job status, so Lyro can confirm a document was accepted into a queue but not that paper came out of the printer. Check the job itself in PrintAutopilot.
All 3 actions your agent can call on Printautopilot, straight from the live MCP connection.
Upload a base64 formatted PDF document to PrintAutopilot queue.
List available PrintAutoPilot queues.
Upload a file to a temporary R2 bucket.
Same connection, same setup. Pick the next one your team already uses.
Answers security questions from the knowledge base, grants and revokes Trust Center access, and maintains the document library.
Queries records with filters and pagination, writes and corrects rows, adds fields as your data changes, and subscribes webhooks to record events.
Fetches live pages as Markdown, JSON, or screenshots, runs crawl and extraction jobs to completion, and manages browser sessions and profiles.
Starts a workflow run against the right template, pulls the data set rows it needs, and closes the run out or restores one deleted by mistake.
Searches send, open and bounce activity, authorises senders, domains and IPs, maintains the suppression list, and manages event webhooks.
Filters a Workiom list down to the record a customer is asking about, and files new records from the conversation as they come in.

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