> 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/2022/may-2022.md). # May 2022 ### New features * Conditional alert actions; you may now add additional filters to alert actions * Alert action duplication, you may now easily copy and paste an alert action to other alert sources * Call routing numbers may now use uploaded audio files to playback greeting, waiting and mailbox messages * New endpoints have been added to the API to support add and remove operations for single user/team private subscribers ### Improvements * Overall page load times have been reduced for the web-ui, especially for accounts with large user and team bases ### New and updated integrations * Sentry inbound integration has been improved to support alert metric events * Autotask inbound integration has been improved to support new webUrl attribute for ticket link generation * SignalFX inbound integration has been improved to support better alert detail extraction --- # 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/2022/may-2022.md?ask=&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.