Guide

Print from Make.com automatically to an office printer

Print from Make.com: send PDFs from Make scenarios to an office printer with the HTTP module and Sealed Print, no open ports, with routing and print options.

Aggiornato il 21 ottobre 2026

Many scenarios in Make.com (formerly Integromat) create or receive documents that someone eventually needs on paper: invoices from accounting, packing slips for the warehouse, orders from an online store or email attachments that need a signature. Make 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 Make.com automatically with the built-in HTTP > Make a request module and Sealed Print, without opening ports and without running your own server.

Make's interface is generally available only in English, so the module and setting names below are the English labels you see in Make.

How printing from Make.com works

The scenario sends the document over HTTPS 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, so nothing has to be opened on the office router.

Prerequisites

  • A Sealed Print account with at least one destination, meaning a printer. The guide Install the relay client explains how to connect a printer in the office.
  • An admin has turned on the inbound channel REST API under Settings → Inbound channels. It is off by default.
  • A Make account. You only need the built-in HTTP app in its current version, not HTTP (legacy).
  • The document is a PDF, JPEG or PNG and at most 50 MB. Make also limits file size by plan; according to Make, the free plan allows 5 MB.

Step 1: Create an API endpoint in Sealed Print

  1. Go to Sources → API endpoints and choose New API endpoint.
  2. Enter a name, for example "Make invoices".
  3. 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.
  4. Choose Create and copy the Endpoint URL. It looks like this: https://www.sealedprint.com/api/print/sp_ep_…

The URL is the key: anyone who knows it can send documents to your printer, no token or password needed. Details are in the guide API endpoints.

Step 2: Provide the document in the scenario

In Make, a file consists of two parts: File name and Data. Every module that downloads or outputs a file provides both. Typical triggers and sources:

  • Gmail > Watch emails with Only emails with attachments/media, followed by Gmail > List email attachments and media with Return media or attachment file data turned on,
  • the Email app for Outlook and other IMAP mailboxes; split the attachment list of an email into single files with Iterator or Email > Iterate attachments,
  • Google Drive > Watch Files in a Folder, followed by Google Drive > Download a File,
  • invoicing tools with their own Make app, such as QuickBooks or Xero, if the app offers a module that returns the invoice PDF,
  • HTTP > Download a file when the PDF is available at a URL.

Step 3: Set up the Make a request module

After the module that provides the document, add HTTP > Make a request. For sending files, Make documents the body type multipart/form-data, which is a form. Sealed Print accepts this form directly:

SettingValue
Authentication typeNo authentication
URLYour endpoint URL https://www.sealedprint.com/api/print/sp_ep_…
MethodPOST
Body content typemultipart/form-data (supports file uploads)
Body content, field of type FileKey file; select the module from step 2 as the file or map File name and Data
Body content, fields of type TextOptions such as name or copies, see the next section
Parse responseYes

Make sets the Content-Type header for the form itself. The file name must end in .pdf, .jpg or .png so Sealed Print can detect the file type. If a module does not provide a clean name, map File name by hand, for example Invoice-{{1.number}}.pdf. Without a name field, the file name becomes the job name.

Run the module once with Run once. Sealed Print answers with HTTP 201 and the new job as JSON, including id, number, name and state. With Parse response set to Yes, you can use these fields in later modules. The job shows up in the Sealed Print Queue right away.

Form fields: name, print options and destination

All fields are optional. Add them under Body content as fields of type Text with a key and a value. Values can come from earlier modules.

Name and print options

FieldMeaningValues
nameJob name in the queueText, up to 200 characters; defaults to the file name
copiesNumber of copies1 to 999
sidesSingle-sided or duplexone-sided, two-sided-long-edge, two-sided-short-edge
colorModeColorauto, color, monochrome
mediaPaper size as a PWG namefor example na_letter_8.5x11in, na_legal_8.5x14in, iso_a4_210x297mm
mediaSourcePaper trayTray name as the printer reports it, for example tray-2
orientationOrientationportrait, landscape, reverse-landscape, reverse-portrait
qualityPrint qualitydraft, normal, high
pageRangesOnly certain pagesfor example 1-3,5
scalingScalingauto, auto-fit, fill, fit, none
finishingsFinishing, several separated by commasfor 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 what it can do.

Where the job goes

The easiest way to route a job is the targets field, as another Text field in the form. 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 targetsEffect
warehouseprints on the destination with the identifier warehouse instead of the endpoint's destination
warehouse,front-deskprints on both destinations
all-printersprints 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, the fields destinationId, destinationIds (several, separated by commas) and groupId take IDs. targets=hold or noTarget=true means no target: the job waits in the queue until someone sends it.

Sealed Print decides in this order:

  1. Destinations in the request: targets, destinationId, destinationIds or groupId replace the endpoint's destination for this one job.
  2. The endpoint's destination: if the request names no destination, the destination or group chosen on the endpoint applies.
  3. 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. The guide Destination groups explains how groups work.

Several printers: routers and filters

The simplest way needs no fields at all: create one endpoint per destination, for example "Make warehouse" for the label printer and "Make accounting" for the office printer. In the scenario, add a Router from Flow controls and attach a separate Make a request module with the matching URL to each route.

On the connecting line before each route, set a filter, for example by sender address, subject, folder or file name. Make processes the routes one after another; a fallback route receives everything that matches no other route.

If you need changing destinations instead of fixed URLs, use a single HTTP module with the targets field and the printer's identifier, which can also come from an earlier module, for example from a lookup table in Make.

To look up IDs, call https://www.sealedprint.com/api/destinations or https://www.sealedprint.com/api/destination-groups with an API token (see API tokens). The token is only for looking things up: API tokens cannot submit jobs, the endpoint URL is enough for printing.

Examples

Invoice, duplex, two copies: Text fields name with Invoice {{1.number}}, sides with two-sided-long-edge and copies with 2.

Packing slip to the warehouse printer instead of the endpoint's destination: Text field targets with warehouse, the identifier of the warehouse printer.

Notice to every printer in a destination group (Team plan): Text fields targets with all-printers, the group's identifier, and colorMode with monochrome.

Errors, error handling and retries

In the module's advanced settings, set Return error if HTTP request fails to Yes. Make then treats every 4xx or 5xx response as an error instead of passing it on silently. Sealed Print's responses mean:

  • HTTP 400: an option has an invalid value, such as sides=duplex, or the file field is missing. 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 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 targets does 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 file name has no matching extension.

Right-click the module and choose Add error handler to decide what happens on an error: Resume continues with a substitute value, Skip drops the bundle, and Retry stores the run as an incomplete execution that Make can complete later. Retry requires Store incomplete executions in the Scenario settings.

Be careful with retries: every successful call creates a new job. When incomplete executions are stored, Make also retries connection errors and timeouts without an error handler. If the connection drops after Sealed Print has already accepted the job, a retry prints the document a second time. Set a generous Timeout for large files, such as 120 seconds, and check the Queue before you repeat a run by hand.

Frequently asked questions

Does Make.com have a print app?

No. Make has no built-in print app. With the built-in HTTP > Make a request module, you send the document to a cloud print service such as Sealed Print, which delivers it to the printer in the office.

Do I have to open a port on the office router?

No. Make only calls an HTTPS address of Sealed Print. The relay client and INFRA printers only open outgoing connections to Sealed Print. No incoming connections into the office network are needed.

Can I print from Make on the free plan?

Generally yes. The HTTP app is available on every Make plan, but Make limits the file size on the free plan, according to Make to 5 MB. Larger PDFs need a paid Make plan. Sealed Print accepts files of up to 50 MB.

How do I print to different printers from one scenario?

Either with a router and a separate API endpoint per printer, or with the form field targets and the printer's identifier for the individual job. With the identifier of a destination group, every printer in the group prints the same job.

How do I see whether the document was printed?

In the Sealed Print queue, which shows the delivery status of every job. In the scenario, 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 state field then reads completed.

How much does printing from Make cost?

Sealed Print bills per delivery, meaning per job to one printer. The plans are on the pricing page. In Make, the scenario's operations count. If you also work with n8n, the article Print from n8n describes the same approach there.

Print and sign from anywhere

I firmatari firmano tramite link email senza account; tutti ricevono il PDF sigillato. Con Free paga solo per firma.

Altre guide e modelli