Skip to main content

Notifications

Printago can send real-time notifications about your print farm to a variety of channels. Get instant updates about print completions, errors, and other important events without staying glued to the screen.

Supported Channels​

Notifications can be delivered through:

  • Discord via an Incoming Webhook
  • Slack via an Incoming Webhook
  • Telegram via a Telegram Bot
  • Pushover via your Pushover account and app
  • Webhook to any custom HTTPS endpoint (commercial accounts only)

Each channel is configured independently. You can enable any combination of channels and choose which events to receive on each.

Supported Events​

When you enable a channel, you select which events trigger a notification. The same event set is available on every channel.

Print job events

  • Job started
  • Job succeeded
  • Job failed
  • Job cancelled

Printer events

  • Printer online
  • Printer offline
  • Printer HMS error
  • Printer HMS warning
  • AI failure detected
  • Continuous print disabled

Order events

  • Order created (manual)
  • Order created (retail)
  • Order cancelled
  • Order closed
  • Orders auto-printed

Maintenance events

  • Maintenance mode on
  • Maintenance mode off
  • Maintenance due soon
  • Maintenance overdue

Material usage events

  • Material usage recorded

Discord Notifications​

Printago can post events into a Discord channel through Discord's built-in Incoming Webhooks.

discord header

1. Create a Discord Webhook​

  1. Open Discord and navigate to the server where you want notifications.
  2. Right-click the channel and select Edit Channel or click the ⚙️ icon.
  3. Click Integrations in the left sidebar.
  4. Click Create Webhook.
  5. Give your webhook a name (e.g. "Printago Notifications").
  6. Copy the webhook URL, you'll need this for Printago.
discord 1
caution

Keep your webhook URL private. Anyone with this URL can post messages to your channel.

2. Configure Printago​

  1. In Printago, go to Settings > Notifications tab.
  2. Choose the Discord channel.
  3. Paste your webhook URL.
  4. Click Enable.
  5. Select which events you want notifications for.

Route Categories to Different Channels​

By default, every Discord notification goes to the one webhook you configured. If you want, say, maintenance reminders in a quiet channel and printer errors in a channel your whole team watches, give a category its own webhook.

Channel routing settings showing the Printers category sending to its own webhook while other categories use the default
  1. On the Discord tab, find the Channel Routing section (visible once Discord is enabled).
  2. For the category you want to move (Print Jobs, Printers, Orders, Maintenance, or Material Usage), turn on Send to a different channel.
  3. Create a webhook in the target Discord channel (same steps as above), paste its URL, and click Save webhook.
  4. Click Send test message to confirm the messages land in the right channel.

Categories without their own webhook keep using the default one, and the section says so explicitly. You can pause an override with the Override active toggle (notifications fall back to the default channel), or turn off Send to a different channel to remove it entirely, which asks you to confirm because it deletes the saved webhook URL. Removing or pausing an override never stops notifications, it just changes where they go.

Disabling Discord removes every category override along with the default webhook, so if you turn Discord back on later you start from a clean slate and paste the webhooks you want.

Ping People with @mentions​

A notification that scrolls past unnoticed is easy to miss. You can make specific events ping people: @everyone, @here, a specific user, or a role, and you can add several mentions to the same event (for example, one per technician on "Maintenance task pending").

Mention settings showing an @everyone rule on HMS warnings and a user mention on maintenance reminders
  1. On the Discord tab, find the Mentions section.
  2. Pick the event and the mention type.
  3. For a user or role mention, Discord needs the numeric ID, not the username. Typing @yourname in a message would not ping anyone. To copy an ID: in Discord, enable Settings > Advanced > Developer Mode, then right-click the user or role and choose Copy ID. The name field next to it is only a label so you can tell the rules apart later.
  4. Click Add mention.
note

@everyone and @here only ping if the Discord channel the webhook posts to allows them. If your server restricts them, the message still posts but nobody is pinged.

Slack Notifications​

Printago can post events into a Slack channel through Slack's Incoming Webhooks.

1. Create a Slack App and Incoming Webhook​

  1. Go to Create your Slack app and create a new app.
  2. Choose From scratch, give your app a name (e.g. "Printago Notifications"), and select the workspace where you want to receive notifications.
  3. In your app settings, navigate to Incoming Webhooks in the left sidebar and toggle Activate Incoming Webhooks to on.
  4. Click Add New Webhook to Workspace, choose the channel where you want to receive notifications, and click Allow.
  5. Copy the generated Webhook URL. It will look like https://hooks.slack.com/services/T00000000/B00000000/XXXX....
caution

Keep your Slack webhook URL secret. Anyone with this URL can post messages to your Slack channel.

2. Configure Printago​

  1. In Printago, go to Settings > Notifications tab.
  2. Choose the Slack channel.
  3. Paste your webhook URL.
  4. Click Enable.
  5. Select which events you want notifications for.

Telegram Notifications​

Printago sends events to Telegram through a bot you create with BotFather. The bot can deliver messages to a direct chat with you, a group, or a channel.

1. Create a Telegram Bot​

  1. Open Telegram and search for @BotFather, the official bot for creating and managing bots.
  2. Start a chat with BotFather and send the command /newbot.
  3. Follow the prompts to choose a name (e.g. "Printago Notifications") and a username for your bot. The username must end in bot (e.g. printago_notify_bot).
  4. BotFather will give you a bot token that looks like 123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11. Copy and save this token.

2. Find Your Chat ID​

For a direct message to yourself:

  1. Start a chat with your bot by searching for its username.
  2. Send any message to your bot.
  3. Visit https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdates.
  4. Look for the chat.id value in the response (it will be a number).

For a channel or group:

  1. Add your bot to the channel or group as an administrator.
  2. For public channels, you can use the @username format (e.g. @mychannel).
  3. For private groups or channels, send a message and check the getUpdates URL above.
  4. Group and channel IDs typically start with -100.

3. Configure Printago​

  1. In Printago, go to Settings > Notifications tab.
  2. Choose the Telegram channel.
  3. Enter both the Bot Token and Chat ID.
  4. Click Enable.
  5. Select which events you want notifications for.
caution

Keep your bot token secret. Anyone with this token can control your bot. For channels, make sure your bot has permission to post messages.

Pushover Notifications​

Printago can send mobile push notifications through Pushover, a paid notification service with apps for iOS, Android, and desktop.

1. Set Up Pushover​

  1. Go to Pushover.net and create an account if you don't have one.
  2. Download the Pushover app on your mobile devices from the Pushover clients page. There is a one-time purchase fee per platform.
  3. Go to Create New Application and fill in:
    • Name: "Printago" (or your preferred name)
    • Description: "Notifications from Printago" (optional)
    • URL: Leave blank (optional)
    • Icon: Optional. You can download the Printago logo or use your own.
  4. After creating the application, copy the API Token/Key (a 30-character string like azGDORePK8gMaC0QOYAMyEEuzJnyUi).
  5. Return to your Pushover dashboard and copy your User Key (another 30-character string like uQiRzpo4DXghDmr9QzzfQu27cmVRsG).

2. Configure Printago​

  1. In Printago, go to Settings > Notifications tab.
  2. Choose the Pushover channel.
  3. Paste the App Token and User Key into the fields.
  4. Optionally configure:
    • Device: Leave empty to send to all your devices, or specify a device name.
    • Priority: Set notification importance. Emergency requires acknowledgment.
    • Sound: Choose a notification sound.
  5. Click Enable.
  6. Select which events you want notifications for.

Webhook Notifications​

For advanced integrations, Printago supports custom webhook notifications that can send events to any HTTPS endpoint. Since webhook notifications require an API key, this feature is restricted to commercial accounts.

Setup Steps​

  1. Set up an HTTPS endpoint on your server that can receive webhook notifications.
  2. Configure your endpoint to accept POST requests.
  3. Your endpoint should validate the X-API-Key header to ensure the request is from Printago. This key is a secret value that should be kept confidential.
  4. In Printago, go to Settings > Notifications tab, choose the Webhook channel, enter your HTTPS endpoint URL, and click Enable to start receiving notifications.

Webhook Payload Format​

When an event occurs, Printago will send a request to your webhook with the following:

  • HTTP header: X-API-Key with the value you configured
  • JSON payload with event details in the request body

Endpoint Requirements​

Your endpoint must:

  • Accept POST requests over HTTPS (HTTP is rejected at configuration time)
  • Validate the X-API-Key header against the key you configured in Printago
  • Respond with any 2xx status code (200, 201, 202, 204, etc.) to acknowledge receipt
  • Respond promptly so the request does not time out

Any response status outside the 2xx range, along with connection failures, DNS errors, and timeouts, is treated as a delivery failure.

Delivery Failures and Auto-Disable​

Printago does not retry failed deliveries. Each event is sent once. If your endpoint is unreachable or returns a non-2xx response when an event fires, that event is lost. There is no replay or backfill mechanism.

To protect endpoints that are misconfigured or offline, Printago tracks failures on a rolling 24-hour window. If a webhook accumulates 10 or more failed deliveries within 24 hours, the integration is automatically disabled. No further events will be sent until you re-enable it.

When you re-enable a previously disabled webhook, the failure counter is cleared.

Common causes of failures we have seen:

  • Endpoint returning 401 Unauthorized because the X-API-Key value on the server does not match the key stored in Printago (often after a key rotation on one side only)
  • Endpoint returning 404 because the receiving workflow or route is not deployed or activated
  • A reverse proxy, CDN, or WAF stripping the X-API-Key header before it reaches your application
  • Endpoint timing out under load

Verifying Your Endpoint​

Before relying on webhooks in production, confirm:

  1. A test event reaches your server (check your access logs for an inbound POST to your configured URL).
  2. Your server returns a 2xx status.
  3. The X-API-Key header arrives intact and matches the key stored in Printago.

If a single delivery succeeds, no failures carry over from a previous disabled state.

API Key Security​

The API key is automatically generated for you, but you can customize it if needed. Remember to:

  • Keep your API key confidential and secure
  • You can change it at any time, but ensure any new key remains sufficiently strong (at least 32 characters)
  • Update your webhook receiver if you change the key

Need help with Notifications? Join our Discord community or reach us at support@printago.io