PrintNode
Utilities & PersonalSend documents from workflows to physical printers through PrintNode cloud printing. Agents discover connected computers and printers, check account credits, submit PDF or raw print jobs by URL or Base64, and track job status for auditing.
What This Integration Enables
The physical world still runs on paper: packing slips in bins, labels on boxes, invoices in front-desk trays. PrintNode bridges cloud workflows to the printers attached to real computers, and this connector makes that bridge an agent's tool. FlowRunner agents verify the account and its credit balance, discover which computers and printers are online, submit PDF or raw print jobs by URL or Base64, and track each job's state for auditing. - Print invoices, receipts, labels, and packing slips as workflow steps - Discover connected computers and their printers, and select targets dynamically by name - Check remaining print credits before dispatching, so jobs do not fail midstream - Submit PDFs and raw printer data from URLs or Base64 payloads - Track job state from queued to printed for audit and reconciliation Print jobs consume a finite credit balance and produce physical output that cannot be un-printed, which is exactly the shape of operation FlowRunner's [human-in-the-loop](/concepts/human-in-the-loop) checkpoints exist for.
Without FlowRunner
With FlowRunner
Use Case Scenarios
The packing slip that beats the picker to the shelf
A [Shopify](/integrations/shopify) order triggers the flow: the agent confirms the warehouse printer is online via List Printers, submits the packing slip with Create Print Job using the PDF-from-URL content type, and logs the returned job id to [Google Sheets](/integrations/google-sheets). By the time the picker reaches the staging area, the slip is in the tray. Offline-printer detection reroutes to the backup machine and flags the outage to [Slack](/integrations/slack).
Invoices generated and handed over in one motion
When an invoice is finalized in [Invoice Ninja](/integrations/invoice-ninja), the agent prints it to the front-desk printer for immediate handoff. Get Print Job confirms completion, and any job that sits queued, usually a sleeping computer running the PrintNode client, escalates with the machine's connection state attached, so the fix is a wake-up, not a mystery.
Document pipeline to paper, with credits watched
Generated documents from [APITemplate.io](/integrations/apitemplate-io) flow straight to print. Before each batch, Get Account Info reads the remaining credit balance; when the balance falls below the size of the pending batch plus a reserve, the run pauses and a person decides whether to top up or trim the batch. Nothing fails half-printed, and the credit purchase decision stays with whoever owns the budget.
Human-in-Loop Highlight
Create Print Job spends twice with one call: it consumes a PrintNode credit from a finite balance and commits ink and paper on a physical machine, and neither comes back if the job was wrong. One mistaken packing slip is noise; a mis-templated batch of 500 is an afternoon of shredding and a drained credit pool. So batch dispatch has a proportional gate. Routine per-order jobs flow untouched, but a run that exceeds the day's normal volume, or any job pointed at a new printer target for the first time, pauses with the facts attached: document sample, target printer and its computer, job count, credits remaining after the run. A person approves, and the agent dispatches, confirms each job's printed state, and reconciles the log. The judgment about whether 500 pages should exist belongs to someone who can see the printer from their desk.
Agent Capabilities
9 actionsAccount
1- Get Account Info Returns the API account's holder, email, remaining print credits, connected computer count, total prints, and permissions. The pre-flight check before any dispatch.
Computers
2- List Computers Lists the computers running the PrintNode client with id, name, hostname, client version, IP addresses, and connection state. The top of the discovery chain.
- Get Computer Retrieves a single computer by id with its connection state. The diagnostic read when jobs sit queued.
Printers
3- List Printers Lists every printer across all connected computers with id, name, capabilities, current state, and owning computer. The selection step before dispatch.
- List Printers on a Computer Lists the printers attached to one computer by its id, with the same detail scoped to a single machine.
- Get Printer Retrieves a single printer by id with capabilities, state, and its computer. The verification read for a specific target.
Print Jobs
3- Create Print Job Submits a PDF or raw print job to a printer, by public URL or Base64 payload, returning the job id. Consumes print credits; the operation this page's human gate scales with.
- List Print Jobs Lists submitted jobs, newest first by default, with id, target printer, title, content type, source, timestamp, and state. The audit trail.
- Get Print Job Retrieves one job by id with its current state. The confirmation step that closes the loop on every dispatch.
Frequently Asked Questions
What can FlowRunner do with PrintNode?
FlowRunner agents can run Get Account Info, List Computers, and Get Computer in PrintNode, plus 6 more actions.
Does connecting PrintNode to FlowRunner require OAuth?
No. PrintNode connects to FlowRunner with basic authentication (a username and password), no OAuth flow required.
Can PrintNode trigger a FlowRunner workflow automatically?
PrintNode doesn't currently expose triggers in FlowRunner. It connects as an action step inside workflows started by another trigger.
Start building with PrintNode
$100 in credits. No card required. Connect in minutes.