Automations overview

You can scope an automation to an Organization, a Team, a Registry, a Registry collection, or a project. An automation observes the event across everything in its scope, including projects, registries, and collections created later. 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 this 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).
• When the production alias is added to an artifact (event), call a webhook to trigger deployment (action).

Events and available conditions differ for automations scoped to a project or a registry. See Automation events and scopes. 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 the Automations hub: Select Automations in the left navigation to see every automation you can access across all scopes and projects. You choose the scope (Organization, Team, Registry, Registry collection, or project) when you create the automation. See Automations hub.
• In a project: Open the project, then select the Automations tab in the project sidebar.
• In a registry: Open the registry, then select the Automations tab.

​

Automations hub

The Automations hub is a global surface in the left navigation that aggregates every automation you can access, across all scopes and projects, in a single list. Use it to discover, inspect, and manage automations without navigating to each project or registry. From the Automations hub, you can:

• View all automations you can access in one list, then filter and sort them (for example, by scope, trigger, or action).
• Use the quick filter to switch between automations you created and all automations in your organization.
• Click an automation’s name to view its full configuration in a details drawer.
• View an automation’s execution history to check whether it succeeded or failed.
• Create an automation and choose its scope, without needing to know the scoped entry point first.
• Select multiple automations and delete them at once.

The Automations hub complements the Automations tab in each project and registry; those scoped tabs remain available for quick access.

​

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: Sends a message to a Slack channel with details about the triggering event. The message summarizes the event and includes a link to view more details in W&B.
• Webhook: Calls a webhook URL with a JSON payload containing information about the triggering event. Use webhooks to integrate with external systems such as 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, then confirm that the action runs and that the payload or message looks correct.
• Avoid alert fatigue: Use run filters, metric thresholds, or alias patterns to limit how often an automation fires. If you have multiple severities, route them to different channels.

​

Limitations

• Run metric automations and run metrics z-score change automations are supported only in W&B Multi-tenant Cloud.
• At the Team and Organization scopes, the W&B App supports only artifact and collection events. Run-based events aren’t available in the App at these scopes. See Automation events and scopes.

​

Next steps

• Automations tutorial: Guides you to create a project automation to alert on run failures and a Registry automation to run a webhook when an alias is added. The tutorial uses the W&B App.
• Create an automation.
• Automation events and scopes.
• Create a secret.