> 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/6.0/6.3/appmixer-ui-sdk.md).

# Appmixer UI SDK

- [Introduction](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/introduction.md): Appmixer SKD is a toolkit to embed workflow automation and integration capabilities into your products. Gain a whole new set of comprehensive features with ease.
- [Installation](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/installation.md): Appmixer SDK package includes two types of modules: basic UMD and advanced ESM.
- [Quick Start](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/getting-started.md)
- [Constructor](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/constructor.md): Appmixer Constructor lays a foundation for building user interfaces with widgets.
- [API Module](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/api-module.md): The Appmixer SDK uses this API module internally to connect to the REST API.
- [UI & Widgets](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets.md): Appmixer UI is a tool for building user interfaces with component-based widgets.
- [Flow Manager](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/flow-manager.md): Browse and manipulate flows that are accessible to the current user.
- [Designer](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/designer.md): Build, edit and inspect individual flows in a comprehensive editor.
- [Insights Logs](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/insights-logs.md): Browse logs of messages that passed through flows.
- [Insights Chart Editor](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/insights-chart-editor.md): Create charts to visualize logs of messages that passed through flows.
- [Insights Dashboard](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/insights-dashboard.md): Browse and manipulate charts created by the current user.
- [Accounts](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/accounts.md): Manage accounts authorized by the current user.
- [Storage](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/storage.md): Manage records associated with data storage utility components of flows.
- [People Tasks](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/people-tasks.md): Manage tasks created by utility components of flows.
- [Connectors](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/connectors.md): Browse apps and components that are accessible to the current user inside flows.
- [Integrations](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/integrations.md): Manage flows used as integration templates and instances.
- [Wizard](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/wizard.md): Manage a flow that is used as an integration instance.
- [Files](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/ui-and-widgets/files.md): Manage files for use with components of flows.
- [Custom API](https://docs.appmixer.com/6.0/6.3/appmixer-ui-sdk/custom-api.md): Appmixer SDK allows you to override API methods used by the SDK instance. This can be handy in edge case scenarios where you need to override the API requests and their parameters or response values.


---

# 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/6.0/6.3/appmixer-ui-sdk.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.
