Notifications
Getting told the things that need you — in your team's channels, in the app, and on your phone.
Peractor tells people about the moments that need a human, and stays quiet otherwise. A phase succeeding is not news; a run waiting on you is.
What Peractor tells you about
| Kind | When |
|---|---|
| Gate | A run parked for your review. |
| Question | An agent asked you something. |
| Interactive | A step is waiting for you to talk to it and end it. |
| Completed · Failed | A run settled. |
| Reviewed | Somebody else approved a run you started, or asked for changes on it. |
| Stopped | Somebody else canceled a run you started. |
| Assigned | Somebody put a task on you. |
| Mentioned | Somebody named you in a comment. |
| Commented | A task you follow has a new comment. |
| Joined | Somebody accepted an invitation to your organization. Sent to the people with Manage members. |
| Monitor | A URL a monitor watches went down or came back. Sent to the people the monitor names and everyone holding a role it names, or else to whoever made it. |
| Memory | An agent or a member proposed a memory entry. Sent to the people who decide there: Manage workflows in the project whose memory it is. |
| Ownership | The owner offered to hand the organization to you. Accept or decline it in Members. |
| Access request | Somebody asked to be let in to something you look after. Sent to the people with Manage access there who could give what was asked; it opens the project's Access page at the request, to grant or decline. |
| Access | Somebody let you in to something you asked to open. It opens the link you asked about. |
| Invite | You were invited to an organization. The one you cannot switch off — until you accept it, you have no other way to find it. |
| Chat | A direct message, a mention, a reply in a thread you follow and — off until you turn it on — a reaction to your message, in Chat. These ring your phone and fill Chat's own Activity, and never reach the Inbox. |
Each kind is a switch in your own notification settings, per organization, grouped as Runs, Tasks, Organization and Chat: Settings → Notifications on the phones and the dashboard, and the This Mac pane on the Mac. A kind added in a later release starts switched on. There is an Inbox in the apps with an unread badge, so nothing depends on a push getting through.
A run's moments reach whoever started it and the people with
Manage runs in its project, who can act on anybody's run there.
A parked gate whose approver rules name people of your organization —
through a role: or a member: rule — reaches
those people instead. Reviewed and Stopped go to the
run's starter alone.
Nobody is told about anything in a project they can't see, such as a private one they aren't let into, so their Inbox never names it — nor about a run that worked with restricted folders or files they can't open.
Your team's channels
Configure notifiers in Settings → Notifications; adding or changing one takes Manage connectors. Every configured one posts, together.
| Provider | Connects with | Notes |
|---|---|---|
| Slack | Add to Slack (OAuth) | One thread per run; images render inline. Pick a public channel, or invite the bot to a private one. |
| Discord | Add to Discord (OAuth) | Channel chosen on Discord's consent screen; coloured embeds. |
| Telegram | Bot token + chat id | Threaded replies per run, photo previews. |
| Microsoft Teams | Workflows webhook URL | Adaptive Cards with the linked issue and status colour. |
| Google Chat | Space webhook URL | Threaded per run. |
| Mattermost | Webhook URL and channel | The self-hosted favourite. |
| Webhook | Any URL | Posts structured JSON per milestone — build anything. |
Each has a Test button that posts a real message before you commit. Slack and Discord are OAuth only — one click installs the app, with no token form to fill.
You can configure more than one of the same provider — a general channel and a releases channel — and name them separately in a notify step.
What gets posted
Runs thread where the platform allows it: a "started" root message, then milestones as replies — ready for review, approved, changes requested with the note, done, failed, canceled — plus any published artifacts as inline images.
A run that worked with restricted folders or files posts none of what it did to a chat or a tracker issue, whose readers nobody can check: not its artifacts, a composed message, a reviewer's note or its question. Each of those posts its title, status and link instead, with "This run worked with files some people can't open.", and the run's own log says so once. Its pull request still gets its artifacts — anyone who can read the repository can read them there.
Your workflows can add their own messages at exact moments with a notify step, and that step can compose its message from what the run actually did rather than posting a fixed sentence.
Push on your phone
The iOS and Android apps get native push for the moments that need a human, and tapping one opens the page it is about — the run (on the gate, question or step it names), the task (on the comment), your invitations, your organization's members, a project's Access page (on the request), or the link you were let in to — signed in as the right account and moved to the right organization and project, even if you have several on the device. The Mac and the dashboard's bell land in the same places.
iOS asks for notification permission the first time a run actually waits on you, not at install. Self-hosters enable each platform independently.