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

# Template schema

Field reference for the parts of an action's YAML definition you can customize.

{% hint style="info" %}
These pages are the field-by-field reference for an action's YAML definition. You need them only to customize an action beyond its form. Start with [Actions → Custom behavior](https://docs.ilert.com/integrations/actions.md#custom-behavior-advanced-topic) for how the definition works and how to edit it.
{% endhint %}

Every action is defined by a YAML document. A template supplies it; you can change `config`, `steps` and `inbound`. The `config` section is a plain map of the template's settings, described in [Actions → The 'config' section](https://docs.ilert.com/integrations/actions.md#the-config-section). The other two have their own schemas:

| Section                                                                    | What it defines                                                                                                              |
| -------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- |
| [steps](https://docs.ilert.com/integrations/actions/template/steps.md)     | The requests the action sends, their conditions, and how the created object is remembered as the twin                        |
| [inbound](https://docs.ilert.com/integrations/actions/template/inbound.md) | How callbacks from the target system are matched to an alert or incident and turned into accept, resolve, comment or reroute |

Each schema is written in OpenAPI 3.1. The variables that placeholders and conditions in these sections can read are described under [Context schema](https://docs.ilert.com/integrations/actions/context.md).


---

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