> For the complete documentation index, see [llms.txt](https://help.tellius.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.tellius.com/tellius-6.3/kaiya/understanding-ai-agents-and-agentic-flows/automated-workflows.md).

# Automated workflows

Kaiya Agentic Insights turns one question into a multi-step analytical workflow, automating planning, execution, and business-ready explanations in a single run.

Kaiya Agentic Insights (also called **Deep Insights** or **Agent Mode**) is the part of Kaiya that turns one real business question into a full, multi-step analytical run. Instead of returning a single chart or a single SQL answer, it reads the question, decides which steps are needed, runs those steps with the right agents (SQL, Python, summary), and then explains the result in business language. 

{% hint style="success" %}
Once you turn on the **Deep Insights** button in Kaiya, it can do this in two ways: it can plan the workflow itself from the question, or it can follow a user-defined workflow that you have already published.
{% endhint %}

This is designed to remove the “20-question” loop common in chat analytics (ask → shallow answer → follow-up → shallow answer). With Agentic Insights, you ask once and Kaiya does the decomposition internally.


---

# 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://help.tellius.com/tellius-6.3/kaiya/understanding-ai-agents-and-agentic-flows/automated-workflows.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.