Skip to main content
Version: 2026.8.0

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. Out of the box, notifications show up in Cobblr itself, so there's nothing to set up to start getting them.

Send it somewhere else​

To hear about things where you already are, add a channel under Me → Notification channels. Channels are set up per workspace, so two workspaces can send to different places:

  • Discord or Slack: create an incoming webhook in the server or workspace and paste the URL.
  • Email: bring your own delivery. Point it at SMTP (Gmail with an app password, Fastmail, and the like) or a transactional provider (Mailgun, Resend, or Postmark) with an API key. Cobblr does not host an outbound mail server.
  • SMS: send through your own Twilio account.
  • Generic webhook: Cobblr POSTs a small JSON envelope to a URL you own, for anything you'd rather wire up yourself.

Then:

  • Send test on each channel exercises the real config.
  • Secrets are stored encrypted and shown as <set> after you paste them.
note

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

Choosing what you hear about​

Each channel carries the notifications you point at it:

  • A specific event type, or all of them.
  • A minimum priority, so urgent things go to SMS while routine notifications go to email or stay in the app.

Nothing leaves your box unless you add a channel that sends it somewhere.

What counts as an event​

Modules announce what happens to their records as events, named module.thing.verb: inventory.part.created, purchases.order.arrived, digifab.print.failure_suspected. Wires can fire on any of them.

Which events reach you as notifications today

Notifications reach you for the events a module maps to a notification, a smaller set today. The one wired up out of the box is a task becoming unblocked when the stock it was waiting on arrives, and more get mapped as modules add them. A few account-level events, like a member offering to share their AI with a workspace you own, also email you so they don't slip past.