Skip to main content

Actions

An action describes a business event you care about, such as:

  • Example: login
  • Example: view_article
  • Example: checkout_complete

Esper cannot define these for you because the meaning depends on your product, your traffic, and your naming.

What an action contains​

Each action definition includes:

  • action_id: The unique identifier for the action definition.
  • tenant_id: The tenant that owns the action.
  • name: The business-friendly name of the action.
  • description: A short explanation of what the action represents.
  • enabled: Whether Esper should evaluate this action.
  • expression: The condition Esper uses to recognize the action in traffic.

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.

API contract​

GET /tenants/{tenant_id}/actions
POST /tenants/{tenant_id}/actions
PATCH /tenants/{tenant_id}/actions/{action_id}
DELETE /tenants/{tenant_id}/actions/{action_id}