Slack, Teams, and browser notifications
Open Notifications in the dashboard to choose what you hear about and where:- Notifications in Mobilerun lists the moments you can be notified about. Use the quick presets to switch whole groups on or off.
- Browser notifications show a system notification even when Mobilerun is in the background. Your browser asks for permission the first time; on a phone, Mobilerun has to be added to your home screen and opened from there.
- Notifications in Slack or Teams sends the same moments to a channel. Pick the channel and what you want to hear about; you can change it later on the Notifications page. Questions your agent asks can also be answered from Slack.
Webhook events
Three webhook events cover the whole lifecycle of an agent turn. They fire for every conversation in your organization, whether the tab is open, in the background, or closed.Option A: let your agent set it up
Your agent can configure its own notifications. Start a conversation and say, in your own words:Notify me at https://hooks.example.com/mobilerun when you finish, fail, or need something from me. Use sensible settings and send a test.Your agent will:
- show you which notification events exist and confirm the selection,
- create the webhook endpoint for that URL, filtered to exactly those events,
- show you the signing secret once and ask you to store it,
- send a test delivery and confirm it arrived.
Your agent creates generic signed webhooks. It does not send email or Slack messages itself; for Slack or Teams, use the Notifications page above. Point a webhook at an automation tool (n8n, Zapier, Make) or your own receiver to turn the event into any other message. A routine’s Notify on success and Notify on failure controls live in the routine’s Notifications dialog.
Option B: set it up yourself
- Open Webhooks in the dashboard and click New webhook.
- Enter your HTTPS URL.
- Select
chat.turn.completed,chat.turn.failed, andchat.input.required. - Save and store the secret shown once.
- Click Send test event and check that your receiver logged a
webhook.testevent.
What the payload contains
The payloads are deliberately minimal. They identify the conversation and the turn, but never include your prompt, your agent’s reply, or the text of a question. Open the conversation to read those.chat.turn.completed and chat.turn.failed
You get exactly one terminal event per turn. No terminal event is sent when you stop the turn yourself, or when the turn belongs to a routine rather than an interactive conversation; those cases are visible in the chat only. A turn that stops because you ran out of credits does send
chat.turn.failed.
chat.input.required
The event is sent once per question. If you answer within the first seconds, before the event has been dispatched, it may be skipped.
Turning it into a message
Slack or Teams
Use the Notifications page, no webhook needed. For custom messages, use n8n’s Webhook trigger, then a Slack node that posts
type, settleReason, and a link built from sessionId.Email via Zapier or Make
Catch Hook → Email. Use one Zap per event type or branch on
type.Push notification
Forward to a service such as ntfy or Pushover from your receiver.
Your own receiver
Verify the signature, deduplicate on
id, and act on type.