Ursa Automations
Building Automations with Ursa
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.
What Ursa Can Automate
Ursa supports the full range of automation capabilities in Asset Panda Pro:
Triggers (What Starts the Automation)
When a record is created — Runs when a new record is added to a collection
When a record is updated — Runs when any field in a record changes
When a record is deleted — Runs when a record is removed
When a form is submitted — Runs when a user submits a specific form
On a schedule — Runs at set intervals (hourly, daily, weekly, monthly, or yearly)
Based on audit dates — Runs relative to audit start or end dates
When a record is audited — Runs when a record is included in an audit
When an audit is closed — Runs when an audit is finalized
Actions (What the Automation Does)
Send a notification — Send an email, Slack message, or Microsoft Teams notification
Send a report — Email a report of collection data
Update field values — Automatically change field values on a record
Create a record — Create a new record in the same or a different collection
Send an audit report — Email an audit report
Subscribe to a webhook — Send data to an external URL when triggered
How to Create an Automation with Ursa
Navigate to the Automations page for your collection.
Open the Ursa chat drawer by clicking the sparkle icon on the left navigation bar.
Switch to Agent mode using the mode dropdown.
Describe the automation you want to create.
Ursa generates the automation configuration and presents it for your review.
Important: Automation creation requires Agent mode. Ask mode cannot create or modify automations.
Describing Automations Effectively
For the best results, include these details in your prompt:
The trigger event — What should start the automation
Conditions (optional) — Any filters or criteria that must be met
The action — What should happen when the automation triggers
Recipients (if applicable) — Who should receive notifications or reports
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."
Reviewing and Customizing the Generated Automation
After Ursa generates your automation:
Review the trigger, conditions, and actions.
The automation is created with a status of Inactive by default, so it won't run until you activate it.
If you need changes, you can:
Ask Ursa to modify specific parts (e.g., "Change the trigger to weekly instead of daily")
Open the automation in the automation editor to make manual adjustments
Note: Ursa creates automations in an Inactive state. Review the configuration and activate it when you're satisfied it's correct.
Tips
One automation per prompt — For best results, describe one automation rule at a time.
Be specific about conditions — If you only want the automation to run under certain circumstances, describe those conditions clearly.
Specify notification recipients — Tell Ursa who should receive emails or notifications by providing email addresses or role names.
Mention scheduling details — For scheduled automations, specify the frequency, day, and time.
Last updated