Notification Channels

Notification channels deliver alerts about events in your Devpilot workspace. Channels live in workspace settings, are scoped to either deployments or scripts, and can be attached to the specific apps or scripts you want alerts for.

Supported Channels

Devpilot supports four channel types:

Channel Scope

Every channel has a scope that determines where it can be attached:

• Deployment — attachable to apps so you get alerts about deployment activity for that app.
• Script — attachable to individual server scripts so you get alerts when the script runs.

You choose the scope when you create the channel. A channel configured for deployments cannot be attached to scripts and vice versa.

Events That Fire Notifications

Deployment-Scope Channels

Alerts fire on deployment lifecycle events for apps the channel is attached to:

• Deployment started, succeeded, failed, or cancelled
• Auto-deploy triggered by a source control webhook

Script-Scope Channels

Alerts fire when a script the channel is attached to executes:

• Script execution started, succeeded, or failed

You can control whether each channel delivers on every event, only on failures, or never (a way to mute a channel without deleting it).

Setting Up Notification Channels

Navigate to Workspace Settings > Integrations > Notification Channels to add and manage channels.

{
  "event": "deployment.succeeded",
  "timestamp": "2026-04-18T14:30:00Z",
  "data": {
    "title": "Deployment succeeded",
    "status": "completed",
    "fields": [
      { "name": "App", "value": "production-api", "inline": true },
      { "name": "Server", "value": "api-server-01", "inline": true }
    ]
  }
}

Controlling When a Channel Fires

Each attached channel has a notify on setting:

• Always — deliver on every matching event (default)
• Failure — deliver only when the event status is failed
• Never — suppress the channel without deleting it (useful for maintenance windows)

Managing Notification Channels

Editing a Channel

Open the channel in Notification Channels and change the name, webhook URL, recipient email, or scope. Save to apply the change; all apps and scripts the channel is attached to immediately use the new configuration.

Disabling a Channel

Switch the channel's status to Inactive. Devpilot skips the channel on every event, but configuration is preserved so you can re-enable it later.

Deleting a Channel

Deleting a channel removes it from every app and script it was attached to. This action cannot be undone.

Best Practices

• Use chat for the team, email for individuals. A shared Slack or Discord channel keeps the whole team in the loop; email is best for owners who need a personal record.
• Use failure-only channels for paging. Create a webhook channel that delivers only on failure and point it at your on-call tool (PagerDuty, Opsgenie) to avoid paging on successful runs.
• Name channels by purpose. Names like prod-deploys-slack or cron-failures-ops-email make it obvious what each channel does when you look at the list.
• Test with a real event. After creating a channel, trigger a small deployment or run a harmless script to confirm messages land correctly.