Skip to main content
Use a W&B automation to send a prompt to ARIA when a specific event occurs. Each time the event occurs, the automation starts a new ARIA conversation and sends it the configured prompt. An automation that sends a prompt to ARIA consists of two main parts:
  • The event that triggers the automation.
  • The prompt that ARIA receives when the event occurs.
Use this workflow to explore experiment results, summarize or report on runs, or investigate metrics that cross a threshold. Sending a prompt to ARIA is one action that a W&B automation can perform. To create automations that send notifications to other destinations, refer to Create a Slack automation or Create a webhook automation. You can also ask ARIA to create and manage W&B automations on your behalf. For details, see Create and manage automations with ARIA.
Available only in W&B Multi-tenant Cloud.ARIA works in team projects, not in your personal entity. Your organization admin must also enable Smart features. See Governance and security.

​
Requirements

Before you create an automation that sends a prompt to ARIA, verify the following:
  • Your organization must have ARIA enabled. If Trigger ARIA doesn’t appear in the Action type list, ARIA isn’t available for your organization, scope, or deployment. The list omits the option without explanation. See Governance and security.
  • You must have write access to the project, registry, or collection you scope the automation to.
  • To scope a W&B automation to a registry and send prompts to ARIA, you must belong to a team in the same organization. Each ARIA conversation is associated with a team, so you can’t create a registry-scoped automation if you don’t belong to a team in that organization.
Each time an ARIA automation runs, it starts an ARIA conversation that counts toward your organization’s usage, the same as a conversation you start yourself.

​
Create an automation

Select Registry or Project based on the scope you want the automation to apply to. Then follow these steps to create an automation that sends a prompt to ARIA.
To apply an automation more broadly, create it from the global Automations hub and select the Team or Organization scope. The steps are the same as those that follow. At these scopes, W&B supports artifact and collection events only. See Automations hub.
A Registry admin can create automations in that registry.
  1. Log in to W&B.
  2. Click the name of a registry to view its details.
  3. To create an automation scoped to the registry, click the Automations tab, then click Create automation. An automation that is scoped to a registry is automatically applied to all of its collections (including those created in the future).
  4. Choose the event to watch for. Fill in any additional fields that appear, which depend upon the event. For example, if you select An artifact alias is added, you must specify the Alias regex. Click Next step.
  5. Select the team that hosts the ARIA conversation. See Where the conversation appears.
  6. Set Action type to Trigger ARIA.
  7. In the Prompt field, write the prompt to send to ARIA. See Write the prompt. Click Next step.
  8. Provide a name for the automation. Optionally, provide a description.
  9. Click Create automation.
The automation is now active and starts a new ARIA conversation whenever the chosen event occurs in the registry.

​
Create and manage automations with ARIA

ARIA can create, delete, enable, and disable automations on demand. Ask ARIA to create an automation: Ask ARIA about your existing automations:

​
Write the prompt

The prompt is the only thing you configure for an ARIA action. Write it the way you would write a message in the ARIA chat window, and include template variables to specify which run, artifact, or metric ARIA should examine. Keep the following constraints in mind:
  • A prompt is required and can be at most 4,000 characters. W&B checks the length again after it substitutes template variables, so a prompt that saves successfully can still fail when the automation runs if the substituted values are long. A prompt that fails this check is recorded as a failed execution in the automation’s execution history.
  • A template variable that doesn’t apply to the event resolves to an empty string rather than to its own name. Use only the variables listed for your event.
  • ARIA starts a new conversation each time the automation runs. It doesn’t continue a previous conversation and doesn’t remember earlier executions of the same automation.
To insert a variable, click the next to it in the list below the Prompt field. W&B appends the variable to the end of the prompt. The list shows only the variables that apply to the event you selected. For example, this prompt investigates each newly linked model version:
You can ask ARIA to help you word a prompt before you save the automation:

​
Template variables

Template variables use the syntax ${variable_name}. The variables available to a prompt depend on the event the automation watches for. The following variables are available for every event: The following variables are available in addition to the preceding ones, depending on the event: The following notes apply to individual variables:
  • ${artifact_version} resolves to an artifact instance, such as wandb-artifact://_id/QXJ0aWZhY3Q6NTE3ODg5ODg3. To refer to the version by name, use ${artifact_version_string}.
  • ${artifact_metadata.KEY} reads a custom metadata value from the artifact version that triggered the event. Replace KEY with the metadata key you want. Only top-level metadata keys are supported.
For the events available at each scope, see Automation events and scopes.

​
View conversations created by automations

The automation creates the ARIA conversation under the account of the user who created the automation, not the user whose action triggered the event. The conversation appears in that person’s ARIA chat history under Past conversations, alongside conversations they started themselves. To identify the user that caused the event, include ${event_author} in the prompt. Where the conversation lives depends on the automation’s scope:
  • Project-scoped and team-scoped automations: The conversation is created in the project where the event occurred.
  • Registry-scoped automations: A registry belongs to your organization rather than to a team, and ARIA conversations must belong to a team. The conversation is created in the team you selected when you created the automation, in a project named wandb_agent_default_project. Look there rather than in the registry. wandb_agent_default_project is a placeholder project that W&B maintains for each team to hold conversations that aren’t tied to a project you opened. You don’t create it, and it’s normally empty apart from these conversations.
To confirm that the automation ran, open its execution history. A successful ARIA execution shows the prompt that W&B sent and a response body containing the conversation’s thread_id. W&B doesn’t link from the execution to the conversation, and an automation-created conversation isn’t marked differently in your chat history.

​
View and manage automations

View and manage automations from the Automations tab in a project or registry, or from the global Automations hub. In the automations list, the action displays as ARIA. Only the creator of an automation that sends prompts to ARIA can edit it because the ARIA conversation runs as that user. Team members with write access to the project or registry can view and delete the automation, but the Edit automation option is unavailable to them. You can’t transfer ownership of the automation. Instead, delete it and have the new owner create it again. Use the same process to recover an automation whose creator has left the team.

​
Limitations

  • ARIA automations are available only on W&B Multi-tenant Cloud, in team projects, and only when your organization admin has enabled Smart features.
  • Each automation can start at most three ARIA conversations per minute. W&B records executions above that limit in the automation’s history with the status Skipped, meaning the automation matched the event but didn’t run its action.
  • If the person who created the automation loses write access to the project or their account is deactivated, every subsequent execution fails. The failure appears in the automation’s execution history.
  • Only the automation’s creator can edit it.
  • The wandb Python library doesn’t support ARIA automations. See Manage automations with the API.

​
Next steps