> 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/6.0/kaiya/understanding-ai-agents-and-agentic-flows/user-defined-workflows.md).

# User-defined workflows

User-defined workflows let you hard-code the exact analytical steps Kaiya should run (SQL pulls, Python methods, visualizations, and the final summary), instead of letting the planner assemble them on the fly. You describe the steps in natural language, optionally add required parameters, and map a trigger phrase to the workflow (for example, “quarterly payer deep dive”). When a user’s question contains that trigger, Kaiya executes your governed sequence in that order, applies your defaults, asks only for missing inputs, and returns a consistent, repeatable output every time.

All user-defined workflows can be found under **Published Agents** tab in **Kaiya → AI Agents →** **Agent Library**.

<figure><img src="/files/ihNgdQxcK4dOPvY7VADA" alt=""><figcaption></figcaption></figure>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.tellius.com/6.0/kaiya/understanding-ai-agents-and-agentic-flows/user-defined-workflows.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.