> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/infraon-automation.md).

# Infraon Automation

Infraon Automation is part of Infraon Configuration and contains configurations that can automate features, processes, and activities within Infraon.

This module of Infraon consists of the following:

**Mail Automator:** Configure IMAP mail accounts on infraon and refer guides to forward your existing emails to Infraon to convert emails into tickets.

**Workflow:** Visualize and create a process flow involving specific activities in the selected module.

**Business Rule :** Defines the business rule for the Infraon system for auto assignment of tickets.&#x20;

**Escalation:** Defines the escalations process and automatic assignment mechanism are employed in support ticket resolution.&#x20;

**Customer feedback templates:** Customize templates to collect feedback to improve service quality and customer experience.

Let's see each of these in detail.&#x20;


---

# 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.infraon.io/infinity/user-guide/infraon-configuration/infraon-automation.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.
