DevBarDevBar

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_eventDescription
pushA git push event received via webhook or CI integration
pr.openedA pull request was opened in a connected repository
pr.mergedA pull request was merged into the target branch
pr.closedA pull request was closed without merging
incident.triggeredA PagerDuty or inbound webhook incident was triggered
incident.acknowledgedAn on-call engineer acknowledged an incident
incident.resolvedAn incident was resolved and closed
monitor.alertA Datadog or Grafana monitor fired an alert
monitor.recoveredA previously firing monitor recovered to a healthy state
deploy.successA deployment completed successfully (DORA integration)
deploy.failureA deployment failed (DORA integration)
webhook.inboundAny event received via POST /webhooks/inbound with a matching token

Available actions

action_typeDescription
notifySend a notification to the DevBar menu bar
slack.messagePost a message to a Slack channel
webhook.sendSend an HTTP POST to an external URL
logWrite an entry to the DevBar audit log

Creating a workflow

  1. 1Go to Dashboard → Workflows and click "New workflow".
  2. 2Choose a trigger event from the dropdown.
  3. 3Optionally add conditions to filter when the workflow fires (e.g. field: severity, op: eq, value: error).
  4. 4Add one or more actions — select the action type and configure its parameters.
  5. 5Set the scope to "org" (visible to all org members) or "team" (restricted to specific teams).
  6. 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.

Requires a Team plan. Workflow sharing and the Marketplace are gated behind the shared_workflows feature flag, which is enabled on Team and Enterprise plans.