What are integrations

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 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

​

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. And tell us. Email [email protected] with the service and what you are trying to build. We move faster on the ones customers are actually blocked on.