> 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/changelog/2025/may-2025-7.md).

# May 2025

### New features and improvements

* We have launched our new feature **Event Flows** in closed **BETA** :tada:, [reach out to us](broken://spaces/-M76ygPnS4HUcFSX8ulm/pages/-MA0haGzw_vocetU3uxE) if you like to try it out; its like call flows, but for your events
* We have launched a new **AI agent** "Alert Investigator" in closed **BETA** :tada:, which uses MCP servers to gather information e.g. ELK Logs or Github Deployment related source code to provide responders with a root-cause analysis right in their ilert alert detail view, reach out to us if you like to try it out.

### Integration updates

* **Autotask** outbound has been revamped
* **ServiceNow** outbound has been revamped
* bidirectional alert source creation no longer relies on redirects (multi forms) the whole creation now happens within the alert source wizard
* New inbound integration [LibreNMS](/integrations/inbound-integrations/librenms.md)
* New inbound integration [Panther](/integrations/inbound-integrations/panther.md)
* New inbound integration [TeamCity](/integrations/inbound-integrations/teamcity.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/changelog/2025/may-2025-7.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.