> For the complete documentation index, see [llms.txt](https://helpdocumentation.gitbook.io/user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://helpdocumentation.gitbook.io/user-documentation/ai-dashboard/create-an-ai-agent.md).

# Create An AI Agent

### Step 1: Access the AI Dashboard

* Sign into your platform and go to the AI dashboard.​

### Step 2: Go to the AI Agents Page

* Navigate to the "AI agents" page within the dashboard.​
* If you need help accessing the dashboard, refer to the separate video on that topic.​

### Step 3: Create a New AI Agent

* Click on "New AI Agent".​
* Enter a name for your agent (e.g., "Support Agent" or "Sales Agent").​

### Step 4: Train the AI Agent with Your Content

* Select the agent you want to train.​
* Choose the option to upload files for training.​
* Supported file types are PDF, DOC, TXT, Excel, and CSV.​
* Upload your file; the AI agent will be trained using that content.​

### Step 5: Review Training Resources (Optional)

* For more details on training the AI agent with your files, consult the specific video dedicated to that step.​

{% embed url="<https://youtu.be/H49YThtOzOM>" %}


---

# 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://helpdocumentation.gitbook.io/user-documentation/ai-dashboard/create-an-ai-agent.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.
