Notifications
Run milestones where your team already looks — seven chat notifiers plus native push on the phones.
Peractor announces run milestones — started, parked for review, approved, changes requested, finished — in the channels your team already watches. Configure notifiers in Settings → Notifications; every configured one posts, together.
The notifiers
| Provider | Connects with | Notes |
|---|---|---|
| Slack | Add to Slack (OAuth) | One thread per run; images render inline. Pick a public channel
from the dropdown, or invite @Peractor to a private one. |
| Discord | Add to Discord (OAuth) | Channel chosen on Discord's consent screen; colored 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 color. |
| Google Chat | Space webhook URL | Threaded per run. |
| Mattermost | Webhook URL (+ channel) | The self-hosted favorite. |
| Webhook | Any URL | POSTs structured JSON per milestone — build anything. |
Each page has a Test button that posts a real message before you commit. Slack and Discord are OAuth-only — there's no token form to fill; one click installs the app.
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. Your workflows can add their own messages at exact moments with
the notify step.
Push on your phone
The iOS and Android apps get native push for the moments that need a
human: "Waiting for your review" when a run parks at a gate,
"The agent needs your input" when it asks a question, and
"Run finished / failed" at the end. Tapping opens the run.
iOS asks for notification permission the first time a run actually
waits on you — not at install. Self-hosters enable each platform with
the PERACTOR_APNS_* / PERACTOR_FCM_* host
variables.