Webhook alert notifications
This feature is in preview phase and is available in Dagster+ in limited early access. Functionality and APIs may change as we continue development. To get early access to this feature, reach out to your Dagster account team. For more information, see the API lifecycle stages documentation.
Dagster+ alerts can be configured to send HTTP requests to any endpoint when an alert is triggered, enabling deep integration with chat clients, task management tools, incident management software, or custom internal systems.
Configuration
Navigate to Deployment Settings > Alert Policies to configure a webhook.
- URL: The destination HTTPS endpoint of your service.
- Headers: Custom headers (e.g.,
Authorization,X-Api-Key). - Body: Use the built-in JSON Editor to construct your payload using the template tokens below.
We suggest storing secrets, such as API keys, as environment variables and including them in the webhook using template tokens.
Domain Whitelist (Early Access Limitation)
During the Early Access period, we are limiting outgoing webhooks to a whitelisted set of domains. Please let us know which domains you'd like to send webhooks to.
Example Webhook Configurations
Use these guides to get started using webhooks with these common services:
Token Reference
Dagster provides dynamic tokens that are replaced with actual event data at runtime. Token availability depends on the Event Type.
Globally Available Tokens
These tokens are available for every notification type.
| Token | Description | Example |
|---|---|---|
{{alert_summary}} | Recommended. One-line summary of the alert. | Job daily_etl failed |
{{alert_content}} | Recommended. Full alert details (errors, links). | Error: Step failed... |
{{deployment_name}} | Name of the Dagster deployment. | prod |
{{deployment_url}} | URL to the Dagster deployment. | https://dagster.cloud/... |
{{alert_policy_name}} | Name of the alert policy that triggered. | Critical Alerts |
{{alert_policy_id}} | Unique ID of the alert policy. | abc123-def456 |
{{alert_policy_description}} | Description of the alert policy. | Alerts when production jobs... |
{{notification_type}} | Type of notification event (e.g., JOB, TICK). | JOB |
{{is_sample}} | true if this is a test/sample notification. | false |
Environment Variable Tokens
You can access environment variables, such as {{env.WEBHOOK_API_KEY}}, to avoid hardcoding secrets. See Environment Variables for setup instructions.
Job & Run Tokens
Available for Job events (Success, Failure, Long-running).
| Token | Description | Example |
|---|---|---|
{{job_name}} | Name of the job. | daily_etl |
{{run_id}} | Unique ID of the run. | abc123-def456 |
{{run_link}} | URL to view the run in Dagster. | .../runs/abc123 |
{{run_status}} | Status (SUCCESS or FAILURE). | FAILURE |
{{failure_message}} | Error message if the run failed. | Step 'load_data' failed... |
{{user_name}} | Name of the user who launched the run. | John Doe |
{{user_email}} | Email of the user who launched the run. | john@example.com |
{{partition_name}} | Name of the partition (if applicable). | 2026-01-08 |
{{schedule_name}} | Name of the schedule that triggered the run. | daily_schedule |
{{sensor_name}} | Name of the sensor that triggered the run. | new_files_sensor |
{{elapsed_time}} | Human-readable duration of the run. | 5 minutes |
{{start_time}} | Start time of the run. | Jan 8, 2026 10:00 AM |
{{end_time}} | End time of the run. | Jan 8, 2026 10:05 AM |
Asset Materialization Tokens
Available for Asset Materialization events (Success/Failure/Check Failure).
| Token | Description |
|---|---|
{{run_id}} | Unique ID of the run. |
{{run_link}} | URL to view the run in Dagster. |
{{failure_message}} | Error message describing the failure. |
{{user_name}} | Name of the user who launched the run. |
{{user_email}} | Email of the user who launched the run. |
Asset Health, Freshness & Table Schema Tokens
Available for Asset Health, Freshness, and Table Schema events.
| Token | Description | Context |
|---|---|---|
{{asset_key}} | Full asset key. | All Asset Events |
{{health_status}} | Overall status (OK, DEGRADED). | Asset Health |
{{materialization_status}} | Status of materialization. | Asset Health |
{{checks_status}} | Status of asset checks. | Asset Health |
{{freshness_status}} | State (PASS, FAIL, UNKNOWN, OK). | Freshness / Health |
Code Location Tokens
| Token | Description |
|---|---|
{{location_name}} | Name of the code location. |
{{location_link}} | URL to the code location. |
{{failure_message}} | Error message describing the load failure. |
Tick (Schedules & Sensors) Tokens
| Token | Description |
|---|---|
{{instigator_name}} | Name of the schedule or sensor. |
{{instigator_type}} | Type (schedule or sensor). |
{{schedule_name}} | Name of the schedule (empty if this is a sensor failure). |
{{sensor_name}} | Name of the sensor (empty if this is a schedule failure). |
Agent Downtime Tokens
| Token | Description |
|---|---|
{{agent_url}} | URL to the agents page in Dagster. |