OAuth app integrations
Connect the work apps each Buda agent needs, review permissions before approval, and keep every connection under your control.
Your agents do their best work when they can reach the systems where work already happens. OAuth app integrations let you connect those systems directly to a Buda agent, without sharing passwords or giving every agent access to every account.
Each connection belongs to one agent. A product agent can work with Linear and Amplitude while a support agent uses Slack and HubSpot. You decide which account to connect, review the requested permissions on the provider's consent screen, and can disconnect it whenever the agent no longer needs access.
The status shown in Settings → Integrations is authoritative for your Space. Connect means the app is ready to authorize, Connected means that agent already has an active connection, and Coming soon means the connection is not currently available in your environment.
Connect an app
Open your Space, go to Settings → Integrations, and select the agent that needs access.
Find the app in OAuth integrations. Click Connect to start. If the app shows Coming soon, it cannot be connected in your Space yet.
Choose the account or workspace on the provider's authorization screen. Review the requested permissions carefully, then approve them.
Return to Buda and confirm that the app shows Connected. The connection is now available to that agent when a task needs it.
Current app catalog
The catalog below reflects the apps currently shown in Buda. The actions an agent can perform depend on the provider, the account you choose, and the permissions you approve.
Project work and knowledge
| App | What it adds to an agent |
|---|---|
| Linear | Work with issues, projects, and engineering workflows through Linear's MCP integration. |
| Asana | Bring Asana project work into the agent's workflow through its MCP integration. |
| Circleback | Connect the agent to Circleback through its MCP integration. |
| Granola | Make the connected Granola workspace available through its MCP integration. |
| Notion | Read and write permitted pages, databases, and blocks in the connected workspace. |
Customer and product operations
| App | What it adds to an agent |
|---|---|
| Amplitude (US) | Analyze product data, experiments, and user behavior in an Amplitude US workspace. |
| Amplitude (EU) | Analyze product data, experiments, and user behavior in an Amplitude EU workspace. |
| Attio | Work with permitted CRM data, records, and workflows in Attio. |
| HubSpot | Bring permitted HubSpot CRM, marketing, and support context into agent workflows. |
Development and publishing
| App | What it adds to an agent |
|---|---|
| GitHub | Install the Buda GitHub App so the agent can read the repositories you select during setup. |
| Raindrop | Make Raindrop's MCP capabilities available to the connected agent. |
| Sanity | Query and manage permitted content, schemas, projects, and releases through Sanity's hosted MCP server. |
| Supabase | Connect one project so the agent can work with its database and other permitted project resources. |
| Trigify IO | Make Trigify IO's MCP capabilities available to the connected agent. |
| Vercel | Use Vercel's MCP integration in the agent's development workflows. |
| WordPress.com | Connect a WordPress.com site through its OAuth 2.1 MCP integration. |
Communication
| App | What it adds to an agent |
|---|---|
| Slack | Read permitted Slack conversations and post updates using the scopes you approve. |
| Superhuman | Read and manage email in the connected Superhuman account. |
Finance and accounting
| App | What it adds to an agent |
|---|---|
| Digits | Connect the agent to the permitted Digits accounting workspace through MCP. |
| Dualentry | Connect the agent to the permitted Dualentry accounting workspace through MCP. |
| Robinhood | Connect the agent to Robinhood's Trading MCP service with the permissions available to your account. |
App-specific setup
GitHub repository access
GitHub uses an app installation flow. During setup, choose the personal account or organization where you want to install Buda, then select the repositories the agent may access. You can review or change repository access later from the GitHub installation settings linked in Buda.
Supabase project selection
Supabase connections are limited to one project per agent connection. Before authorization, enter the project's 20-character Project ID, also called the project reference. During authorization, choose the organization that owns that project.
A Supabase connection can permit changes to data, schemas, functions, and other project resources. Use a development or test project unless the agent is explicitly intended to work with production data.
Amplitude region
Choose Amplitude (US) or Amplitude (EU) to match where your Amplitude workspace is hosted. The two entries are separate so your authorization and product data stay in the correct region.
Permissions and security
- Connections are agent-specific. Connecting an app to one agent does not give every agent in the Space access.
- The provider controls consent. Its authorization screen shows the scopes or permissions being requested before you approve them.
- Buda stores the resulting credential securely. The agent uses it only when working with that connected app.
- Workspace permissions still apply. You need edit or manage access for the agent to connect or disconnect its integrations.
- The provider remains in control. Its own account, workspace, organization, and resource permissions continue to limit what the agent can reach.
Disconnect or revoke access
To stop an agent from using an app, open Settings → Integrations, select the agent, open the connected app's menu, and click Disconnect. Buda removes the stored connection for that agent.
For complete provider-side revocation, also open the provider's connected-app or installation settings and remove Buda there. This is useful when an account is being retired, ownership has changed, or you want to verify that the provider has invalidated the authorization.
Troubleshooting
- The app says Coming soon: the connection is not configured or available in your environment. No authorization can be started until its status changes to Connect.
- The authorization window does not open: allow pop-ups for Buda, then try Connect again.
- You closed or denied the authorization: return to Buda and start the connection again when you are ready to approve it.
- Authorization failed: confirm that you selected the intended account or organization and that your provider account can approve app access, then retry.
- Supabase cannot access the project: confirm the Project ID and authorize with an account in the organization that owns the project.
- A previously connected app stops working: disconnect it, reconnect it, and review the provider's consent screen for any changed permissions.