Zapier & Make (no-code automation)
You don't need to write code to print from another app. PaperReady connects to Zapier and Make, so a new order, a form submission, or a spreadsheet row can print a label on your own printer automatically — "when X happens, print Y."
What you get
- Action — Print a Label: pick a printer and one of your saved designs, then map the incoming data (customer name, SKU, address) onto the design's fields. Or send a pre-rendered PDF/PNG or raw ZPL.
- Trigger — Print Event: start a workflow the moment a label prints, fails, or expires — log it to a sheet, post to Slack, whatever you like.
Connect it
- In your console → API keys, create a key (it starts with
pr_live_). - In Zapier or Make, add PaperReady and paste that key when it asks to connect. It'll show your workspace name once connected.
- Add the Print a Label action, choose your printer + design, and map the fields from the trigger app.
Make sure the target computer's Print Bridge is running — that's what the label actually prints on. Jobs to an offline workstation queue for a few minutes and print when it reconnects.
Under the hood
Both integrations use the same cloud API and your API key: the action calls POST /api/v1/print, and the trigger subscribes your Zap/scenario to print webhooks via /api/v1/hooks. So every automated print is metered exactly like an API print ($0.01 per delivered label), and shows up in your usage and history.
Building the integration yourself or self-hosting? The Zapier (Platform CLI) and Make (app blueprint) sources live in the project's
integrations/ folder, and every endpoint they use is in the OpenAPI spec.