Connect an Integration

Step 1 — Go to Integrations

In the Console, click Integrations in the left sidebar.

Step 2 — Choose an integration

Click the service you want to connect. Each card shows:

• What the integration can do
• Required permissions
• Authentication method (OAuth or API key)

Step 3 — Authenticate

OAuth integrations (GitHub, Slack, Google, Atlassian, Notion): you’ll be redirected to the provider’s login page to authorize Auteryn.

API key integrations (Telegram bot token, ServiceNow, custom tokens): paste credentials in the connection setup form.

Use a service account where possible

For shared team integrations (GitHub, Google, Slack), connect using a service account rather than a personal account. This avoids issues if the connecting person leaves your organization.

Step 4 — Set permissions

1. Click on the connection → Permissions
2. Toggle each permission on or off
3. Save

Step 5 — Enable for your agent

1. Open the agent → Integrations tab
2. Find the integration and enable it
3. Save

---

Whose account does the agent act as?

When you connect a personal account — your own Google, Slack, or GitHub login — the agent acts as you when it uses that connection. A personal connection is private to you by default: teammates can’t use it until you share it.

Auteryn labels each connection so you can tell at a glance:

• Personal · you — your own login. Acts as you.
• Personal · <name> — a teammate’s login. Acts as them.
• Shared · team — a service or bot account the whole team can use.

A personal connection has three sharing states, changed from the connection card’s Who can use this menu (by the connection’s owner, or an org owner/admin):

• Private to you — the default. Only your own runs can act as it.
• Shared with team — anyone’s agents can use it.
• Specific people… — only the teammates you pick.

If an agent reaches for a personal connection that hasn’t been shared with the person running it, the conversation keeps going — just 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.”

Attaching connections to agents: only the owner can attach their private personal connection to an agent (admins can’t attach someone else’s private login), and a connection an admin marks Only admins can attach is admin-attach-only. Tightening sharing later never breaks agents that already use the connection — admins get an explicit “detach from N agents” action instead.

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 carries its own status dot. Green means agents can use it right now; amber means it still needs something from you (usually re-authorizing); red means the credential is gone and only reconnecting will fix it.

A service showing Needs attention or Error has at least one unhealthy connection — the dot 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 use Test on that connection.
• 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 → [connection name]
2. Click Disconnect
3. Review what’s listed, then confirm

Before you confirm, Auteryn names every agent, loop, and knowledge source 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 tab.

Owners and admins can disconnect and restore. Members can do neither.

---

Troubleshooting

The agent isn’t using the integration

• Confirm the integration is enabled on the agent’s Integrations tab (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 → [connection] → Reconnect
• Re-authorize via OAuth — this refreshes the token without losing your permission settings