> 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/kb/appmixer-studio-features/connected-accounts.md).

# Connected accounts

Throughout the process of creating workflow automations or integrations, you will be most likely connecting different third-party accounts (Slack, Asana, Salesforce, ...). The time and place you'll be connecting the accounts is at the time you need them, in the flow/integration configurations. However, it is very useful to have a one-stop shop for all your third-party accounts for management and security purposes. This is exactly what the Connected Account UI provides.

In the following sections, you'll learn how to connect a new account and manage it in the "Accounts" panel.

{% content-ref url="/pages/-Mez6TiYk4M-R1M5QNav" %}
[Connecting a new account](/kb/appmixer-studio-features/connected-accounts/connecting-a-new-account.md)
{% endcontent-ref %}

{% content-ref url="/pages/-Mf2xn7b6Zye5t-\_q5p4" %}
[Managing accounts](/kb/appmixer-studio-features/connected-accounts/managing-accounts.md)
{% endcontent-ref %}


---

# 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/kb/appmixer-studio-features/connected-accounts.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.