> 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/ilert.md).

# @ilert

Reference for the @ilert variable in action placeholders and conditions.

{% hint style="info" %}
This page describes the `@ilert` variable: ilert objects looked up by id, 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 `@ilert` (outbound only): ilert objects looked up by id when a placeholder references them, for example `{{ @ilert.schedules.12.user.email }}`. Only referenced ids are loaded, at most 25 per action, and only ones the action's owner may read. An unknown id is absent.

```yaml
openapi: 3.1.0
info:
  title: ilert action context - @ilert
  version: 1.0.0
  description: >-
    Root `@ilert` (outbound only): ilert objects looked up by id when a
    placeholder references them, for example
    `{{ @ilert.schedules.12.user.email }}`. Only referenced ids are loaded, at
    most 25 per action, and only ones the action's owner may read. An unknown
    id is absent.
components:
  schemas:
    IlertLookups:
      type: object
      properties:
        schedules:
          type: object
          description: Schedule id to schedule. Only schedules are supported.
          additionalProperties:
            $ref: '#/components/schemas/Schedule'
    Schedule:
      type: object
      description: >-
        The schedule as returned by the ilert API, including the user
        currently on call.
      additionalProperties: true
      properties:
        id:
          type: integer
        name:
          type: string
        user:
          type: object
          description: The user currently on call. Absent when nobody is.
          additionalProperties: true
          properties:
            email:
              type: string
```


---

# 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/ilert.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.
