Workflows
Automate actions in response to DevBar events — no code required. Workflows let you connect any trigger (incident, deploy, PR) to any action (Slack message, notification, webhook).
What are Workflows?
A Workflow is an automation rule scoped to your organisation or a specific team. Each workflow has:
- A trigger event — the DevBar event that starts the workflow.
- Optional conditions — field-level filters so the workflow only fires when relevant (e.g. severity = error).
- One or more actions — what happens when the trigger fires and conditions pass.
Org admins can publish workflows to the Workflow Marketplace so teammates can install them with one click and optionally fork and customise locally.
Available trigger types
| trigger_event | Description |
|---|---|
| push | A git push event received via webhook or CI integration |
| pr.opened | A pull request was opened in a connected repository |
| pr.merged | A pull request was merged into the target branch |
| pr.closed | A pull request was closed without merging |
| incident.triggered | A PagerDuty or inbound webhook incident was triggered |
| incident.acknowledged | An on-call engineer acknowledged an incident |
| incident.resolved | An incident was resolved and closed |
| monitor.alert | A Datadog or Grafana monitor fired an alert |
| monitor.recovered | A previously firing monitor recovered to a healthy state |
| deploy.success | A deployment completed successfully (DORA integration) |
| deploy.failure | A deployment failed (DORA integration) |
| webhook.inbound | Any event received via POST /webhooks/inbound with a matching token |
Available actions
| action_type | Description |
|---|---|
| notify | Send a notification to the DevBar menu bar |
| slack.message | Post a message to a Slack channel |
| webhook.send | Send an HTTP POST to an external URL |
| log | Write an entry to the DevBar audit log |
Creating a workflow
- 1Go to Dashboard → Workflows and click "New workflow".
- 2Choose a trigger event from the dropdown.
- 3Optionally add conditions to filter when the workflow fires (e.g. field: severity, op: eq, value: error).
- 4Add one or more actions — select the action type and configure its parameters.
- 5Set the scope to "org" (visible to all org members) or "team" (restricted to specific teams).
- 6Click "Publish" to make the workflow available. Team members can install it from the Marketplace.
Example: Post to Slack when a PagerDuty incident is triggered
This example workflow fires when a PagerDuty incident arrives via the inbound webhook and posts a formatted message to your Slack #incidents channel.
Workflow definition (JSON)
{
"name": "PagerDuty → Slack #incidents",
"trigger_event": "incident.triggered",
"conditions": [
{ "field": "severity", "op": "eq", "value": "error" }
],
"actions": [
{
"action_type": "slack.message",
"channel": "#incidents",
"text": "🚨 Incident triggered: {{title}} — {{message}}"
}
],
"scope": "org"
}The condition ensures the workflow only fires for severity: error events — info and warning events are skipped.
Managing workflows via API
All workflow operations are available via the Workflows API. Use POST /api/v1/org/workflows to create workflows programmatically or as part of an infrastructure-as-code setup.
shared_workflows feature flag, which is enabled on Team and Enterprise plans.