> For the complete documentation index, see [llms.txt](https://developers.bloomcredit.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.bloomcredit.io/enablement-services/mutations/importconnectionmutation.md).

# ImportConnection

{% hint style="info" icon="lock" %}
**Authorization**

Requires user scoped authorization via session token. See the 'Session Token Authentication' section in [Enablement Services Authorization](/enablement-services/enablement-services-getting-started/enablement-services-authentication.md) guide for reference.
{% endhint %}

The importConnection mutation allows you to import a previously established aggregator connection, enabling our system to ingest and categorize transactions associated with that connection.

This mutation accepts both Plaid access tokens and processor tokens.

* `Access Token`: A token that provides full access to the user's financial data.
* `Processor Token`: A token created for a specific processor that grants limited access, typically used for one-time data sharing.

.

{% code title="Mutation" %}

```graphql
# Example using an access token
mutation {
  importConnection(token: "access-sandbox-123abc") {
    connectionId
    provider
  }
}

# Example using a processor token
mutation {
  importConnection(token: "processor-sandbox-456def") {
    connectionId
    provider
  }
}

```

{% endcode %}

#### Input Attributes

| Attribute | Description                              |
| --------- | ---------------------------------------- |
| **token** | A Plaid access token or processor token. |

***

#### Output Attributes

| Attribute        | Description                          |
| ---------------- | ------------------------------------ |
| **connectionid** | Unique connection identifier.        |
| **provider**     | Connection provider (PLAID, MX, etc) |


---

# 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://developers.bloomcredit.io/enablement-services/mutations/importconnectionmutation.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.