Skip to main content
This feature requires a Pro or Enterprise plan.
Automations exist for both projects and registries. Where you create an automation, which events you can use, and how scope works all differ. For event types by scope, see Automation events and scopes. W&B Automations follow a simple pattern: when an event occurs and optional conditions are met, an action runs automatically. For example, when a run fails (event), notify a Slack channel (action). Or when the production alias is added to an artifact (event), call a webhook to trigger deployment (action). Events and available conditions depend on whether the automation is scoped to a project or a registry. Example: Run fails (event) and optional run name filter (condition) then Slack notification (action). Or: alias production added (event) then webhook (action).

​
Where to create automations

  • In a project: Open the project, then click the Automations tab in the project sidebar.
  • In a registry: Open the registry, then click the Automations tab.

​
Use cases

  • Run monitoring and alerting: Notify the team when a run fails or when a metric crosses a threshold (for example, loss goes to NaN or accuracy drops).
  • Registry CI/CD: When a new model version is linked or an alias (such as staging or production) is added, trigger a webhook to run tests or deploy.
  • Project artifact workflows: When a new artifact version is created or an alias is added in a project, run a downstream job or post to Slack.
For full event and scope details, see Automation events and scopes.

​
Automation actions

When an event triggers an automation, it can perform one of these actions:
  • Slack notification: Send a message to a Slack channel with details about the triggering event. The message summarizes the event, with a link to view more details in W&B.
  • Webhook: Call a webhook URL with a JSON payload containing information about the triggering event. This enables integration with external systems like CI/CD pipelines, model deployment services, or custom workflows.
For implementation details, see Create a Slack automation and Create a webhook automation.

​
How automations work

To create an automation, you:
  1. If required, configure secrets for sensitive strings the automation requires, such as access tokens, passwords, or sensitive configuration details. Secrets are defined in your Team Settings. Secrets are most commonly used in webhook automations to securely pass credentials or tokens to the webhook’s external service without exposing it in plain text or hard-coding it in the webhook’s payload.
  2. Configure team-level webhook or Slack integrations to authorize W&B to post to Slack or run the webhook on your behalf. A single automation action (webhook or Slack notification) can be used by multiple automations. These actions are defined in your Team Settings.
  3. In the project or registry, create the automation:
    1. Define the event to watch for, such as when a new artifact version is added.
    2. Define the action to take when the event occurs (posting to a Slack channel or running a webhook). For a webhook, specify a secret to use for the access token and/or a secret to send with the payload, if required.

​
Recommendations

  • Start small: Begin with one or two automations for high-value events (for example, run failures or production alias changes). Validate that they work as expected before adding more.
  • Test before production: Create automations in a test project or with a test webhook or Slack channel first. Manually trigger the event and confirm the action runs and the payload or message looks correct.
  • Avoid alert fatigue: Use run filters, metric thresholds, or alias patterns to limit how often an automation fires. Route different severities to different channels if needed.

​
Limitations

Run metric automations and run metrics z-score change automations are currently supported only in W&B Multi-tenant Cloud.

​
Next steps

Looking for companion tutorials for automations?