> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rundesert.com/llms.txt
> Use this file to discover all available pages before exploring further.

# What are integrations

> First-party connections we build and maintain, so the agent does not have to.

An integration is a service you connect once to your account. Every automation
you build can then reach it, without you handing the agent a token.

## Why we build these ourselves

The agent is good at working out access to a service on its own. For most of the
web, that is exactly what you want, and it is what the [Bot
detection](/bot-detection) page walks you through.

But a handful of services show up in almost every customer's work. Rebuilding
access to those from scratch in every workspace wastes your time and gives you a
slightly different result each time.

So we build those in house and call them first-party integrations. You connect
once, we maintain it, and it works the same way in every workspace you own.

## The vault

Connecting a service puts its credentials in a vault that we run, not in your
workspace.

Here is what that means in practice.

* **The agent never holds your long-lived credential.** It stays encrypted in our
  database and never reaches your workspace.
* **The agent asks for access at run time.** When a run needs to touch your mail,
  it requests a short-lived token, uses it, and lets it expire. It does not keep
  a copy.
* **We refresh it for you.** Tokens expire on the provider's schedule. We renew
  them behind the scenes, so your automation does not break one morning because a
  token aged out.
* **You can pull the plug.** Disconnect a service under **Integrations** and
  every automation loses access right away.

This is why a first-party integration beats pasting a token into the chat. Both
work, but the vault handles expiry, renewal, and revoking for you.

## What we support

<CardGroup cols={2}>
  <Card title="Google" icon="https://mintcdn.com/desertlabs/yriovLtjCNsTfMuj/images/logos/google.svg?fit=max&auto=format&n=yriovLtjCNsTfMuj&q=85&s=7954b935e9fcdb28f630063943f0702a" href="/integrations/google" width="268" height="274" data-path="images/logos/google.svg">
    Live now. Gmail and Google Docs.
  </Card>

  <Card title="Outlook" icon="https://mintcdn.com/desertlabs/yriovLtjCNsTfMuj/images/logos/outlook.svg?fit=max&auto=format&n=yriovLtjCNsTfMuj&q=85&s=6e0f971f9b19014eb2bd9cfee401439b" href="/integrations/outlook" width="570" height="540" data-path="images/logos/outlook.svg">
    Coming soon.
  </Card>

  <Card title="Slack" icon="https://mintcdn.com/desertlabs/yriovLtjCNsTfMuj/images/logos/slack.svg?fit=max&auto=format&n=yriovLtjCNsTfMuj&q=85&s=cbda411f9668c7e113da391f526aeea8" href="/integrations/slack" width="2448" height="2453" data-path="images/logos/slack.svg">
    Coming soon.
  </Card>

  <Card title="Notion" icon="https://mintcdn.com/desertlabs/yriovLtjCNsTfMuj/images/logos/notion.svg?fit=max&auto=format&n=yriovLtjCNsTfMuj&q=85&s=d488a6297228012c6a04f0a4423a4b8d" href="/integrations/notion" width="256" height="268" data-path="images/logos/notion.svg">
    Coming soon.
  </Card>
</CardGroup>

## If we do not support it yet

You are not stuck. The agent can reach almost any service the ordinary way: get
an API token from that service and paste it into the chat. See [Logins and
tokens](/prompting#logins-and-tokens).

And tell us. Email **[support@rundesert.com](mailto:support@rundesert.com)** with
the service and what you are trying to build. We move faster on the ones
customers are actually blocked on.