Alerts

LangBot watches each Workspace for repeated failures. When a threshold is reached it opens an alert and notifies the Workspace owners and admins. Configure it in Settings → Alerts (owner or admin role).

On self-hosted and dedicated instances alerts are off by default: nothing is evaluated or sent until an admin turns on "Alerts on" in Settings. LangBot Cloud (cloud.langbot.app) Workspaces have alerts on by default and mail through the platform's own service. When the dashboard's Failed card already shows failures while alerts are off, the card shows an Enable alerts shortcut that opens the alert settings.

Rules

Thresholds and windows are adjustable within limits (at least 3 failures) so a single blip never pages anyone.

Each alert is sent when it opens, reminded after 6 h, 12 h and then every 24 h while it keeps failing, and once more when it recovers (optional). Emails never contain end-user conversations: only the rule, the affected name, failure counts and a redacted error summary.

Email channels

When both are available, pick one in Settings.

If no mail service is configured and no admin has signed in with a LangBot Account, the alert settings show a Sign in with LangBot Account prompt. It binds your local account to the LangBot Account with the same email and brings you back to the alert settings, ready to use the free official sender.

Configure your mail service

email:
    provider: smtp          # or resend
    from: 'LangBot <[email protected]>'
    smtp:
        host: smtp.example.com
        port: 587
        username: [email protected]
        password: ''        # inject with EMAIL__SMTP__PASSWORD
        starttls: true
        ssl: false

The same section sends member invitations. workspace.invitations.email from older releases is moved to email on startup, and WORKSPACE__INVITATIONS__EMAIL__* variables keep working.

Limits of the official LangBot Space sender

LangBot Space enforces these server-side to prevent abuse:

• The recipient is always the requesting LangBot Account's own address; an instance cannot choose another one.
• Space renders the email from a fixed template and strips links from error summaries.
• Free quota: 20 emails per day and 200 per month per account, 20 per day per Workspace, and 3 test emails per hour. Refused sends show as "Quota reached" in the delivery log.
• Turn it off in your LangBot Space profile under Email preferences → Instance Alerts.

Webhooks

Add a webhook under Settings → API, then select it in the alert settings. Selected webhooks receive:

{
  "uuid": "…",
  "event_type": "alert.fired",
  "data": {
    "workspace_uuid": "…",
    "workspace_name": "Default Workspace",
    "incidents": [
      {
        "rule": "pipeline_failures",
        "subject_name": "Default Pipeline",
        "state": "firing",
        "event_count": 5,
        "error_type": "PipelineError",
        "error_summary": "…",
        "opened_at": "2026-11-12T08:42:05"
      }
    ]
  }
}

event_type is alert.fired, alert.reminder, alert.resolved or alert.test. Use it to forward alerts to Slack, Feishu, DingTalk or WeCom groups.

Turning alerts on and off

• One Workspace: switch "Alerts on" in Settings, or disable individual rules. New self-hosted Workspaces start with alerts off and LangBot Cloud Workspaces with alerts on; a saved choice always wins.
• The whole instance: set alerts.enabled: false in config.yaml (or ALERTS__ENABLED=false).