> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/platform/using-the-platform/integrations-and-credentials.md).

# Integrations & Credentials

## Overview

Many blocks on the AutoGPT Platform integrate with external services like Google, GitHub, Linear, Twitter, and more. These integrations require credentials — such as OAuth connections, API keys, or username/password pairs — to access your accounts on those services.

This guide explains how credentials work on the platform, how to add them, and how to manage them.

## How Credentials Work

### Platform-Provided Credentials

On the cloud-hosted platform at [platform.agpt.co](https://platform.agpt.co), some plans and account configurations include managed AI providers. If a block requires credentials that are not included, the platform will prompt you to connect your own. See the [pricing page](https://agpt.co/pricing) for current plan details.

### User-Provided Credentials

For services tied to your personal accounts, connect your own credentials. Credentials can be reused across agents, but you choose which compatible credential an agent or task uses. Managed credentials may be selected automatically when available.

## Adding Credentials

You can connect credentials centrally from **Settings → Integrations → Connect Service**, or in context when a builder block or task asks for one.

### When Building an Agent

If a block needs credentials, select an existing compatible credential or connect a new one from the block.

### When Running an Agent

Credential fields show the credentials that task will use. Select an existing compatible credential or connect a new one.

### Credential Types

Depending on the service, you'll be prompted to authenticate in one of three ways:

| Type                    | Description                                     | Example Services        |
| ----------------------- | ----------------------------------------------- | ----------------------- |
| **OAuth**               | Click to authorise via the service's login page | Google, GitHub, Twitter |
| **API Key**             | Paste your API key from the service's dashboard | Linear, OpenAI          |
| **Username & Password** | Enter your account credentials                  | Varies by service       |

{% hint style="info" %}
Credentials are reusable, but each block or task retains its selected credential reference.
{% endhint %}

## Managing Credentials

1. Open **Settings**.
2. Select **Integrations**.
3. Use **Connect Service** to add a credential, or manage/remove credentials already listed.

**URL:** [platform.agpt.co/settings/integrations](https://platform.agpt.co/settings/integrations)

{% hint style="warning" %}
Removing a credential can break agents, workflows, or active webhooks that reference it. Review the dependency warning before confirming removal.
{% endhint %}

## Self-Hosted Credentials

When self-hosting, configure deployment-level provider keys and OAuth application credentials in `autogpt_platform/backend/.env`, then connect end-user accounts from **Settings → Integrations** as needed. See the [Self-Hosting Guide](/docs/platform/self-hosting/getting-started.md) for details.


---

# 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://agpt.co/docs/platform/using-the-platform/integrations-and-credentials.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.