Notifications

Overview

Abbado sends notifications to a Discord webhook when agents finish, fail, or need your attention. This lets you step away from the dashboard while agents work and get alerted when something requires action.

Setup

Create a Discord webhook

In your Discord server:
- Go to Server Settings > Integrations > Webhooks
- Click New Webhook
- Choose a channel and copy the webhook URL

Configure in Abbado

Go to Settings in the Abbado dashboard, or use the API:

curl -X PUT http://localhost:3000/api/settings/notifications \
  -H "Content-Type: application/json" \
  -d '{
    "discord_webhook_url": "https://discord.com/api/webhooks/...",
    "notify_on_pipeline_complete": true,
    "notify_on_run_failed": true
  }'

Enable per-run notifications

Each run has a notification toggle. Click the bell icon on a run, or use the API:

curl -X POST http://localhost:3000/api/runs/<run-id>/notify \
  -H "Content-Type: application/json" \
  -d '{"notify": true}'

Notification Types

Session Idle

Trigger: Agent finished responding (Stop hook) and the run has notifications enabled.

Message: Includes the run ID and a summary of the last assistant message (first 200 characters).

Session Ended

Trigger: Session terminated (SessionEnd hook) and the run has notifications enabled.

Message: Run ID with completion confirmation.

Run Failed

Trigger: Agent encountered an error (StopFailure hook) or the adapter crashed.

Message: Run ID with the error reason (first 200 characters).

This notification is sent regardless of the per-run toggle — it uses the global notify_on_run_failed setting.

Needs Attention

Trigger: Agent is waiting for permission or is idle and needs user input (Notification hook with permission_prompt or idle_prompt type).

Message: Run ID with the notification message.

Settings

Setting	Default	Description
`discord_webhook_url`	`""`	Discord webhook URL. Empty = notifications disabled.
`notify_on_pipeline_complete`	`true`	Send notification when a pipeline/session completes
`notify_on_run_failed`	`true`	Send notification when a run fails

API

GET  /api/settings/notifications     # Get current config
PUT  /api/settings/notifications     # Update config
POST /api/runs/{id}/notify           # Toggle per-run notifications

Per-Run Toggle

Notifications are opt-in per run. When you create a session, notifications default to off. Toggle them on for long-running sessions where you want to be alerted.

The toggle affects:

Session idle notifications (Stop hook)
Session ended notifications (SessionEnd hook)

It does NOT affect:

Run failed notifications (always sent if notify_on_run_failed is true)
Needs attention notifications (always sent for permission/idle prompts)