> ## Documentation Index
> Fetch the complete documentation index at: https://docs.esperr.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Actions

> Actions name request behaviors that policies can reference.

Examples:

* Example: `login`
* Example: `view_article`
* Example: `checkout_complete`

Esper cannot define these for you because the meaning depends on the tenant's
traffic model and naming conventions.

## What you define for an action

When creating an action, you choose:

* `name`: The business-friendly label for the event you want Esper to recognize.
* `description`: Optional context for operators who maintain the action later.
* `expression`: The traffic condition Esper should treat as that action.

## How to use actions well

* Define actions in business language, not backend language.
* Keep actions stable so they can be reused in policies.
* Use actions as building blocks for entity analysis and mitigation policy.