> 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/stackai-tools/communication-and-human-input/create-connection.md).

# Create Connection

Ask the person using Chat Assistant to connect a service when the workflow needs that account’s access. Execution pauses while they complete the connection flow.

## Before you start

This action works in Chat Assistant. The user needs an account with access to the required service.

## Request a service connection

1. Choose the **Provider ID** and, when required, **Connector Type ID** for the service needed by the later action.
2. Use **Context** to explain what the workflow needs to access and why.
3. Run the workflow in Chat Assistant. Complete the displayed sign-in or credential flow.
4. Confirm that the connection response is available before the dependent action continues.

**Result:** The resumed run receives the connection result after the user completes the connection flow.

## Behavior and troubleshooting

This action does not create credentials for the provider or bypass its account permissions. The user must complete the provider’s authentication requirements. Follow the relevant setup instructions in the [Provider Catalog](https://docs.stackai.com/integrations/catalog.md).

## Inputs

| Field                  | Parameter           | Description                                                 |
| ---------------------- | ------------------- | ----------------------------------------------------------- |
| Provider ID (required) | `provider_id`       | The provider to create a connection for.                    |
| Connector Type ID      | `connector_type_id` | Optional specific connector type to use.                    |
| Context                | `context`           | Additional context to explain why the connection is needed. |

## Outputs

| Field             | Parameter           | Description                                |
| ----------------- | ------------------- | ------------------------------------------ |
| Provider ID       | `provider_id`       | The provider the connection is for.        |
| Connector Type ID | `connector_type_id` | The connector type if specified.           |
| Context           | `context`           | The context message provided.              |
| Resume Output     | `resume_output`     | The connection data when workflow resumes. |

## Related guidance

[Human Input and Approval Controls](https://docs.stackai.com/technical-reference/interfaces-and-conversations/human-input-and-approval-controls.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/stackai-tools/communication-and-human-input/create-connection.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.
