Global Action: Send Print Job To Print Node
This Action allows you to send remote print jobs to any printer connected through the PrintNode service. Use it to automatically print shipping labels, packing slips, receipts, or other content directly from a workflow.
Before using this Action, you must configure the PrintNode integration. For detailed setup instructions, see the PrintNode Integration article.
Configuring the Action
Once the integration is connected, you can add the “Send Print Job to PrintNode” Action to your Workflow. The available fields let you define which printer to use, what content to print, and how the print job should be labeled.
| Field Name | Description | Example |
|---|---|---|
| Computer | Select which computer to send the print job to. This list is populated from your connected PrintNode devices. | Office-PC |
| Printer | Select the printer connected to the selected computer. | HP LaserJet 1020 |
| Job Title | A label that appears in your PrintNode job history. Supports tokens. | {{ order.name }} Shipping Label |
| Content Type | Select the type of content you want to print. | Text, PDF URL, File URL |
| PDF URL | The URI of the PDF you want to print. Required if using pdf_uri. |
{{ shipping_label_url }} |
| File URL | URI of a raw print file (e.g., .txt or custom format). Required if using raw_uri. |
{{ file_url }} |
| Text | Text content to print including any token values. | Order {{ order.name }} – Print this text. |
Example Configuration
This setup prints a PDF shipping label to a specific printer when an order is fulfilled:
| Field | Value |
|---|---|
| Computer | Shipping-Station |
| Printer | Brother QL-800 |
| Job Title | {{ order.name }} Shipping Label |
| Content Type | pdf_uri |
| PDF URL | {{ order.shipping_label_url }} |
Troubleshooting & Usage Tips
Test Connection fails with valid API key: The test button uses the saved API key, not the current form input. Always click Save before testing the connection.
Printer list is empty: Ensure that the PrintNode client is running and logged in on the computer you wish to print from.
Job fails but no error is shown: PrintNode may accept the job but fail during actual printing. Check PrintNode job history or enable webhooks to monitor job success.
Base64 content too large: PrintNode has a 50MB request body limit. If your raw content exceeds this, use a URL (pdf_uri or raw_uri) instead.
Missing required content: The action requires exactly one content type field to be filled in. Make sure you've selected a content type and provided the corresponding value.
Credit Cost
Send Print Job to PrintNode incurs a cost of one Action Credit on Lite plans and is unlimited on Unlimited plans.
Custom Actions
This action is also available in custom workflows as printnode_print_job. You can use it programmatically with full token support and advanced debugging.
Use the following debug tokens in test workflows:
{{ printnode.debug.computers }}– Outputs a list of available computers.{{ printnode.debug.printers }}– Outputs a list of available printers.
These debug outputs are useful for verifying device availability before triggering a print job.