> For the complete documentation index, see [llms.txt](https://docs.appmixer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.appmixer.com/getting-started/build-your-automation-hub.md).

# Build Your Automation Hub

The Automation Hub is a one-stop shop for automations and AI agents for your end users.

Get started with the Automation Hub:

1. [Build and Publish a Template](/getting-started/integrations.md)
2. [Customize and Share Your Hub](/getting-started/customize-and-share-your-hub.md)
3. [Embed Your Automation Hub](/getting-started/embed-your-automation-hub.md)
4. [Monitor Hub Performance](/getting-started/monitor-hub-performance.md)

***

**Embed your own Hub to allow users to:**

* Browse and start Automations pre-built by your team
* Customize pre-built Automations
* Manage Logs and Accounts for their Automations

**Your team can easily manage the Hub:**

* Organize automations into categories (shown as tabs in the Hub)
* Adjust the look and feel of the Hub
* Monitor health and statistics of Hub Automations
* Define who can access specific automations
* Allow or Disable customization of pre-built templates by end-users


---

# 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.appmixer.com/getting-started/build-your-automation-hub.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.