> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/actions/context/actor.md).

# actor

Reference for the actor variable in action placeholders and conditions.

{% hint style="info" %}
This page describes the `actor` variable: who made the change, one of the variables you can use in `{{ }}` placeholders and conditions when you customize an action's YAML definition. It is available in `steps` and in templated settings (such as a webhook body), not in `inbound`. Start with [Actions → Custom behavior](https://docs.ilert.com/integrations/actions.md#custom-behavior-advanced-topic) for how the definition works.
{% endhint %}

Root `actor` (outbound only): who made the change. Absent when nobody did, for example on `alert.escalated`, `alert.escalation_ended`, `alert.priority_raised` and delayed incident events. On a manual run it is the user who clicked Run.

```yaml
openapi: 3.1.0
info:
  title: ilert action context - actor
  version: 1.0.0
  description: >-
    Root `actor` (outbound only): who made the change. Absent when nobody did,
    for example on `alert.escalated`, `alert.escalation_ended`,
    `alert.priority_raised` and delayed incident events. On a manual run it is
    the user who clicked Run.
components:
  schemas:
    Actor:
      type: object
      properties:
        id:
          description: Id of the user or alert source.
          type: integer
        type:
          type: string
          enum: [USER, SOURCE]
          description: A person, or the alert source (for example an auto-resolve).
        name:
          type: string
          description: Display name ("first last", falling back to the email).
        origin:
          type: string
          description: >-
            Where an accept or resolve was done outside the web app. Present
            only on `alert.accepted` and `alert.resolved`. For action callbacks
            it is the template's brand, for example `jira`; Telegram buttons
            send `Telegram (<name>)`; a ServiceNow alert source sends
            `ServiceNow`.
          examples: [jira, Telegram (Jane Doe), ServiceNow]
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ilert.com/integrations/actions/context/actor.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
