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.

To hear about things somewhere other than the app:

1. Open Me → Notification channels.
2. Add a channel (Discord, Slack, email, SMS, or a webhook) and press send test.
3. Point events at it and set a minimum priority and a cadence under When things arrive.

In the app

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

• One that offers a choice shows it as buttons, in the bell and on the full notifications page: a workspace invite has Accept and Decline on the row, a service that is due has Mark done. Pressing one runs it there and the notification says what it did. The buttons follow your role, so a read-only guest sees the news without the button.
• Every notification goes somewhere. One about a single record opens that record, so a jar expiring in your Groceries table opens the jar rather than a list to search. One covering several things opens where they all are: several dated items open the calendar on that day, several unblocked tasks open the projects list.

note

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

Send it somewhere else

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.
• send test on each channel exercises the real config.
• Secrets you paste are stored encrypted and shown as <set> afterward.

Your own Discord DMs

Connect and verify Discord in your account settings and workspace notifications reach you as a direct message as well as in the bell. A parcel out for delivery, an order to confirm.

• This is separate from channels. The channels above are per workspace and go to a webhook you set up.
• Low-priority notices stay bell-only, so a DM is never used for something you would not have looked up anyway.
• Email is unaffected. It is still sent only where a workspace has explicitly subscribed you to it.
• A mention arrives as a card showing what was written, with a Reply button that posts your answer into the discussion without opening Cobblr. See Replying from Discord.
• When Cobblr moves to a new Discord app, your settings say so and offer one re-confirm (Reconnect Discord). Until then those notifications wait in the bell rather than going to a channel nobody is listening on.

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 you can send urgent things 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.

When things arrive

Under Notifications, the Delivery tab carries When things arrive: a cadence per channel, set once for you, not per workspace, so one daily message covers all of your workspaces.

Each channel has two cadences:

• Conversation: replies, mentions, things that just happened. Most people want these as they happen.
• Due today: things a date brought up. Food expiring, a service interval reached, something running low. These usually read better as one list in the morning.

Each is as it happens or once a day at a time you choose, in your own timezone. Due today can also be same as conversation, which is how delivery worked before the split existed.

• Being mentioned by name always interrupts, whatever the cadences say. So does anything a module marks high or urgent, like a delivery that needs putting away now.
• A waiting count next to each cadence tells you what is queued, so you can see what the next message will contain before it arrives.
• The bell is never delayed. In-app notifications and your history are unaffected. A cadence changes when a channel pushes to you, not what your workspace records.
• Notifications about a conversation carry the comment. The bell and the cross-workspace inbox show the comment you were mentioned in under the one-line summary, the same way a Discord DM does.

A common setup: Discord DM with conversation on as it happens and due today on once a day at 07:00. Chat still reaches you live, and the morning message tells you what expires today and what is due a service.

Email

• Email carries a once-a-day message and nothing else. Cobblr will not mail you per event.
• It starts arriving when you set one of its cadences to once a day, and that setting is the whole request. On as it happens it stays quiet, and the screen says so rather than letting you configure something that never sends.
• Turning email off under communication preferences still means off. A cadence says when, never whether.

Why cadences exist, and what a daily message looks like

By default every channel tells you about things as they happen. That is right for a bell you glance at and wrong for a channel that pushes into your attention, especially once you track enough things to hear from several a day. A mailbox with forty notifications in it is a mailbox nobody reads.

If several things happen before your time you get one message listing them, not one message each. A quiet day sends nothing at all, so an empty digest never arrives just to say nothing happened.

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.

• Notifications reach you for the events a module maps to a notification, a smaller set today.
• Wired up out of the box: a task becoming unblocked when the stock it was waiting on arrives. 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.