Notifications
Two different things share the word “notification”: being told when something happens, and a workflow sending a message as part of what it does. This page covers both.
Being told when something happens
Section titled “Being told when something happens”The product notifies you about events like these:
| Event | When |
|---|---|
| Workflow finished | A run you started completed |
| Workflow failed | A run ended in error |
| Someone joined your workspace | An invite was used — goes to the owner, because it changes the seat count |
| Something was shared with you | A teammate gave you access to a list |
| A strategy stopped looking safe | Decay monitoring changed its status |
| A test suite got worse | A scheduled evaluation scored below its previous run |
The full list, and which of them are delivered today, is in the notification events reference.
Choose your channels in your profile’s notification preferences. They are per person, not per workspace: sharing a workspace with someone does not mean you both get the same notifications. Email is the default.
If a workspace’s subscription has lapsed, notifications for it stop. They resume when there is an active plan again.
Sending messages from a workflow
Section titled “Sending messages from a workflow”If your organisation has messaging enabled, a workflow can send email, SMS or a Slack message as one of its steps. There are two ways to do it, and the difference is who decides the details.
You decide, up front. Add a tool step with the recipient and content fixed. Nothing pauses to confirm, because you already specified everything by building it that way:
send_emailsend_sms— the number must be in full international form, like+15551234567send_slack_message— use the channel id, and invite the bot to that channel first
The assistant decides, from context. Add the messaging capability and describe what you want. It composes the message and picks the channel from your request. In chat, a clear instruction with a recipient — “text +1555… that the report is ready” — is treated as consent and sends immediately. Anything vaguer gets one summary to confirm first, and answering it sends. That confirmation survives across turns, so you can answer it a message or two later.
If you need a guaranteed pause before every send, mark the step to clarify first. A model’s final text asking “shall I send?” does not pause anything on its own — nothing stops on a question, so make the pause explicit.
When a send does not arrive
Section titled “When a send does not arrive”- Slack: “channel not found”. The bot is not in that channel, or the id is wrong. Invite the bot and use the channel id rather than its name.
- SMS rejected. The number is not in international format, or your provider is on a trial that only sends to verified numbers.
- The messaging tools are not in the palette. Your organisation has not enabled messaging. Everything else on this page will be unavailable too.
- A step completed but nothing sent, and the reply is a question. The assistant asked instead of sending. Use a step that clarifies first if the pause needs to be mandatory.
What it costs
Section titled “What it costs”Every successful send is metered as one third-party API call, tagged with the provider. Failed sends are not counted. You can see the volumes in your usage — see Usage and billing and the billing units reference.