Add an Event node and choose the events, for example "job held" and "job timeout".
MONITORING / EVENTS / NOTIFICATIONS
Know When a Label Printer Stops, Before the Line Does
Get an email or Slack message when a label printer runs out of ribbon or labels, jams, loses its connection mid-job, or a job fails or has not printed in time. No monitoring server.
FREE PLAN · NO CREDIT CARD · WINDOWS / MAC / LINUX / WEB
THE PROBLEM
A label printer that stops is quiet. The ribbon runs out at 14:10, and nobody notices until the dock asks where the pallet labels are at 14:45. By then jobs have piled up and someone is reprinting the afternoon by hand.
LabelInn sees these moments as they happen, because it talks to the printer directly. An Event node turns them into an alert.
🔔 The printer tells you, not the dock. Email, Slack or Discord the moment a printer needs a person. Start free →
01 / ALERTS
Events you can alert on
| Event | When it fires |
|---|---|
| Job held | A job stopped because the printer needs a person: ribbon out, media out, head open, jam, over-temperature, paused at the panel, connection lost |
| Job resumed | The same job continues, so the alert can be closed |
| Job timeout | A job has not finished within the time you set on the Print node |
| Job failed | A job ended with an error |
| Supply low | Labels or ribbon fall below the threshold |
| Printer back online | A printer becomes ready again, for example to release a waiting batch |
02 / PRINTER MONITORING
Build the alert
Narrow it if you want. Filters match fields of the event, for example one printer, or only "ribbon out" faults.
Add a Notify node. Email, Slack, Discord or any incoming-webhook URL. The message can use fields from the event: "{{printer}} needs attention".
03 / EVENTS
Useful combinations
- Held → shift lead email; resumed → "all clear". Nobody is left with a stale alarm.
- Timeout → alert. "If it has not printed in 4 minutes, tell me" works even when nothing visibly failed.
- Failed → webhook to your ticketing system.
- Back online → print the batch that was waiting.
04 / NOTIFY
Good to know
- Channels: email, Slack, Discord and any webhook, including your ticketing or on-call system.
- Held is reported by the PC that drives the printer, because the fault is only visible between that PC and that printer. That PC needs to be running LabelInn.
- The same events can go to Zapier, Make or your own webhooks. See the fleet dashboard for the overview of every printer.
QUESTIONS / FAQ
Frequently asked questions
Can I get an alert when my label printer runs out of ribbon or labels?
Yes. When a job stops because of ribbon out, media out, an open head, a jam or similar, LabelInn emits a "job held" event that an Event node can turn into an email, Slack or Discord message.
Can I be alerted if a label has not printed after a few minutes?
Yes. Set a timeout on the Print node; if the job has not finished in time, a timeout event fires.
Which channels can alerts go to?
Email, Slack, Discord and any webhook URL, so alerts can also reach a ticketing or on-call system.
Do I need a separate monitoring server?
No. The events come from LabelInn itself, from the PCs that drive your printers.
KEEP GOING
Related
NEXT STEP / LABELINN
Hear about printer problems first
Add one Event node and one Notify node, and stop discovering printer problems at the dock. · Held, timeout, failure and supply events · Email, Slack, Discord, webhooks · All-clear when the job resumes