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

# last

Reference for the last variable in action placeholders and conditions.

{% hint style="info" %}
This page describes the `last` variable: the most recent response, 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 `inbound`, not in templated settings (such as a webhook body) (such as a webhook body). Start with [Actions → The 'steps' section](https://docs.ilert.com/integrations/actions.md#the-steps-section) for how the definition works.
{% endhint %}

Root `last`: the most recent response. Outbound, it is the last response of the current step; absent before the step's first request. In `expect.condition`, `referenceWrite` and `authoredId` it is the response that just arrived. Inbound, it is the most recent hydrate read.

```yaml
openapi: 3.1.0
info:
  title: ilert action context - last
  version: 1.0.0
  description: >-
    Root `last`: the most recent response. Outbound, it is the last response
    of the current step; absent before the step's first request. In
    `expect.condition`, `referenceWrite` and `authoredId` it is the response
    that just arrived. Inbound, it is the most recent hydrate read.
components:
  schemas:
    Response:
      type: object
      required: [body]
      description: A recorded response. Headers are not exposed.
      properties:
        status:
          type: integer
          description: HTTP status.
        body:
          description: >-
            Parsed JSON when the response is JSON, otherwise the raw text
            (truncated).
```


---

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