> For the complete documentation index, see [llms.txt](https://docs.stackai.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/create-and-manage-connections.md).

# Create and manage connections

A connection gives StackAI access to an account in an external service. A connector holds the shared authentication settings for that service. Use a connection when a workflow must read or change information in that account.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSQ1Sgy933krTyK0S4JpP%2Fuploads%2FkyJ4klpZcLHIiou3FXkp%2FG046.mp4?alt=media&token=0c8af3e9-77af-4dd0-bbda-41dc649fe3b3>" %}

## Before you start

Have access to an account with the provider permissions needed by your intended actions.

## Choose the provider and connector

Open Connections, select New Connection, and search for the required provider.

![Provider and organization connector selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/Xgr4UtJCP5PpVQrKbs4Z/assets/g046-g046-01-provider.png)

Choose the provider used by the workflow action you need.

Select the intended organization connector.

![Provider and organization connector selection](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/PSz8sB6QY6WOQMwjPACh/assets/g046-g046-02-connector.png)

Its configuration determines the application and authentication method used for the account connection.

If no connector is available, ask an organization administrator to review [Organization connector credentials](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/organization-connector-credentials.md) and the provider's availability. You do not need to register another application merely because you are adding a personal account connection; reuse the organization connector intended for your operation. Find provider-specific authentication and action requirements in the [Provider Catalog](https://docs.stackai.com/integrations/catalog.md).

## Authorize and name the connection

Review the provider's authorization screen and sign in with the intended account.

![Account authorization and connection naming](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/h3QQ6YwJYDbCyIGw9eDv/assets/g046-g046-03-authorize.png)

Check the requested permissions. A descriptive connection name does not limit the access granted by the provider.

Rename the connection to identify its account and purpose.

![Account authorization and connection naming](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/UqMwMGYdXjpCA9MvXZgQ/assets/g046-g046-04-name.png)

A clear name helps builders choose the correct account when several connections use the same provider.

## Check the connection

Check the connection's health status.

![Provider connection health check](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/aVHg77TNkJnT8zAcbz31/assets/g046-g046-05-health.png)

Read the reported error. For expired or revoked authorization, use **Reconnect**, complete provider consent with the intended account, and check health again. For missing permissions, ask the connector owner to review [Custom OAuth scopes and reauthorization](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/custom-oauth-scopes-and-reauthorization.md); changing the connection name will not grant access. If the provider is temporarily unavailable, retry after it recovers. Share the provider name, connection name, and error text with the connector administrator if the problem persists; omit credentials.

Select the connection in an action that reads data from the provider.

![Provider connection health check](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/jexFocGApOVPpZhpUSLx/assets/g046-g046-06-select.png)

A simple read operation can help you check account access without changing external records.

Run the action and inspect its response.

![Provider connection health check](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/DDP30Q4VPfoDWZEpIKY7/assets/g046-g046-07-test.png)

Confirm that the returned information belongs to the intended account.

## Manage who can use it

Open Permissions and review who can use the connection.

![Connection sharing permission controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/3mIt8EevyNAqAwG7Y74D/assets/g046-g046-08-sharing.png)

Share it only with members who should be able to use the account access it provides.

## Reconnect an account

Use Reconnect when the account authorization needs to be refreshed.

![Provider account reconnection controls](https://content.gitbook.com/content/SQ1Sgy933krTyK0S4JpP/blobs/xP4NPP5MosPqQre53yp1/assets/g046-g046-09-reconnect.png)

Complete the provider flow, then check connection health and rerun the required action.

## Important behavior

A connector defines the provider application and authentication method. A connection stores an account’s authorization through that connector.

Sharing a connection lets other authorized members use the account access it provides.

## Continue

* [Configure and test an action](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/configure-and-test-an-action.md)
* [End user connections](https://docs.stackai.com/guides-and-quickstarts/using-tools-and-actions/end-user-connections.md)


---

# 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.stackai.com/guides-and-quickstarts/using-tools-and-actions/create-and-manage-connections.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.
