ezeep Blue
Utilities & PersonalSend documents from a flow straight to any cloud-connected printer with ezeep Blue, choosing copies, color, duplex, and paper format. Agents print picking lists, labels, and signed paperwork where a physical copy is still required.
What This Integration Enables
Paper is not a legacy problem to be automated away. In a warehouse the pick list is what the picker carries down the aisle. In a clinic the discharge summary is the artifact the patient leaves with. In a court and in a freight yard the signed page is the record. Plenty of processes are digital at every step except the one where they become physical, and that last step is usually the one that breaks, because it depends on a driver installed on a machine at a site, maintained by whoever was there when it was set up.
ezeep Blue removes the driver from the path. FlowRunner agents send a document produced earlier in a flow straight to a cloud-connected printer, choosing copies, color, duplex, tray and paper format, and get a print job ID back that they can poll. They can upload once and print to several sites, print from a URL without routing the bytes through FlowRunner at all, hold a job in the pull-print queue until someone releases it onto a specific device, and cancel a queued job before it ever reaches paper. Administrators get the rest of the surface: the printer inventory, the group assignments that decide who can see which device, the connectors that link the hardware to the cloud, and asynchronous CSV reports covering every job in a date range. What the connectors layer buys you here is that the flow stops caring where the printer is. What FlowRunner adds on top is that it also stops assuming a printer is a safe place to send something unattended.
Without FlowRunner
With FlowRunner
Use Case Scenarios
Pick lists at the site that is shipping the order
Orders release for picking in waves. For each order the agent builds the pick list, resolves the correct site printer with Get Available Printers using the warehouse code on the order, and confirms with Get Printer Properties that the device supports the paper format the label stock needs. It submits the document with Print File and stores the print job ID on the order record. When On Print Job Event returns, the order is stamped with the page count and the outcome. A picker who reports a missing sheet gets an answer from the order record rather than a walk to the printer, and a jam that stops a wave surfaces in the shift channel while the wave is still open.
Signed paperwork released at the counter
A contract is signed electronically in DocuSign and a countersigned copy has to be handed over in person. The agent calls Upload Document to place the PDF in ezeep storage without printing it, then leaves it in the pull-print queue. When the customer arrives, a member of staff at the counter triggers the release step, the agent calls Release Print Job against the device beside them, and the page comes out while they are standing there. The document is never sitting in a tray in an empty room.
Monthly print cost and volume reporting
At the start of each month the agent calls Create Print Report for the previous month, polls Get Print Report until it reads succeeded, then calls Download Print Report to save the CSV into FlowRunner file storage. From there it pushes the file into Google Sheets for the finance review and posts the headline volume per site into the operations channel. The report can be generated with personal data blanked, which is what makes it usable in an organization that cannot circulate a per-user print log.
Human-in-Loop Highlight
Printing is not undoable, and ezeep is explicit about the boundary: a queued job can be cancelled, but a job already sent to a printer cannot be recalled. That boundary is exactly where an agent should stop. The case that makes it concrete is a document with a named individual on it, a discharge summary, a payroll advice, a countersigned contract, destined for a device in a shared corridor. The agent has everything it needs to print: the file, the printer ID from Get Available Printers, the location string that says Corridor MFP. What it does not have is any way to know whether anyone is standing next to that device, and once the pages are out, the only recovery is a person walking to the tray. So the agent leaves the job in the pull-print queue instead of releasing it, and asks the owner in their channel: "Discharge summary for record 8842 is queued. Release now to Clinic 2 Corridor MFP, or hold until a nurse is at the device?" Release Print Job is the resume step, and Cancel Print Job is the other answer. That is human-in-the-loop doing something a retry policy cannot: deciding that the safest thing an automated system can do with a piece of paper is not print it yet.
Agent Capabilities
30 actionsPrinting
5- Print File Print a FlowRunner file on a cloud-connected ezeep printer in one step, uploading the bytes and queueing the job together. Used for documents produced earlier in a flow such as invoices, labels and pick lists. Returns the print job ID for polling.
- Print Document From URL Print a document that ezeep downloads from a publicly reachable URL, without routing the bytes through FlowRunner. Used for large files and for documents already hosted somewhere the printer service can reach. The URL must carry any access token it needs.
- Upload Document Upload a FlowRunner file into ezeep storage and return the file ID without printing it. Used when the same document has to reach several printers: upload once, then print per device.
- Print Uploaded Document Print a document already in ezeep storage by file ID. Used to send one uploaded document to multiple printers or with different finishing options without re-uploading it.
- Get Print Configuration Retrieve the rendering configuration for the connected organization, most usefully the list of printable file extensions. Used as a pre-check before submitting a document type the organization may not support.
Print Jobs
4- Get Print Job Status Retrieve the live state of a job including queue position and pages printed so far. Used to poll after submission until the job finishes or errors.
- List Print Jobs List the print jobs stored for the connected user, newest first. Used to find pull-print jobs waiting for release and to read recent history.
- Cancel Print Job Delete a stored print job so it is never released to a printer, freeing its storage. Used to cancel a queued pull-print job or clear a failed one. Jobs already sent to a printer cannot be recalled.
- Release Print Job Release a queued pull-print job onto a specific printer, the equivalent of walking up to a device and tapping print. Used as the resume step after a person confirms the document should come out on that device.
Printers
3- Get Available Printers List every cloud printer the connected user may print on, with ID, name and physical location. Used to resolve a printer before submitting a job, reflecting the user's group assignments rather than the whole inventory.
- Get Printer Properties Retrieve a printer's full capabilities: color and duplex support, supported paper formats and IDs, orientations, resolutions, trays and defaults. Used to confirm a print action's settings will be accepted before submitting.
- Get Printer Capabilities Retrieve the organization's capability overrides for a printer, covering whether color and duplex are permitted and which trays are enabled. Used to respect policy that sits on top of what the driver technically supports.
Printer Administration
5- List Managed Printers List the printers registered in the organization with their connector, driver assignment, status and spool formats. Used for the administrative inventory view, with paging. Requires an administrator connection.
- Update Printer Update a registered printer's display name, location or status, leaving unspecified fields unchanged. Used to keep the inventory readable as devices move. Requires an administrator connection.
- Delete Printer Permanently remove a printer from the organization along with every group assignment referencing it. Users lose access immediately and queued jobs for that printer cannot be released. Requires an administrator connection.
- List Printer Assignments List every printer with the groups it is assigned to, which is what determines who can see and use it. Used to audit access before changing it. Requires an administrator connection.
- Assign Printer To Groups Set which groups a printer is assigned to. Used to grant or withdraw access to a device, noting that the supplied list replaces the current assignments entirely. Requires an administrator connection.
Connectors
3- List Connectors List the print connectors linking physical printers to the ezeep cloud, including ezeep Hub devices, print servers and virtual connectors, with status and operating system. Used to check whether a site's hardware is online before investigating a failed job.
- List Printers By Connector List every printer published through a single connector. Used to audit what a specific Hub or print server exposes, for example before decommissioning it. Requires an administrator connection.
- Delete Connector Remove a print connector from the organization, disconnecting every printer it published. Used when retiring a Hub or print server. Requires an administrator connection and cannot be undone.
Users and Organizations
7- Get Current User Retrieve the connected user's printing entitlements, covering pull printing, local printing, self service, My Printers and print later, together with their group IDs. Used to branch a flow on what the account is allowed to do.
- List Users List the users of the organizations the connection manages, with email, display name, roles, verification state and outstanding invitations. Used for onboarding and access review.
- Get User Retrieve a single user's profile including roles, join date and invitation history. Used for targeted lookups during access review.
- Invite User Send an ezeep invitation email so a new person can join the organization and print, with an expiry you set. Used as a step in staff onboarding.
- List User Invitations List every invitation sent from the connected account with its delivery status and whether it is open, accepted or expired. Used to chase people who have not joined yet.
- List Organizations List the ezeep organizations the connected partner account manages, each with its ID, name and profile link. Used to scope administrative actions. Requires partner-level API access.
- Get Organization Retrieve a single organization by ID. Used when a flow operates across more than one managed organization. Requires partner-level API access.
Reports
3- Create Print Report Start generation of a CSV report covering every print job in a date range, optionally blanking personal data for privacy compliance. Used for monthly cost and volume reporting. Generation is asynchronous.
- Get Print Report Check the generation state of a report. Used to poll until the report reads succeeded, or to detect that generation failed and the report should be recreated.
- Download Print Report Download a completed report and save the CSV into FlowRunner file storage, returning a URL for later steps. Used to hand the file to a spreadsheet parser, a storage bucket or an email attachment.
Triggers
1 triggersEvent Triggers
1- On Print Job Event Fires when an ezeep print job finishes, either successfully or with an error, delivering the final job state including printer, connector, page count, paper, duplex, color and CO2 impact. ezeep registers a webhook endpoint for the flow, so this reports the outcome rather than polling for it. Optionally restrict the trigger to a single printer, which is what you want when one device at one site is the thing a workflow depends on.
Frequently Asked Questions
What can FlowRunner do with ezeep Blue?
FlowRunner agents can run Print File, Print Document From URL, and Upload Document in ezeep Blue, plus 27 more actions.
Does connecting ezeep Blue to FlowRunner require OAuth?
Yes. ezeep Blue connects to FlowRunner with OAuth 2.0, so agents authenticate without handling raw credentials.
Can ezeep Blue trigger a FlowRunner workflow automatically?
Yes. ezeep Blue supports 1 trigger that can start a FlowRunner workflow automatically.
Start building with ezeep Blue
$100 in credits. No card required. Connect in minutes.