Integrations
Integrations connect your agents to the services you already use. Sign in once, and an agent can work with your email, calendar, code, documents, and chat — on your behalf, with your data staying under your control.
Services you can connect
Install an integration from the community catalog, then connect your account:
| Service | What agents can do |
|---|---|
| GitHub | Browse repositories, manage issues and pull requests, create branches and commits, run workflows. |
| Notion | Create and update pages, query and populate databases, organize content. |
More services land in the catalog as they're released — browse it from your own install to see what's available today.
Connecting an account
From User Settings → Integrations, pick a service, sign in through its standard consent screen, and approve access. That's it — OtoDock stores the connection on your server and keeps it refreshed automatically, so it doesn't silently expire.
You can connect multiple accounts to the same service and choose which account a given agent uses. For shared agents that act on behalf of the team, a manager designates which of their own connected accounts the agent uses as its identity. If a shared agent is asked to use a service no account has been designated for, it says exactly that in chat and points a manager at the right setting (Agent Settings → MCPs) — nothing fails silently.
GitHub also accepts a personal access token, if you'd rather not use OAuth at all.
Your own OAuth app
Connecting an OAuth service means registering a developer app with the vendor and providing its credentials in the admin settings — that way the app, and the scopes it asks for, stay entirely under your control.
The tokens stay on your install, readable only by OtoDock and kept out of agents' reach —
with one deliberate exception: connecting GitHub makes its token available in the agent's
shell, so git and gh just work in chat. See Credentials.
Integrations power triggers, too
Connecting a service also unlocks its event triggers — so an agent can react to a new issue or a fresh comment, not just act when you ask. See Triggers.
Next steps
- Triggers → — have agents react to events from connected services.
- Credentials → — how connections are stored and protected.
- Community Catalog → — connect even more services.