Print from n8n automatically with the HTTP Request node
Print PDFs from n8n workflows automatically with the HTTP Request node and Sealed Print. All parameters for printers, groups and print options.
Atualizado a 21 de outubro de 2026
Many n8n workflows produce documents that someone eventually needs on paper: invoices from the online store, packing slips for the warehouse, shipping labels, reports for the weekly meeting or email attachments that have to be signed off. n8n has no print node of its own, and a printer on the office network cannot be reached from n8n Cloud or from a server in a data center. This article shows how to print from n8n automatically with the built-in HTTP Request node and Sealed Print, without opening ports and without writing a script.
How printing from n8n works
The workflow sends the document over HTTPS to a secret Sealed Print URL, called an API endpoint. Sealed Print turns it into a print job 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, and it does not matter whether n8n runs in the cloud, on your own server or on a Raspberry Pi.
Prerequisites
- A Sealed Print account with at least one destination, that is, a printer. How to connect an office printer is explained in the guide Install the relay client.
- An admin has switched on the inbound channel REST API under Settings → Inbound channels. It is off by default.
- A current version of n8n, either n8n Cloud or self-hosted. You only need the built-in HTTP Request node, no community node.
- The document is a PDF, JPEG or PNG and no larger than 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 "n8n 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. You do not need an API token or a password. More in the guide API endpoints.
Step 2: Provide the document in the workflow
The HTTP Request node sends a file from the binary data of the previous node. Typical sources are:
- Gmail or Microsoft Outlook with downloaded attachments (field
attachment_0), - Google Drive, Dropbox or OneDrive with the operation that downloads a file (field
data), - a second HTTP Request that loads a PDF from your store or accounting software, with Response Format set to File,
- Read/Write Files from Disk on self-hosted n8n.
Note the name of the binary field, usually data. You can see it in the node output under Binary.
Step 3: Set up the n8n HTTP Request node
After the node that provides the document, add an HTTP Request node and configure it like this:
| Setting | Value |
|---|---|
| Method | POST |
| URL | your endpoint URL https://www.sealedprint.com/api/print/sp_ep_… |
| Authentication | None |
| Send Query Parameters | on, with the parameters from the next section, for example name |
| Send Body | on |
| Body Content Type | n8n Binary File |
| Input Data Field Name | the name of the binary field, for example data |
n8n sends the file as the request body and sets the Content-Type from the file's MIME type. If it only says
application/octet-stream, which happens with some downloads, switch on Send Headers and set the header
content-type to application/pdf, image/jpeg or image/png.
Run the node once. Sealed Print answers with HTTP 201 and the created job as JSON, including id, number, name
and state. The job appears right away in the Sealed Print Queue. You can use these fields later in the
workflow, for example to write the job number into your CRM.
The request is equivalent 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
Query parameters: name, print options and destination
All parameters are optional. Enter them under Query Parameters as name and value. Values can come from previous
nodes, for example {{ $json.invoiceNumber }}.
Name and print options
| Parameter | Meaning | Values |
|---|---|---|
name | Name of the job in the queue | text, up to 200 characters; "API job" if omitted |
copies | Number of copies | 1 to 999 |
sides | Single-sided or duplex | one-sided, two-sided-long-edge, two-sided-short-edge |
colorMode | Color | auto, color, monochrome |
media | Paper size as a PWG name | for example na_letter_8.5x11in, na_legal_8.5x14in, iso_a4_210x297mm |
mediaSource | Paper tray | name of the tray as the printer reports it, 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 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 |
Sealed Print answers an unknown identifier 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) |
IDs never change, even when someone renames a destination. Identifiers are easier to read and can be copied straight from the interface.
Sealed Print decides in this order:
- Destinations in the request:
targets,destinationId,destinationIdsorgroupIdreplace the endpoint's destination for this one job. - Destination of the endpoint: 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 Team plan. Without it, Sealed Print answers with HTTP 402. How groups work is described in Destination groups.
The simplest way: one endpoint per destination
If a workflow always prints to the same printer, you need no parameters at all. Create a separate endpoint for each destination, for example "n8n warehouse" for the label printer and "n8n accounting" for the office printer, and use the matching URL in the workflow. A Switch node can branch to different HTTP Request nodes depending on the document type.
Finding 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 when you call it with an API token:
- Create a token under Settings → API tokens, see API tokens.
- In an HTTP Request node (Method
GET, Send Headers on, headerAuthorizationwith the valueBearer sp_api_…), call one of these addresses: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 for looking things up. Printing only needs the endpoint URL, because API tokens cannot submit jobs themselves.
Examples
Invoice, double-sided, two copies:
| Name | Value |
|---|---|
name | Invoice {{ $json.number }} |
sides | two-sided-long-edge |
copies | 2 |
Packing slip to the warehouse printer instead of the endpoint's destination:
| Name | Value |
|---|---|
targets | warehouse |
Notice to every printer in a destination group (Team plan):
| Name | Value |
|---|---|
targets | all-printers |
colorMode | monochrome |
Printer depending on the document: the identifier can come from a previous node, for example
{{ $json.location === "Building 2" ? "warehouse-building-2" : "warehouse" }}.
Alternative: form data instead of a binary body
Instead of sending the file as the request body, you can send a form. Set Body Content Type to Form-Data, add a
parameter of type n8n Binary File named file, and pass the options as additional form fields, for example
name and copies. Important: with a form, Sealed Print reads the options from the form fields, not from the query
parameters. The file needs a file name ending in .pdf, .jpg or .png if n8n does not send a matching MIME type.
Errors and what they mean
- HTTP 400: an option has an invalid value, such as
sides=duplex. 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, or the
Content-Typeis missing. Set the header as described in step 3.
Be careful with Retry On Fail in the node settings: 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. If in doubt, check the Queue.
The same approach works from any other program that can send an HTTP request, see the use case Print API.
Frequently asked questions
Does n8n have a print node?
No. n8n does not ship a print node. With the built-in HTTP Request node you send the document to a cloud print service such as Sealed Print, which delivers it to the printer. Community nodes for printing exist, but they generally need the printer on the same network as n8n.
Does this work with n8n Cloud?
Yes. The workflow only calls an HTTPS address. The printer stays in the office and fetches the job through the relay client or over IPP INFRA. n8n and the printer do not have to be on the same network.
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. Incoming connections into the office network are not needed.
How do I print to different printers from one workflow?
Either with a separate API endpoint per printer, or with the query 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 check whether the document was printed?
In the Sealed Print queue, which shows the delivery status of every job. In the workflow, you can query the job at
https://www.sealedprint.com/api/jobs/<id> with an API token; the id is in the response to the print request. The
field state then reads completed.
What does printing from n8n cost?
Sealed Print bills per delivery, that is, per job to one printer. The plans are listed on the pricing page. n8n itself is generally free to self-host as the Community Edition, while n8n Cloud has its own paid plans.