Connect an Integration

Step 1 — Go to Integrations

In the Console, click Integrations in the left sidebar.

Step 2 — Choose an integration

Click a card to see what an integration does before you connect it. A panel opens with:

• What it lets an agent do: its abilities, split into what it can read and what it can change
• What it asks for: the permissions it requests, or the details you will enter

For an integration that runs on the vendor’s hosted service, an info icon beside its name opens Runs on the vendor’s hosted service. It shows the host and the date it was last reviewed, along with Vendor status.

For a Featured MCP Integration, the panel shows when Auteryn last vetted it and has its own Install button (Install another once one is installed).

Click the connect button in that panel, such as Connect GitHub, or use Connect on the card to go straight to it. When the service already has a connection, the button reads Connect another account.

Step 3 — Authenticate

OAuth integrations (GitHub, Slack, Google, Jira, Confluence, Notion, Linear): you’ll be redirected to the provider’s login page to authorize Auteryn. On a team, Auteryn first asks who can use the connection.

Credential integrations (a Telegram bot token, Twilio account credentials, a ServiceNow login, a Featured MCP key): paste the credentials in the connection setup form.

Use a service account where possible

For shared team integrations (GitHub, Google), connect using a service account rather than a personal account, so the connection doesn’t depend on one person’s login.

Step 4 — Add it to your agent

1. Open the agent → Integrations section
2. Click Add integration and pick the service
3. Choose its abilities. They start read-only. Turn on Allow writes only when the agent needs to change things
4. Save

Each agent has its own abilities, so two agents can use the same connection and still do different things.

---

Who can use this

Behind a connection is an account. An agent that uses the connection acts as that account, and what the agent does shows as that account in the service. Who may use a connection falls into three cases:

• Shared with your team. Any agent the connection is added to can use it, including agents that answer customers.
• Only you, or specific people. You alone, or just the teammates you pick, can use it.
• Each person’s own account. You set this on the agent. It acts as whoever is chatting with it, and each teammate connects their own account.

On a team, each connection also says whose account it is: Acts as your <service> account, or Acts as <name>’s <service> account for a teammate’s. A team account has no such line.

When you connect

On a team, connecting a service with your own sign-in (such as Google, GitHub or Notion) starts with a question: Who can use this connection. Everyone on <team> is already chosen. The other choices are Only you and Specific people, and with Specific people you pick the teammates after you connect. Choose, then continue to the service to sign in. When the sign-in finishes, a message says who can use the connection.

A shared connection can be used by any agent it is added to, including agents that answer customers. What an agent does with it shows as your account in the service. For a connection that shouldn’t depend on one person, connect with a service account instead.

If you are the only person in your organization, you aren’t asked. A new connection is private to you. Connections that already exist keep the sharing they had.

Change who can use a connection

On a team, each connection has a sharing control that shows the current choice:

• Everyone on <team>: shared with your team.
• Only you, or Only <name> on a teammate’s connection.
• Specific people · n: the teammates you picked.
• Team account: see Team accounts.

Select it to open Who can use this connection and choose again. The connection’s owner and organization owners and admins can change it. For everyone else it is a label.

Owners and admins also see Adding to agents there, with the setting Only owners and admins can add it to agents. An Only you connection can be added to an agent by its owner alone, and admins can’t add someone else’s. Tightening sharing later never breaks agents that already use the connection. Admins get an explicit Also detach from N agents option instead.

If an agent uses a connection that isn’t shared with the person running it, the conversation keeps going and only that action is declined, with a note like “This agent uses <name>’s personal GitHub account. Connect your own GitHub to use it, or ask them to share it with the team.”

Share the connections you already have

When your organization has teammates, Auteryn asks once whether to share the connections only you can use. The prompt, Share your connections with <team>?, lists them and appears on the Integrations page and in the Command Center. Share with team shares every connection listed, and Keep private leaves them as they are. After you answer, the prompt doesn’t come back, and you can share any of them later from its sharing control.

Team accounts

Connections made with an API key, a bot token or a service account are team accounts. No one’s personal login is behind them, so there is no sharing choice: the control reads Team account, and the team can use the connection. Owners and admins can still limit who adds it to an agent.

Each person’s own account

Some agents should act as whoever is chatting, not as one shared login. On the agent, turn on Acts as each user for the integration (see Integrations in the agent guide). Each teammate then connects their own account, and the agent uses the account of the person running it. If someone hasn’t connected yet, the agent’s setting decides: it uses the team connection, or it asks them to connect their own account first. In chat, a run that needs your own account shows Connect your <service> account, which opens the Console to connect it. Commands an agent runs on its own computer still use the team connection.

When agents use each person’s own account and you haven’t connected yours, the integration’s page shows a card with Connect my account. On a team, once you have connected your own account to an integration, with or without an agent that acts as each person, a line under the connection list reads Your account: connected as <account>, with Reconnect and Disconnect. Owners and admins also see how many people have connected their own account.

Already had connections?

Connections that existed before identity labels launched were kept shared with team so nothing broke. Owners and admins saw a one-time review banner to keep each one shared or make it private to its owner.

---

Checking a connection is healthy

Each connection shows its own status. Working means agents can use it right now; Needs reconnect means your sign-in expired and reconnecting puts it back to work; Not working means agents can’t use it right now. Hover over a status for the reason and when it was last checked.

A service showing Needs attention or Error has at least one unhealthy connection — the status beside each connection name tells you which one. To check for yourself rather than waiting for the status to catch up:

• One connection — open the integration and choose Test connection from that connection’s menu.
• Several — use Test all at the top of the integration’s panel.

Testing makes a real call to the provider, so it reports what an agent would actually hit, not what we last recorded.

---

Disconnecting a connection

1. Go to Integrations and open the service
2. Open the connection’s menu and click Disconnect
3. Review what’s listed, then confirm

Before you confirm, Auteryn names every agent and Loop that uses this connection — those are what stop working. Disconnecting applies to your whole organization, not just your own agents.

You have 30 days to undo it

A disconnected connection isn’t erased immediately. It moves to Recently deleted at the foot of the Integrations page and stays restorable for 30 days, after which it is permanently removed. If it was the last connection for that service, the restore offer also appears on the service’s card in the directory — so you don’t accidentally connect a second account when you meant to bring the first one back.

Restoring brings back the connection and re-arms its event webhooks. It does not re-attach the connection to agents: any agent that used it needs enabling again on its Integrations section.

Owners and admins can disconnect and restore a connection. Members can only disconnect their own account, with Disconnect on the Your account line under the connection list.

---

Troubleshooting

The agent isn’t using the integration

• Confirm the integration is enabled in the agent’s Integrations section (not just connected at the org level)
• Explicitly mention the service in your message: “Use GitHub to check the open issues”

OAuth token expired

• Go to Integrations, open the service and choose Test connection, then Reconnect
• Re-authorize via OAuth. This refreshes the token on the same connection