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

# config

Reference for the config variable in action placeholders and conditions.

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

Root `config` (outbound and inbound). Always present: the template's defaults merged with the values set on the action.

```yaml
openapi: 3.1.0
info:
  title: ilert action context - config
  version: 1.0.0
  description: >-
    Root `config` (outbound and inbound). Always present: the template's
    defaults merged with the values set on the action.
components:
  schemas:
    Config:
      type: object
      description: >-
        Keys are the template's settings (its form fields). Scalar values
        arrive as strings, so compare switches with `config.pushComments ==
        'true'`. List settings (chips) are arrays. Secrets are never part of
        config.
      additionalProperties: true
      examples:
        - project: OPS
          issueType: Task
          pushUpdates: "true"
          pushComments: "true"
          labels: [ilert, on-call]
```


---

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