Can Lyro tell whether a print job finished?

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.

What file format does Lyro have to send?

Create Document takes a base64-encoded PDF and validates the encoding before it is submitted, so PDF is the format that reaches a queue. Upload File stages other files in temporary storage for later operations, but the queue submission itself is a PDF.

Where does a file sit between upload and printing?

Upload File puts it in a temporary R2 bucket that PrintAutopilot uses for staging, which is what makes a two-step flow possible: Lyro can hold a document while it confirms the queue with the person asking, then submit it.

How is this different from a Zapier or Make print automation?

Those run a fixed path: a trigger fires and the same file goes to the same queue every time. Lyro decides in the conversation which queue fits, asks when it is ambiguous, and can stage a file first and submit it only once the answer is clear.

Printautopilot MCP integration

Lists the available print queues, stages the file, and submits a PDF to the printer that should handle it.

Connect Printautopilot See all integrations

3actions available

What your agent can do with Printautopilot

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

Create document
Lyro uploads PDFs to PrintAutopilot's queue directly from conversations. Documents reach the print system instantly without manual intervention.
List queues
Lyro lists available print queues to route jobs correctly. Support agents can verify which destinations are live before queuing documents.

See all 3 actions

How businesses use Printautopilot + Lyro

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

Send a job to a queue that actually exists
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.
List QueuesCreate Document
Print a document straight from the conversation
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.
Upload FileCreate DocumentList Queues
Stage a file now, print it once the queue is confirmed
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.
Upload FileList Queues
Reprint paperwork on request
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.
Upload FileCreate Document

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

01
Connect Printautopilot
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.
02
Tell your agent what you need
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.
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

Printautopilot · Lyro

Everything else about Printautopilot

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.