> For the complete documentation index, see [llms.txt](https://prohelp.assetpanda.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://prohelp.assetpanda.com/ursa/ursa-administrator-tasks/ursa-automations.md).

# Ursa automations

Build automations with Ursa

Ursa supports the full range of automation capabilities in Asset Panda Pro. See [Manage automations](/settings/account-management/automations.md).

Ursa can create automation rules for your collections based on natural language descriptions. Instead of manually configuring triggers, conditions, and actions, you can describe what you want to automate and let Ursa build it for you.

## Create an automation with Ursa

1. In the navigation pane, select <img src="https://1392520265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxeONEzrcpTXxoedP4Phm%2Fuploads%2FPGcLPehdYLLP7bOmBehU%2FSettings.png?alt=media&amp;token=3aac23e7-2676-4aa4-ae39-6e8941b81b8c" alt="Settings icon" data-size="line"> **Settings** > **Account Management**.
2. Expand the appropriate account and module, and then click **Manage** in the **Automation** tile. The list of automations is displayed.
3. In the navigation pane, select ![URSA icon](https://1392520265-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FxeONEzrcpTXxoedP4Phm%2Fuploads%2FsvBdaCrsAlOIDNyFGzOU%2FURSA.png?alt=media\&token=1624067c-3976-4931-a19c-a7f79b2b53bd). The chat window is displayed.
4. In the chat input, enter the automation you want to create, including the following details:

   * **Trigger:** Event that starts the automation
   * **Conditions** (optional): Filters or criteria that must be met. If you only want the automation to run under certain circumstances, describe those conditions clearly.
   * **Action**: The tasks that should occur when the automation event occurs
   * **Recipients**: If applicable, the individuals (email addresses or role names) who should receive notifications or reports
   * **Schedule**: For scheduled automations, specify the frequency, day, and time.

   See [Example prompts](#example-prompts).\
   \
   Ursa generates the automation configuration and presents it for your review.

{% hint style="info" %}
For best results, describe one automation rule at a time.
{% endhint %}

6. [Review and customize the generated automation](#review-and-customize-the-generated-automation).

#### Example prompts

> *Send an email notification when a laptop's warranty expiration date passes.*

> *When a new record is created in the People collection, create a corresponding record in the Equipment Assignments collection.*

> *Every Monday at 9 AM, send a report of all assets with a **Status** of Needs Maintenance.*

> *When a record is updated and the **Status** field changes to Retired, update the **Available** field to No.*

> *Send a Slack notification when a form is submitted for an equipment check-out.*

> *One day before an audit start date, send an email reminder to the audit team.*

***

## Review and customize the generated automation

1. Review the trigger, conditions, and actions.

{% hint style="info" %}
The automation is created with a status of **Inactive** by default, so it won't run until you activate it.
{% endhint %}

2. To modify the automation, perform one of the following tasks:
   * Ask Ursa to modify specific parts. For example, *"Change the trigger to weekly instead of daily."*
   * Open the automation in the automation editor to make manual adjustments.
3. When the automation is correct, select the **Status** toggle for the automation to activate it.