Automation events and scopes

  2 minute read  

An automation can run when a specific event occurs at a given scope, either a registry or a project. This page lists the events that can trigger an automation at each scope.

Registry

This section describes the scopes and events for an automation in a Registry.

Scopes

You create a Registry automation in these scopes:

• A Registry and all of its collections (the default).
• A single collection.

Events

These events can trigger a Registry automation:

• Linking a new artifact to a collection: Test and validate new models or datasets when they are registered.
• Adding a new alias to a version of an artifact: Trigger a special step of your workflow when a new artifact version has a specific alias applied. For example, deploy a model when it has the deploy alias applied.

Project

This section describes the scopes and events for an automation in a project.

Scopes

You can create a project automation in these scopes:

• The project and all of its collections (the default).
• All collections that match the filter you supply.

Events

These events can trigger a project automation:

• Linking a new artifact: Test and validate new models, datasets or dataset automatically.
• Creating a new version of an artifact: Apply recurring actions to each version of an artifact. For example, start a training job when a new dataset artifact version is created.
• Adding a new alias to a version of an artifact: Trigger a special step of your workflow when a new artifact version in a project or collection has a specific label or alias applied. For example, run a series of downstream processing steps when an artifact has the test-set-quality-check alias applied.

Next steps

• Create a Slack automation
• Create a webhook automation