Skip to main content

Notifications

Cobblr can let you know when something happens: an order arrived, a print finished, a part dropped below its reorder point. Where you hear about it is up to you.

In the app​

Out of the box, notifications show up in Cobblr itself, so there's nothing to set up to start getting them.

note

Browser push, for reaching you when the app is closed, is architected but not wired up yet; today the channels below cover that.

Discord and Slack​

To get notified where you already are, point Cobblr at a Discord or Slack incoming webhook:

  1. Create an incoming webhook in your Discord server or Slack workspace. Both give you a URL to post to.
  2. Paste that URL into the matching channel in Cobblr.
  3. Pick which events go there.

From then on, the events you chose post into that channel. A plain webhook is also supported for anything you'd rather wire up yourself, so a self-hosted install can feed its own scripts or another tool.

Choosing what you hear about​

Notifications are per event, so you decide which events reach which channel. Send order arrivals to Discord, keep the noisier stuff in the app, whatever fits how you work. Nothing leaves your box unless you set up a channel that sends it somewhere.

What counts as an event​

Every module announces what happens to its records as events, named module.thing.verb: inventory.part.created, purchases.order.arrived, digifab.print.failure_suspected. Anything a module announces can feed a notification channel, and the same events are what wires fire on, so if you can be notified about it, you can also automate on it.