> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/workflow-guides/how-to-connect-an-integration.md).

# Connect an integration

Connect your workspace to third-party services from **Integrations**.

This guide covers finding an integration, adding a connection, and confirming it is ready. Connected integrations are reusable across apps and agents.

## Prerequisites

{% hint style="info" %}
You need access to a Qore workspace and **Integrations**.

You also need service credentials. These may be an API key, OAuth login, or core-banking credentials.
{% endhint %}

## Connect methods

Each integration uses one of three connect methods:

* **Connect BYOK (Bring Your Own Key)** — you supply your own API key or OAuth credentials. Best for services you already have an account with (e.g., OpenAI, Salesforce, Stripe).
* **Connect via UDG (Uptiq Data Gateway)** — you authenticate through Uptiq's managed gateway. Best for partner-managed services.
* **MCP Sandbox Account** — connects to core banking / accountancy systems through the Kinective network (cards marked **Powered by K**).

## Steps

{% stepper %}
{% step %}

### Open Integrations

Select **Integrations** in the left navigation. The catalog lists 200+ integrations. Use the **search** box, the **category chips** (All, Storage, Authentication, LLM, Payments, CRM, Accountancy, Banking, Messaging, …), or the **status** filter to find a service.

<figure><img src="/files/JuHX4q45kkAHFzF0A93J" alt=""><figcaption><p>The Integrations catalog, with search, category chips, and integration cards</p></figcaption></figure>
{% endstep %}

{% step %}

### Select the integration

On the integration's card, click **+ Connect** (visible directly on the card). This opens the integration's **detail page**, showing its status (e.g., *Not Connected*), an **Overview**, and an **All Connections** table.

<figure><img src="/files/nRBdkgxpcXT92fZ4M4r9" alt=""><figcaption><p>The integration detail page, showing status, Overview, and the All Connections table</p></figcaption></figure>
{% endstep %}

{% step %}

### Add a connection

Click **+ Add Connection**. In the **Manage {Service}** dialog, enter a **Connection Name** and the service-specific details:

* **LLMs** (e.g., OpenAI): choose a **Model** (and provide your API key where prompted).
* **OAuth services**: click to authorize through the provider's consent screen.
* **Token / token + webhook services**: paste your API key (and webhook secret).

Then click **Save**.

<figure><img src="/files/Jun6QrtXgFyhDrHPsRsz" alt=""><figcaption><p>The Manage {Service} dialog, with Connection Name, service fields, and Save</p></figcaption></figure>

{% hint style="info" %}
Credentials are encrypted at rest and masked as `******` on read. For OAuth, tokens are refreshed automatically.
{% endhint %}
{% endstep %}
{% endstepper %}

## Verify

The connection appears in the integration's **All Connections** table with a connected status.

The integration is now available to your **apps and agents**.

## Common issues

* **Not sure which method to use.** Core-banking cards show **Powered by K** (MCP Sandbox / Kinective); most SaaS use BYOK or UDG.
* **OAuth won't complete.** Re-run the connect step and finish the provider consent screen; ensure pop-ups aren't blocked.
* **The service I need isn't in the catalog.** For any REST API without a pre-built connector, use the [API Call Skill](/platform-resources/skill-library/logic-and-data-integration/api-call.md).

## Related pages

* [Integrations Hub](/integrations/integrations-hub.md) and [Connect Methods](/integrations/integrations-hub/connect-methods.md)
* Use it in an app: [Create an app](/workflow-guides/create-an-app.md)
* Give an agent reach into a service: [Create an agent](/workflow-guides/create-an-agent.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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.uptiq.ai/workflow-guides/how-to-connect-an-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.