> For the complete documentation index, see [llms.txt](https://docs.riff.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.riff.ai/reference/shared/integrations.md).

# Integrations

Connect your app to the systems your data lives in, such as your accounting system or ERP.

An integration connects Riff to another system, such as your accounting system, your ERP or Slack. Once an integration is linked to your app, the Riff agent can build your app to read from and write to that system.

In a team, an Owner or Admin installs each integration once, and builders then link it into the apps that need it.

## Install an integration for your team

Team Owners and Admins install integrations:

1. In the left sidebar, click **Admin**, then **Connections**.
2. Under **Integrations**, click **Add Integration** and choose the system.
3. Give the connection a name. Then either click **Connect your account** and sign in to the system, or click **Add API Keys**, enter the keys and click **Save Credentials**.

Other members see "Ask your admin to install integrations".

To let Ask Riff explore an installed integration, click **Add to context**.

## Link an integration to your app

1. In your app, open **Integrations** with **+**.
2. Click **Link Account Integration** and choose the integration.

You can also ask the Riff agent to link it. Then tell the agent what data you need, and it writes the code that uses the integration.

If an admin has turned on **Require admin approval** for that integration, your request goes to an admin first.

In a personal workspace, there's no Admin step: add the integration straight from your app's Integrations tab with **+ Add Integration**.

## Who can see the data

A team integration is shared. Every builder who links it can see what it returns, and every call uses the same account or key. If some data should stay with certain people, decide that before you connect it: an admin can turn on **Require admin approval**, or the key can go in one app's own [Secrets](https://docs.riff.ai/reference/shared/secrets.md) instead.

## If your system isn't listed

Click **?** in the top bar to contact support, and tell us which system you use. If the system gives you an API key, you can also store the key in your app's [Secrets](https://docs.riff.ai/reference/shared/secrets.md) and ask the Riff agent to connect to it.


---

# 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.riff.ai/reference/shared/integrations.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.
