Skip to content
SubClik

Webhooks: messages in Slack, Teams, Google Chat, Zapier or Make

Send a message to a chat channel or an automation tool when a printer has a problem, a job is logged or completed, or an invoice is issued or paid.

Where: Administration › Integrations › Chat & automationFor Owners, admins

Step by step

  1. Get an incoming webhook address from your chat or automation tool (see the guides for Slack, Teams, Google Chat and Zapier/Make).
  2. In SubClik open Administration › Integrations and paste it into Address (https).
  3. Tick the events you want under Printer problems and Jobs and invoices.
  4. Press Add webhook. You see "Webhook added. Events are sent within a minute." and the Signing secret (shown only now).
  5. Press Send a test next to the new webhook: "Test message queued: it arrives within a minute."

The events

Printer problems: Paper jams, Service calls / error codes, Printer stopped (in error / offline), Toner low / empty, Waste toner box, Drum / imaging unit, Memory errors (these are ticked to start with), Doors / covers open, Paper & trays, Output tray full, Maintenance kits and Other alerts.

Jobs and invoices: New job logged, Job completed, Invoice issued, Invoice paid in full. (Not on the printer monitoring plan.)

Where to get the address

Slack: api.slack.com/apps › Create New App › From scratch › Incoming Webhooks › On › Add New Webhook to Workspace › choose the channel › copy the Webhook URL.

Microsoft Teams: in the channel › ⋯ › Workflows › Send webhook alerts to a channel › Add workflow › copy the address.

Google Chat: the space › its name › Apps & integrations › Webhooks › Add webhooks › Save › copy the address.

Zapier: trigger Webhooks by Zapier › Catch Hook. Make: Webhooks › Custom webhook › Add. Copy the address.

Rules

At most 5 webhooks per firm. The address must start with https:// and be on the internet: "the webhook address must start with https://".

A message counts as delivered only when the receiving service answers OK. If it answers with an error, is busy (429) or does not answer, SubClik tries again after 1, 2, 4 … up to 60 minutes, at most 8 times within 2 days. An address that does not exist (for example 404) is not tried again.

The list shows each address, its events, when a message was last delivered and, for the last 7 days, how many were delivered, are waiting or were not delivered (with the reason). Send failed again queues the ones that were not delivered. Remove deletes a webhook.

For developers

The body is JSON with event (printer.problem, job.created, job.completed, invoice.issued, invoice.paid or test), the printer, job or invoice details and a ready-made text.

The header X-SubClik-Signature: sha256=<hex> is the HMAC-SHA256 of the body with your signing secret.

X-SubClik-Delivery is the same on every retry of one message: use it to ignore a message you already processed. X-SubClik-Attempt is the try number. Answer with any 2xx status within 8 seconds.

Ideas to try

  • A #breakdowns channel in Slack for jams and error codes, so the whole team sees them.
  • A Zap that adds every paid invoice to a Google Sheet.
  • A Teams message to the boss when a big job is completed.

Questions

I lost the signing secret.

It is shown only once. Remove the webhook and add it again to get a new one. Slack, Teams and Google Chat don't need it.

Nothing arrives in Slack.

Press Send a test. If the test does not arrive within a few minutes, check the address in Slack and add the webhook again.

Works together with