Notifications
Notifications are in-app messages in the header bell and on the Notifications page. They tell people something happened. They are not toasts, and they are not approval requests — they do not pause a run.
Opening a notification marks it read. The badge count is unread items only. Opening the bell popover does not mark everything read — use Mark all as read for that.
When to use
- Tell members a workflow finished, a record changed, or someone should open a resource
- Let an agent or workflow notify people without waiting for a reply
- Point recipients at a table, agent, or other workspace resource with a click
Use approval flow when a run must wait for a yes/no or submitted answers.
Open the inbox
Use the bell in the header for a short list, or open Notifications for the full inbox.
| Action | What happens |
|---|---|
| Open a notification | Marks it read |
| Mark all as read | Marks every unread item read (bell popover and Notifications page) |
| Click the rest of the row (web) | Marks it read and opens the linked resource when one is set |
| Click Created by {Name} (web) | Opens that agent or user |
| Tap a row (mobile) | Opens the linked table when the link is a table; other resource types stay on the list |
Native push for inbox items, approvals, and new messages opens the matching mobile page.
What a notification shows
| Field | Required | What it does |
|---|---|---|
| Message | Yes | Body in the inbox |
| Icon | No | Optional icon (default is the bell) |
| Linked resource | No | Resource opened when the recipient clicks the row on web (agent, user, workflow, table, role, knowledge base, connected service, chat profile). On mobile, a table link opens that table; other types stay on the notifications list |
| Created by | No | Attribution line. The name is a link (agent or user). Sends from a block or agent tool always set this to the running agent |
Send a notification
Use the Send Notification block in a workflow, or attach it as a block tool on an agent.
- Pick at least one workspace user and/or role.
- Write the message.
- Optionally set an icon, a linked resource, and extra data on the block.
The run continues as soon as the notification is sent. Recipients are resolved when it is sent: people who join a role later do not receive that notification.
When an agent uses the tool, the model fills recipients and message on each call.
Limits
- Recipients are workspace members and role holders only. You cannot send to the whole company from the block or agent tool.
- You must pick at least one user or role.
- Role membership is a snapshot at send time.
- Notifications do not wait for a reply and do not appear on Approvals.
Related
- Approval Flow — pause a run until a human decides
- Roles — target role holders when sending
- Workspace Users — who can receive workspace notifications
- Send Notification — block and agent tool
- Agents / Workflows — where you send from
- Companion app — Alerts tab and native push