Configure PrintNode and agency printers

PrintNode lets an action in Holidario send a guest information sheet to a document printer or a label to a sticker printer. The account, computers, drivers, and printers remain the responsibility of your agency.

The person configuring the integration needs access to its credentials. Staff printing during operations need only permissions for the source document or task and should not know the PrintNode key.

Before you start#

You need:

• the Agency plan with PrintNode available;
• read-print-node permission to view and update-print-node to configure;
• authorization for the team's PrintNode resource;
• a PrintNode account controlled by your agency;
• the PrintNode client installed and connected on every computer serving printers;
• installed drivers and a successful local test page;
• the account API key.

Give printers unambiguous names in PrintNode, such as location, floor, and type. Holidario displays those names when choosing a destination.

Connect the account#

1. Switch to the correct team.
2. Open Integrations > PrintNode.
3. If it shows Disconnected, open Edit.
4. Enter the complete API key and save.
5. Return to the integration and check that it shows Connected and the expected account.
6. Select Load Printers.

The key is stored encrypted. Do not copy a partial version or share it with staff who only print.

Assign printers#

Holidario keeps two independent destinations:

• Document printer: information sheets and regular documents, normally A4.
• Sticker printer: adhesive labels used in cleaning.

In the printer list:

On a phone, swipe the table horizontally to review the assignment and action columns; they are not removed from the mobile view.

1. locate the device by name and computer;
2. confirm that it is online;
3. open its actions;
4. select it as the document or sticker printer;
5. verify that it appears as Active in the relevant card.

You can use two different devices or the same one if the hardware and paper suit both formats. Changing an assignment affects the team's next prints, not only your user.

First controlled check#

1. Choose a document without real or sensitive data.
2. Confirm that the printer computer is on and its PrintNode client is connected.
3. Send one print only.
4. Wait for it to physically appear before repeating.
5. Check size, orientation, paper, and destination.

The integration screen does not provide a separate test-preview workflow. The check must be made from a controlled real flow.

Hand the workflow to operational staff#

The default Manager and Front desk roles do not include read-print-node or update-print-node. They do not need to open the integration or know its key: they print from a document or task they are already authorized to use.

• For front desk, provide Generate, save or print the guest information sheet.
• For cleaning, provide Print cleaning labels and export plans.

Tell them which physical printer to check and who administers the connection. A send confirmation does not prove there is paper, ink, or labels, or that the document was collected.

Know when it is ready#

The integration is ready when:

• the status shows Connected;
• the expected printers appear in the list and online;
• there is an active destination for every format you use;
• a controlled test leaves the correct device;
• operational staff know where to find and collect each print.

You do not need to configure a sticker printer if your agency does not use that workflow.

If printers do not appear#

1. Check that the connected account is correct.
2. On the computer, verify that the PrintNode client is open and signed in.
3. Print a local page to separate a physical problem from a remote one.
4. Refresh the list in Holidario.
5. If the API key changed, replace it and check the connection again.

Do not select a similarly named device without confirming its computer and location.

If a print fails or does not appear#

1. Record the time and requested document.
2. Check whether the screen reported success or an error.
3. Review computer connection, local queue, paper, consumables, and printer status.
4. Confirm that the active assignment did not change.
5. Repeat once only when you know the first job is no longer pending.

If a document prints twice, stop further retries and inspect the PrintNode and operating-system queues first.

Security and privacy#

• Guest sheets can contain operational or personal data: collect them immediately.
• Securely destroy spare or defective copies.
• Do not assign printers in public or uncontrolled shared areas.
• Remove old devices and computers from the PrintNode account.
• Do not send the API key to support; status and device names are enough.
• Review PrintNode pricing and terms directly with the provider.

What to send support#

Include the team, document type, printer name, computer, time and time zone, visible status, and exact error text. Do not attach a real guest sheet if an anonymized version can reproduce the issue.