Resources · Make integration

PrintNode Make integrationAutomate PrintNode with Make.

What if documents printed themselves the moment another app had them ready? The PrintNode Make integration offers 11 modules: 1 instant trigger, 3 actions and 7 searches. This guide is for ops teams who print labels, tickets or forms, and it walks you from connection to a working first scenario.

Try the PrintNode integration on MakeSee the 11 modules

Verified Trustpilot reviews · AI, automation & growth agency

What you can automate

What can the PrintNode Make integration do for you?

The PrintNode Make integration links your PrintNode account to Make, a visual tool where you build a scenario: an automation made of modules, each one a brick that triggers, acts or searches. With it, Make can send print jobs to your printers, react to new PrintNode events and read what happened to computers, printers and jobs.

Paper out of the printer, straight from another app. A warehouse team gets a new shipment in its order tool; the next module, Send a Print Job, drops the document into the queue of the right printer. Nobody opens a file or clicks Print.

Printing you can check. Send a Print Job (synchronous) waits for the result before the scenario moves on, so a front desk can post the outcome in its team chat or write it to a sheet. Get Print Job States and Get a Print Job let a later scenario look back at a job it did not send itself.

A live picture of your print setup. Watch New Events starts a scenario as soon as PrintNode records something new, while List Computers and List Printers give an IT lead an inventory of every machine attached to the account.

The PrintNode documentation gives no numbered limit for these modules, so the ceilings that count are those of your Make plan; the Make pricing page compares them. If you are weighing Make against n8n, the n8n vs Make comparison sets out the criteria. And if you want a guided path through the editor, Make training starts from zero.

Connect

How do you connect PrintNode to Make?

  1. 01

    Create an API key in PrintNode

    Log in to your PrintNode account and open API Keys. PrintNode asks for your account password first. Type a name for the key, something like the name of your scenario so you recognize it later, then click Create.

  2. 02

    Copy the key and open Make

    Copy the API key PrintNode shows you. In Make, add any PrintNode module to a scenario and click Create a connection. A connection is your PrintNode account linked to Make once, then reused by every PrintNode module.

  3. 03

    Paste the key and confirm

    Paste the key into the PrintNode API Key field and click Continue. Make saves the connection. From now on, the module fields can list the printers and computers that your account holds.

First scenario

Your first scenario: print a document and get the result back

GoalWhen a new file lands in the storage app your team already uses, Make sends it to your PrintNode printer and waits to learn how the job went.

  1. 01

    Create the scenario

    On the Scenarios page, create a new scenario and click the big +. Choose the trigger of the app that holds your documents, such as a new file in a shared folder.

  2. 02

    Add the PrintNode module

    Click the + on the right of that first module, search for PrintNode and pick Send a Print Job (synchronous). Select your connection, or create it with your API key.

  3. 03

    Choose the printer and map the data

    Once the connection exists, Make lists the printers it can read in your account: pick the one that should print. Then map the data coming from the first module into the job.

  4. 04

    Test with Run once

    Drop a test document where the first module looks, click Run once and open the bubbles above each module. You read the bundles each module received, including the result PrintNode sent back.

  5. 05

    Schedule and switch it on

    Open the clock on the first module to set how often Make checks it; a new scenario runs every 15 minutes by default. Switch the scenario on and it keeps printing without you.

Triggers

What starts a PrintNode scenario

1 module starts a scenario when something happens in PrintNode. A scheduled trigger is checked by Make on the scenario's schedule; an instant one is called by PrintNode as soon as it happens.

PrintNode1Watch New Events

Watch New Events

Instant trigger

In Make“Triggers when a new event is created.”

Watch New Events starts your scenario each time PrintNode records a new event in your account. What happens around your printers can then set off the rest of your automation, with no one refreshing a dashboard to spot it.

How it fires
instant. PrintNode calls Make through a webhook as soon as the event happens, which is what the lightning badge on the module means.
When to use it
you want a follow-up every time PrintNode reports something new, such as a line in a log sheet or a closer look with Get Print Job States.
Watch out
the documentation only says it fires on new events, so run the scenario with Run once and read one bundle before mapping anything.
Modules

Everything the PrintNode modules can do

PrintNode gives you 10 modules. For each one: what it does for you, when to reach for it, and what to watch out for.

PrintNode1

Make an API Call

Action

In Make“Performs an arbitrary authorized API call.”

Make an API Call is your way out when no ready-made module covers the job: it calls any endpoint of the PrintNode API from inside the scenario, with the connection you already set up, so there is no second key to paste.

When to use it
you know a PrintNode feature from its API and none of the ten other modules exposes it.
Watch out
you write the request yourself, so you need to know which endpoint you are calling and what it expects.
PrintNode2

Send a Print Job

Action

In Make“Sends a print job to a specific printer.”

Send a Print Job puts a document in the queue of one specific printer. You get paper out of a printer from any app Make can read, without anyone opening the file and clicking Print.

When to use it
a new order, ticket or form entry should come out at the desk that handles it, and nothing later in the scenario depends on how the job ended.
Watch out
if a later module needs the outcome, pick the synchronous version, which is the one built to wait for the result.
PrintNode3

Send a Print Job (synchronous)

Action

In Make“Sends a print job to a specific printer and waits for the result.”

With this variant, the scenario sends the job to a chosen printer and holds on until the result comes back. The modules after it work with a known outcome instead of a guess.

When to use it
you want to act on that result, for instance post it in your team chat or record it next to the order it belongs to.
Watch out
waiting counts toward the run time of the scenario, and on the Free plan a run stops after 5 minutes of execution.
PrintNode4

Get a Computer

Search

In Make“Gets a computer.”

Get a Computer fetches one computer from your PrintNode account, so the scenario knows which machine it is dealing with before it reports or prints anything.

When to use it
you already know which computer matters, say the one at the shipping desk, and want its details to feed a message or a check.
Watch out
it returns a single computer; to browse them all and choose, start with List Computers.
PrintNode5

Get a Printer

Search

In Make“Gets a printer.”

Before a job goes out, this search brings back the record of one printer from your account. It lets the scenario confirm it is aiming at the right device instead of trusting a name someone typed by hand.

When to use it
several teams share printers and you want the scenario to look up the exact one it targets.
Watch out
you still pick which printer to fetch; when you do not know it yet, List Printers shows every option.
PrintNode6

Get a Print Job

Search

In Make“Gets a print job.”

Need to follow up on a job already sent? Get a Print Job brings back that one job, so a scenario can revisit it well after the moment it went to the printer.

When to use it
a colleague asks whether a contract went out, and a scenario answers by reading the job rather than someone walking to the printer.
Watch out
you have to say which job you want; if you only know roughly when it left, List Print Jobs is the better start.
PrintNode7

Get Print Job States

Search

In Make“Gets a print job's states.”

This search returns the states a print job went through, which tells you its story rather than a single snapshot. Each state can arrive as its own bundle, meaning one item passed to the next module.

When to use it
a customer or colleague asks what became of a job you sent, and you want every step it went through, not just where it stands now.
Watch out
every bundle runs the following modules once, and each run is an operation counted on your Make plan.
PrintNode8

List Computers

Search

In Make“Lists computers.”

List Computers returns every computer attached to your PrintNode account, one bundle each. It is the quickest way to see which machines are ready to print from a single module.

When to use it
an IT lead wants an inventory in a spreadsheet, or a scenario must check that a given machine is still listed.
Watch out
the modules after it run once per computer, so a long list means more operations.
PrintNode9

List Printers

Search

In Make“Lists printers.”

This module gives the full list of printers in your PrintNode account. You see at a glance what the scenario can target, without opening PrintNode in another tab.

When to use it
you are setting up a new flow and want to know which printers exist, or you keep a shared sheet of printers up to date after a change.
Watch out
like any search, it can return zero, one or many bundles, and each one feeds the next modules separately.
PrintNode10

List Print Jobs

Search

In Make“Lists print jobs.”

For a view of what actually went to paper, List Print Jobs returns the jobs of your account as separate bundles, ready to be written to a log or checked one by one.

When to use it
a manager wants a record of printed documents in a sheet, or a scenario has to find a job you did not note down.
Watch out
many jobs mean many bundles, and each one costs an operation in every module that follows.
Need help

Need help automating PrintNode with Make?

A person reads every message.

FAQ

PrintNode and Make: common questions

01Is the PrintNode Make integration free?
Yes, on the Make side. PrintNode is a standard app, available from the Free plan. That plan allows 2 active scenarios, a minimum of 15 minutes between two scheduled runs, 5 minutes of execution per run, files up to 5 MB and 512 MB of data transfer. Paid plans (Core, Pro, Teams and Enterprise) lower the interval to 1 minute, remove the cap on active scenarios and allow 40 minutes of execution. Your PrintNode subscription is a separate matter this page does not cover.
02What do you need to connect PrintNode to Make?
A PrintNode account and an API key. In PrintNode, open API Keys, confirm with your account password, name the key and click Create. Copy the key, open Create a connection on any PrintNode module in Make, paste it into the PrintNode API Key field and click Continue. The documentation lists no other prerequisite. That single connection then works for all 11 modules, so you only go through these steps once.
03Does the PrintNode trigger in Make react in real time?
Yes. Watch New Events is an instant trigger: PrintNode calls Make through a webhook as soon as a new event happens, instead of Make checking at intervals. The module shows a lightning badge for that reason. It is the only trigger of the app. If you would rather start from something else, such as a new file or a form entry in another app, put that app's trigger first and add a PrintNode action behind it, as in the scenario above.
04What if the PrintNode module you need is missing in Make?
Use Make an API Call. It calls any endpoint of the PrintNode API from your scenario with the same connection, which covers what the 10 other modules do not. You write the request yourself, so check the endpoint before you start. On limits, the PrintNode documentation gives no numbered cap for these modules; the constraints you are more likely to meet are those of your Make plan, such as execution time and the minimum interval.
05Should you use Make or n8n for PrintNode?
It depends on how you like to build. On Make, PrintNode comes with 11 ready modules, an instant trigger and Make an API Call for the rest, all in a visual editor with a Free plan to start. Before choosing n8n, check whether it offers a PrintNode node and which operations it covers. Neither tool is ranked here: compare the modules you actually need, then test one scenario on each side.
Same platform

Other docs you might need on this stack.

Browse all integrations