> ## Documentation Index > Fetch the complete documentation index at: https://docs.vybe.build/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Connect 3,000+ apps so AI coworkers and apps can read and act on your data Integrations connect Vybe to the apps your team works in, such as HubSpot, Salesforce, Jira, Notion, Gmail and Stripe. Once an app is connected, your AI coworkers can look things up and take actions in it, and your apps can call it from their code. ## The catalog Vybe's catalog has more than 3,000 apps. To browse it, click **Connect integration** on the **Connections** page. The **Select Integration** dialog opens, with a search box and pages of results. A few apps are built into Vybe and appear at the top of the list: | Integration | What you need | | - | - | | **Anthropic Managed Agents** | An **Anthropic API Key**, plus an optional **GitHub Personal Access Token** for work on code | | **Granola** | An API key | | **Intercom API Key** | An Intercom API key | | **Luma** | An API key | | **Supabase Management API** | A Supabase personal access token, entered in the **API Key** field | | **Zuora Billing** | A **Client ID** and **Client Secret**, plus the **API Tenant Environment** that issued them | | **LinkedIn** and **WhatsApp** | Your own account. See [LinkedIn and WhatsApp](https://docs.vybe.build/channels/linkedin-and-whatsapp.md) (Beta). | If an app isn't in the catalog, check the [MCP server catalog](https://docs.vybe.build/connections/mcp-servers.md), or connect it as a [custom API](https://docs.vybe.build/connections/custom-apis.md). ## Connect an integration **1. Open the catalog** Go to **Connections** in the sidebar and click **Connect integration** on the **Integrations** tab. You can also connect from a chat: click **+** in the message box and choose **Connect integration**. **2. Pick the app** Search for the app and click it. **3. Sign in or enter a key** For most catalog apps, a window opens where you sign in to the app and approve access (OAuth), or paste an API key if the app uses one. You'll see "*App* connected successfully". For Anthropic Managed Agents, Granola, Intercom API Key, Luma, Supabase Management API and Zuora Billing, a **Connect *name*** form asks for the credentials. Click **Connect**. **4. Review the settings** The integration's settings dialog opens. Choose the **Visibility**, add a **Display name (optional)**, give coworkers access under **Agent access**, and fill in any app-specific settings. Click **Save**. New accounts are Private: only you can use them, plus any coworkers you give access to. Switch **Visibility** to **Organization** to let everyone in your organization use the account. See [Who can use a connection](https://docs.vybe.build/connections/overview.md#who-can-use-a-connection). Some apps ask for a setting that Vybe uses on every call, for example a PostHog **Project ID**, a Jira **Cloud ID** or a GitHub **Owner and Repository**. Built-in integrations may show **Settings (optional, used when not specified per call)**. ## Connect more than one account You can connect the same app several times, for example a shared support inbox and your own inbox. Give each one a **Display name (optional)** so you and your coworkers can tell them apart. When several accounts could fit a request, the coworker asks which one to use. You can also name the account in your message or @-mention it. ## Give a coworker access Connecting an account doesn't give your AI coworkers access to it. Each coworker needs access to each account, at **Full access**, **Read only** or **Custom** level. You can give access from the coworker's **Connections** section, from the account's settings, or by approving the coworker's request in chat. See [How an AI coworker gets access](https://docs.vybe.build/connections/overview.md#how-an-ai-coworker-gets-access). > [!NOTE] > > A Slack integration account is separate from adding a coworker to Slack. To let people talk to a coworker in Slack, see [Slack](https://docs.vybe.build/channels/slack.md). A Slack integration account only gives access to the Slack actions in the catalog, using the account you connected. ## Use integrations in chat Ask for what you need in plain language. The coworker picks the integration and the action. **Fetching data** > Show me all open Jira tickets assigned to the engineering team. > Pull our last 30 days of Stripe charges and summarize them by customer. > What are our top-performing Google Ads campaigns this month? **Taking actions** > Create a Jira issue in the Backend project: "Fix login timeout bug", priority High. > Add these three leads to our Q3 outreach campaign in Lemlist. **Exploring what's available** > What can you do with our HubSpot connection? > Show me the fields on our Salesforce Lead object. To point the coworker at a specific account, type **@** in the message box and pick it from the **Integrations** section. The same list includes external databases, organization databases, data queries and custom APIs. ### What you'll see in the chat The coworker's work shows up as steps in its reply: | Step | What happened | | - | - | | "Listed integrations" or "Searched integrations for "*query*"" | It looked for a matching account or app | | "Connected to integration" | It loaded the actions an account offers | | "Ran *action*" | It ran an action, such as creating an issue. You can open the step to see its input and output. | | "Requested access" | It asked you for access it doesn't have | In the coworker's [activity history](https://docs.vybe.build/coworkers/usage-and-activity.md), each action appears as "Ran integration tool". When the coworker needs an app you haven't connected, it shows a **Connect *name*** card: * **Connect** opens the integration list, already searched for the app. Connecting from this card gives the coworker access right away. * If you already have a matching Private account that the coworker can't use, the card lists it with a **Grant** button. Use **Connect a different account** to add another one instead. * When it's done, the card reads "Connected as *account*" or "*n* accounts connected", with **Connect another**. If the account is connected but the coworker doesn't have access, you'll see a **Grant access to *name*** card instead. Pick the access level and click **Approve**. In Slack, the coworker posts a message with a link that opens Vybe to finish connecting. Connect links work once and expire after an hour. ### Tips for good prompts * **Be specific.** Instead of "show me Salesforce data", say "show me Salesforce opportunities closing this quarter worth more than \$50,000". * **Name the account** when you have more than one: "use the support@ Gmail account". * **Ask what's possible** before you plan a task: "What can you do with Jira?" * **Chain steps together.** "Pull open Jira tickets, find each assignee in Slack, and DM them a reminder about overdue tickets." * **Make it recurring.** Ask the coworker to run the task on a schedule, or to react to events in the app. See [Scheduled tasks](https://docs.vybe.build/automations/scheduled-tasks.md) and [Triggers](https://docs.vybe.build/automations/triggers.md). ## Use integrations in apps Apps call integrations from their code, and the AI in the app editor writes that code for you. Describe what you want: > When someone submits the new ticket form, create a Jira issue in the Backend project with the form data. The AI uses `runIntegrationAction` in browser code and `runIntegrationActionFromServer` in server code, such as API routes and background jobs. * **Organization** accounts work in all app code, including background jobs. * **Private** accounts only work while the person who connected them is using the app. They don't work in background jobs or scheduled code. If an account is disconnected or its sign-in expires, the app code that uses it fails until you reconnect it. See [Working with code](https://docs.vybe.build/apps/working-with-code.md) and [Background jobs](https://docs.vybe.build/apps/background-jobs.md). Artifacts that a coworker publishes can also show live data from integrations, but only through read-only actions. See [Artifacts](https://docs.vybe.build/coworkers/artifacts.md). ## Reconnect an account If an account's sign-in expires or is revoked, calls fail with an authorization error, and the coworker tells you which account is failing. To fix it: 1. Connect the app again from **Connect integration**. This adds a new account; the old one stays in the list. 2. Give your coworkers access to the new account. 3. Recreate any triggers on the new account. A trigger stays on the account it was created on. 4. Disconnect the old account. If the coworker says an action failed even though other actions on the same account work, reconnecting won't help: the account is missing a permission in the app itself. Ask an admin of that app to grant it. For LinkedIn and WhatsApp, use the reconnect button in the account's dialog on the **Connections** page. See [LinkedIn and WhatsApp](https://docs.vybe.build/channels/linkedin-and-whatsapp.md). ## Disconnect an account Open **Connections**, click the account, then click **Disconnect *name***. Confirm with **Delete**. * This permanently deletes the account from Vybe. * Triggers that use the account are deleted too. The dialog tells you how many. * Coworkers lose access, and app code that uses the account stops working. Only the person who connected the account, or an Owner or Admin, can disconnect it. You can also delete accounts from **Settings → Data → Integrations**. ## Troubleshooting > **An app can't be connected yet** > > You see "*App* can't be connected yet: it has no actions available." The catalog lists the app, but Vybe can't do anything with it yet. Check the [MCP server catalog](https://docs.vybe.build/connections/mcp-servers.md) or set it up as a [custom API](https://docs.vybe.build/connections/custom-apis.md). > **Vybe failed to save the connection** > > You see "Failed to save *App* connection". The sign-in worked, but Vybe couldn't save the account. Try again. If it keeps happening, contact [support@vybe.build](mailto:support@vybe.build). > **The coworker says it can't use an account** > > The coworker doesn't have access yet. Approve its request in chat, or turn the account on in the coworker's **Connections** section. If the account is someone else's Private account, ask them to share it or switch it to **Organization**. > **The coworker can read but not create or update** > > Its access level is **Read only**, or **Custom** without that action. Change the level in the coworker's **Connections** section. > **The coworker used the wrong account** > > Name the account in your message, or @-mention it. Display names make this easier. > **App code works for me but not for others** > > The app is probably using your Private account. Switch the account's visibility to **Organization**, or connect a shared account with Organization visibility. This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.