Print from Zapier automatically to your office printer
Print from Zapier without opening ports: send PDFs from Gmail, Google Drive, Dropbox or your shop to the office printer with a Code or Webhooks step.
Mis à jour le 21 octobre 2026
Many Zaps create or receive documents that someone needs on paper in the end: invoices from the shop, packing slips for the warehouse, shipping labels or email attachments that have to be signed off. Zapier has no print app of its own, and a printer on the office network cannot be reached from the cloud. This article shows how to print from Zapier with the built-in apps Code by Zapier or Webhooks by Zapier and Sealed Print, without opening a port on the router.
How printing from Zapier works
The Zap sends the document over HTTP to a secret Sealed Print URL, called an API endpoint. Sealed Print creates a print job from it and delivers it to the printer:
- through the relay client on a computer or NAS in the office where the printer is installed,
- directly to printers with IPP INFRA support, which fetch their jobs themselves,
- or over IPP to a printer that is reachable from the internet.
The relay client and INFRA printers only open outgoing connections. Nothing has to be opened on the office router. Zapier runs only in the cloud, so this is the usual way to get documents from a Zap onto paper.
Prerequisites
- A Sealed Print account with at least one destination, that is a printer. The guide Install the relay client explains how to connect a printer in the office.
- An admin has switched on the inbound channel REST API under Settings → Inbound channels. It is off by default.
- A paid Zapier plan, generally Professional or higher. According to Zapier, Webhooks by Zapier is not included in the Free plan, and Code steps may only run for about one second there, which is usually not enough to download and upload a PDF.
- The document is a PDF, JPEG or PNG file of at most 50 MB.
Step 1: Create an API endpoint in Sealed Print
- Go to Sources → API endpoints and select New API endpoint.
- Enter a Name, for example "Zapier invoices".
- Under Target, choose the printer, destination group or workflow the documents should go to. With Default target, every job goes to your default target; with No target – keep in Sealed Print, it waits in the queue until someone checks and sends it.
- Select Create and copy the Endpoint URL. It looks like this:
https://www.sealedprint.com/api/print/sp_ep_…
The URL is the access key. Anyone who knows it can send documents to your printer. No API token or password is needed. More in the guide API endpoints.
Step 2: Choose a trigger that delivers the document
A Zap starts with a trigger that provides a file. Typical examples:
- Gmail with the trigger New Attachment: it starts a separate run for every attachment of an email.
- Google Drive or Dropbox with New File in Folder, for example for a folder called "To print".
- Shopify with a new order, followed by a step that fetches the invoice or packing slip PDF from your invoicing app.
Zapier shows files in a step's output as (Exists but not shown). The file is only downloaded during the run. In the next step, map exactly this field, not a field with the file name or size. Map only one file: Zapier packs several files in one file field into a ZIP archive, and Sealed Print rejects that.
A Filter by Zapier step with Only continue if… stops unsuitable files, for example by letting through only
attachments whose file name ends in .pdf. That keeps signature images from emails out of the printer.
Step 3: Send the document to Sealed Print
There are two ways to make the actual call. The Code step sends the file exactly the way Sealed Print prefers it: as the
request body with a matching Content-Type and the options as query parameters. The Webhooks step needs no code, but it
sends the file as a form whose structure you control less precisely in Zapier.
Option A: Code by Zapier
Add the app Code by Zapier with the event Run Javascript. Under Input Data, create three entries:
| Key | Value |
|---|---|
file | the file field from the trigger, for example the Gmail attachment |
name | the job name, for example the invoice number |
endpoint | your endpoint URL https://www.sealedprint.com/api/print/sp_ep_… |
In the Code step, a file arrives as a download URL. The code fetches it, sends it to Sealed Print and passes the response on to the following steps:
const source = await fetch(inputData.file)
if (!source.ok) {
throw new Error(`Download failed: HTTP ${source.status}`)
}
const url = new URL(inputData.endpoint)
url.searchParams.set("name", inputData.name || "Zapier")
url.searchParams.set("sides", "two-sided-long-edge")
const response = await fetch(url, {
method: "POST",
headers: { "Content-Type": "application/pdf" },
body: Buffer.from(await source.arrayBuffer()),
})
const text = await response.text()
if (!response.ok) {
throw new Error(`Sealed Print: HTTP ${response.status} ${text}`)
}
const job = JSON.parse(text)
output = { id: job.id, number: job.number, name: job.name, state: job.state }
For JPEG or PNG files, set the Content-Type to image/jpeg or image/png. Add more options with
url.searchParams.set(…). According to Zapier, a Code step may run for 30 seconds on the Professional and Team
plans. That is enough for typical PDFs.
Option B: Webhooks by Zapier
Add the app Webhooks by Zapier with the event POST. Only POST and PUT can send files, Custom Request cannot.
| Field | Value |
|---|---|
| URL | your endpoint URL https://www.sealedprint.com/api/print/sp_ep_… |
| Payload Type | Form |
| Data | the options as name and value, for example name and copies |
| File | the file field from the trigger |
With a file in the File field, Zapier sends the request as multipart/form-data. Sealed Print expects the file in
the form field file and detects the format from the MIME type or the file extension .pdf, .jpg or .png. With a
form, Sealed Print reads the options from the form fields, not from query parameters in the URL.
Zapier does not document exactly under which names the file and the Data fields arrive in the form. After the
first test, check in the Queue whether the name and options were applied. If Sealed Print answers with HTTP 400 and
a note about the field file, or the options are missing, use option A. Zapier also lists a maximum payload of 5 MB
for webhook actions. Larger files are also better sent with the Code step.
The response from Sealed Print
Sealed Print answers with HTTP 201 and the created job as JSON, including id, number, name and state. The job
appears in the Queue right away. You can use these fields later in the Zap, for example to write the job number
into a spreadsheet.
Both options correspond to this curl command:
curl -X POST "https://www.sealedprint.com/api/print/sp_ep_…?name=Invoice%201042&sides=two-sided-long-edge" \
-H "Content-Type: application/pdf" \
--data-binary @invoice-1042.pdf
Parameters: name, print options and destination
All parameters are optional. In the Code step you set them as query parameters, in the Webhooks step as fields under Data. Values can come from earlier steps, for example the order number from Shopify.
Name and print options
| Parameter | Meaning | Values |
|---|---|---|
name | job name in the queue | text, at most 200 characters; "API job" if omitted |
copies | number of copies | 1 to 999 |
sides | one-sided or duplex | one-sided, two-sided-long-edge, two-sided-short-edge |
colorMode | color | auto, color, monochrome |
media | paper size as PWG name | for example na_letter_8.5x11in, na_legal_8.5x14in, iso_a4_210x297mm |
mediaSource | paper tray | tray name as reported by the printer, for example tray-2 |
orientation | orientation | portrait, landscape, reverse-landscape, reverse-portrait |
quality | print quality | draft, normal, high |
pageRanges | only certain pages | for example 1-3,5 |
scaling | scaling | auto, auto-fit, fill, fit, none |
finishings | finishing, several separated by commas | for example staple, staple-top-left, punch, fold |
Sealed Print adapts the options to the device. If a printer cannot do something, such as duplex, it still prints the job with the capabilities it has.
Where the job goes
The simplest way to route a job is the query parameter targets. It takes the identifiers of destinations and
destination groups, several separated by commas. You find the identifier in Sealed Print in the Identifier column
under Targets and on every group. It is the same short name as in the printer URL
…/ipp/print/<token>/<identifier> and in email addresses with +<identifier>.
Value of targets | Effect |
|---|---|
warehouse | prints on the destination with the identifier warehouse instead of the endpoint's destination |
warehouse,office | prints on both destinations |
all-printers | prints on every printer in the destination group all-printers |
For an unknown identifier, Sealed Print answers with HTTP 404 and names it in the response.
Instead of identifiers you can also pass IDs:
| Parameter | Meaning |
|---|---|
destinationId | ID of a destination |
destinationIds | several destination IDs separated by commas; every destination prints the job |
groupId | ID of a destination group; every printer in the group prints the job |
noTarget | true: no target, the job waits in the queue until someone sends it (like targets=hold) |
Sealed Print decides in this order:
- Destinations in the request:
targets,destinationId,destinationIdsorgroupIdreplace the endpoint's destination for this one job. - The endpoint's destination: if the request names no destination, the destination or group chosen on the endpoint applies.
- Default target: if the endpoint is set to Default target, the job goes to the default target of the person who owns the endpoint, otherwise to the organization's default target. See Your default target.
Several destinations in one request and destination groups are part of the Sealed Print Team plan. Without it, Sealed Print answers with HTTP 402. The guide Destination groups explains how groups work.
The simplest way: one endpoint per destination
If a Zap always prints on the same printer, you need no parameters at all. Create a separate endpoint for each destination, for example "Zapier warehouse" for the label printer and "Zapier accounting" for the office printer. With Paths by Zapier you branch by document type or sender, and every path sends to its own URL. According to Zapier, Paths is available from the Professional plan. For a single printer, a filter is enough.
Find the IDs of destinations and groups
For targets, the identifier from the interface is enough. The REST API returns the IDs for destinationId and
groupId with an API token:
- Create a token under Settings → API tokens.
- With Webhooks by Zapier and the event GET, call one of these addresses, with the header
Authorizationand the valueBearer sp_api_…under Headers:https://www.sealedprint.com/api/destinationsfor destinations,https://www.sealedprint.com/api/destination-groupsfor destination groups.
- Every entry has an
idand aname. Copy theidinto the parameter.
You only need the API token to look things up. To print, the endpoint URL is enough, because API tokens cannot submit jobs themselves. The API reference describes every endpoint.
Errors, retries and tasks
- HTTP 400: an option has an invalid value, such as
sides=duplex, or the form is missing the fieldfile. The response names the field. - HTTP 402: several destinations or a destination group without the Team plan.
- HTTP 403: the inbound channel REST API is switched off, or the person who owns the endpoint has left the organization.
- HTTP 404: the URL is wrong or was replaced with Generate new URL, or an identifier in
targetsdoes not exist. The response then names the identifier. - HTTP 413: the file is larger than 50 MB or larger than your plan allows.
- HTTP 415: the file is not a PDF, JPEG or PNG, for example a ZIP archive, or the
Content-Typeis missing.
You see failed runs in the Zap History. From the Professional plan, Zapier can retry failed steps automatically with Autoreplay, according to Zapier up to five times. Be careful: every successful call creates a new job. If the connection drops after Sealed Print has already accepted the job, a retry prints the document a second time. The same applies when you replay a run by hand. When in doubt, check the Queue. For errors such as 400, 403 or 415, a retry does not help. You can switch off Autoreplay for a single Zap in its advanced settings with Never replay.
Zapier counts every successful Webhooks or Code step as one task. According to Zapier, triggers, filters and paths do not use tasks. One printed document therefore generally costs one task.
Frequently asked questions
Does Zapier have its own print app?
No. Zapier does not include a print app. With Code by Zapier or Webhooks by Zapier you send the document to a cloud print service such as Sealed Print, which delivers it to the printer in the office.
Is Zapier free, or do I need a paid plan?
Zapier has a Free plan, but for printing you generally need a paid one. Webhooks by Zapier is not included in Free, and Code steps only get about one second of run time there. With Professional or higher, both options work.
Do I have to open a port on the office router?
No. The relay client and INFRA printers only open outgoing connections to Sealed Print. No incoming connections into the office network are needed.
How do I print from one Zap to different printers?
Either with a separate API endpoint per printer and Paths by Zapier, or with the parameter targets and the
printer's identifier for each job. With the identifier of a destination group, every printer in the group prints the
same job.
How do I know whether the document was printed?
In the Sealed Print queue, with the delivery status of every job. In the Zap, you can query the job with an API token
at https://www.sealedprint.com/api/jobs/<id>; the id is in the response to the print request. The field state
then reads completed.
What does printing from Zapier cost, and are there alternatives?
Sealed Print bills per delivery, that is per job to one printer. The plans are on the pricing page. In Zapier, every print call counts as one task. If you use n8n instead of Zapier, see Print from n8n automatically.