Notifications
In-app notifications keep you informed about workflow runs, reviews, and invitations. Optionally receive an email whenever a new notification arrives — controlled by a single switch in your personal settings.
The platform raises in-app notifications for events such as completed or failed workflow runs, human-in-the-loop review requests, and team invitations. Unread notifications surface on the bell in the sidebar and in Settings → Account → Notifications.
Email notifications
You can also receive an email each time you get a new notification, so you stay informed when you are away from the app.
Email notifications are on by default. You will receive an email for every new in-app notification until you turn the setting off.
Turning email notifications on or off
Open Settings → Account → Preferences.
Toggle Email me about new notifications. The change takes effect immediately and applies across every organisation you belong to.
When the switch is off, you keep receiving in-app notifications on the bell — only the emails stop.
The email is sent through your organisation's configured email provider. If your workspace has not finished email setup, in-app notifications still work, but no email is delivered.
Process Flow notifications
Process Flows raise four kinds of notification. Each arrives in the in-app inbox and by email, and opens the task (or flow) in Horizon through its Open button. A link that still points at Agentic's old flow pages forwards to Horizon.
| Type | When | Who |
|---|---|---|
process.instance_created | A flow instance started — by an operator, a webhook or a schedule. One per person, listing the first-stage tasks waiting on them. | Everyone cast in the instance, and anyone a first-stage task is assigned to by name. When nobody can be reached, the organization's administrators, so they can assign the personas. |
process.task_assigned | A task became open later and waits on someone: it was unlocked, moved into a stage, added, or assigned. First-stage tasks are listed in process.instance_created instead. | The task's assignee, or everyone holding the persona it is assigned to on that instance. A persona holder is not paged again when somebody else is added to the cast. |
process.task_sla_breached | An open task passed its due date (dueOffsetDays or due on the task template). Checked hourly; a due date that moves is a new deadline and notifies again. | The task's assignees; failing that the instance's cast, then the organization's administrators. |
process.approval_requested | A stage gate needs approval. | The approver persona's members, falling back to the organization's administrators (a staffing notice only; they cannot approve until assigned). |
Each notification is raised once per person per event: a task that is re-read, re-swept or activated a second time does not notify again, and a task handed to someone new notifies them once. Overdue notices are also written to the flow's activity log.
Who is cast in a new instance? A new instance copies the persona assignments of the most recent instance of the same flow in the same environment, so a recurring flow started by a webhook lands with last time's cast. A persona still empty after that is staffed from the organization-chart functional role the template declares for it, if any (see Staffing a persona from the organization chart). A persona nobody could staff stays empty until someone assigns it, and the organization's administrators are told.
Data source notifications
Data sources in Analytics raise these in-app notifications. Each opens Data sources in Analytics.
| Type | When | Who |
|---|---|---|
data_source.state_changed | A data source started failing, runs late for its own schedule, was paused (after failing repeatedly, or because the person it runs as lost access), or recovered — with the reason and who fixes it. Raised once per change; a source that keeps flapping alerts at most once every six hours, and the rest goes into the digest. See Alerts and the daily digest. | The organization's administrators, and the person who added the data source while still a member. |
data_source.daily_digest | Once a day, what changed for the data sources that did not need an alert, one paragraph per source. At most one a day; none when nothing changed. | Administrators, for every data source; the person who added a data source, for theirs. |
data_source.copy_paused | A database source's copy was paused after failing as many runs in a row as the auto-pause threshold; live queries keep working. | The organization's administrators. |
A data source added with its alerts turned off raises neither of the first two.
Attachments from Process Flows
A Process Flow distribution can include artifacts selected by the pack author from earlier document, workflow-output, or file-upload tasks. Each in-app notification shows those files as authorized attachment links. If email delivery is enabled, the same files arrive as real MIME attachments — generated output as UTF-8 Markdown and uploads with their original bytes and MIME type.
The platform resolves and validates the complete attachment set before notifying anyone. A distribution can carry at most ten files, with an 8 MiB limit per file and 8 MiB total. Recipients receive the complete set or no attachment delivery; the platform never silently drops an unsupported, missing, or oversized file.
Attachment links are not public file URLs. Opening one verifies that you were an eligible recipient, that you can still access the Process Flow, and that the source still matches the version sent. If a source is deleted or changed after dispatch, the notification does not serve different content under the old link.
Turning email notifications off affects only the email copy. The in-app notification and its authorized attachment links remain available.