Notifications
The notifications system keeps you informed about relevant events in real time.
The notification bell
There is a bell icon in the top-right corner of the screen. The number on it tells you how many unread notifications you have.
Click the bell to open the notifications panel.
Notification types
| Type | When it is generated | Who receives it |
|---|---|---|
| New task | A task is assigned to you, including when you claim it yourself | whoever received the task |
| Task delegated | Someone delegates a task to you | whoever received the delegation |
| Process error | An instance fails on an automated step | whoever started the instance |
| AI agent failure | An agent does not finish a step's analysis | whoever submitted the task |
| Robot failed or timed out | A robot execution ends badly | whoever triggered the execution |
| Message from an agent | An AI agent sends a notice during the process | the user the agent names |
There is no due-date notification in the bell
A due date raises nothing in the bell, neither when it approaches nor when it passes: the bell only reacts to something that happens — an assignment, a delegation, a failure. What does exist is the daily digest e-mail below, which separates overdue tasks from merely old ones once a day. The due date also shows on the list and on the task screen.
A completed process generates no notification either. An instance that finishes well fires a webhook, if one is registered for instance.completed — see Webhooks.
The daily digest e-mail
Once a day you get one e-mail with the work waiting for you — not one per task. A busy process alone would produce hundreds of messages a day; the digest makes the volume depend on the number of people, not the number of tasks.
If you belong to more than one company, it is still one message, with a section per company. Each section carries, in this order:
- Waiting the longest — oldest first, with how many days they have waited
- Overdue — what is past its due date, kept apart from what is merely old
- New in the last 24 hours
- That company's total
Every row links straight into the task. At most five rows per block: the total says the rest.
The digest is always your own work, whatever your role. A manager or an administrator sees the whole company on the Tasks screen, which is what that screen is for; the e-mail is not. It carries what is assigned to you, or a candidate for you and your groups — a "what is waiting for you" summary with the whole company inside it would be exactly the noise it exists to avoid.
On a day with nothing waiting, nothing is sent. A company with no tasks produces no section, and someone left with no sections gets no message — a daily message with nothing in it would lead you to ignore the ones that do have something.
The hour is the platform's (07:00 by default, adjustable by the Super Admin in the server configuration), not your own timezone. To stop receiving it, turn Receive the daily digest off in your profile.
The digest is not for urgency
A step that needs somebody within two hours is not served by an e-mail arriving tomorrow morning, and raising the frequency does not fix it — it only rebuilds the volume problem. For that, watch Instances or your task inbox.
Marking as read
- Click a notification to mark that one as read
- Use the Mark all as read button to clear them all at once
Real-time notifications
Flowi Agentic uses a real-time connection (WebSocket). New notifications appear on their own, with no need to reload the page, and the bell counter updates the moment something arrives.