> ## Documentation Index
> Fetch the complete documentation index at: https://wb-21fd5541-docs-1778-mysql-updates.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations overview

> Use W&B Automations for triggering workflows based on events in W&B

<Info>
  This feature requires a [Pro or Enterprise plan](https://wandb.ai/site/pricing/).
</Info>

This page describes *automations* in W\&B. [Create an automation](/models/automations/create-automations/) to trigger workflow steps, such as automated model testing and deployment, based on an event in W\&B, such as when an [artifact](/models/artifacts/) artifact version is created or when a [run metric](/models/runs/) meets or changes by a threshold.

For example, an automation can notify a Slack channel when a new version is created, trigger an automated testing webhook when the `production` alias is added to an artifact, or start a validation job only when a run's `loss` is within acceptable bounds.

## Overview

An automation can start when a specific [event](/models/automations/automation-events/) occurs in a registry or project.

In a [Registry](/models/registry/), an automation can start:

* When a new artifact version is linked to a collection. For example, trigger testing and validation workflows for new candidate models.
* When an alias is added to an artifact version. For example, trigger a deployment workflow when an alias is added to a model version.

In a [project](/models/track/project-page/), an automation can start:

* When a new version is added to an artifact. For example, start a training job when a new version of a dataset artifact is added to a given collection.
* When an alias is added to an artifact version. For example, trigger a PII redaction workflow when the alias "redaction" is added to a dataset artifact.
* When a tag is added to an artifact version. For example, trigger a geo-specific workflow when the tag "europe" is added to an artifact version.
* When a metric for a run meets or exceeds a configured threshold.
* When a metric for a run changes by a configured threshold.
* When a run's status changes to **Running**, **Failed**, or **Finished**.

Optionally, you can:

* Filter artifacts, aliases, or tags by name
* Filter runs by user or run name.

For more details, see [Automation events and scopes](/models/automations/automation-events/).

To [create an automation](/models/automations/create-automations/), you:

1. If required, configure [secrets](/platform/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](#automation-events) 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.

## Limitations

[Run metric automations](/models/automations/automation-events/#run-metrics-events) are currently supported only in [W\&B Multi-tenant Cloud](/platform/hosting/#wb-multi-tenant-cloud).

## Next steps

* [Create an automation](/models/automations/create-automations/).
* Learn about [Automation events and scopes](/models/automations/automation-events/).
* [Create a secret](/platform/secrets/).