> ## Documentation Index > Fetch the complete documentation index at: https://docs.brilo.ai/llms.txt > Use this file to discover all available pages before exploring further. # Integrations > Connect Brilo to the tools you already use, including your CRM, your calendar, the phone numbers you own, and your own email domain. An integration connects Brilo to a tool your team already uses, so your agent can look something up while a caller is on the line and write back once the call ends. Brilo has four kinds of integration, and each one is set up in a different part of your dashboard. ## What you can connect Each row below is a different kind of connection, with its own setup and its own owner, and links to the guides for it. | Kind | What it connects | Who sets it up | Guides | | - | - | - | - | | App store | Your CRM, calendar, helpdesk, ecommerce tools and more | Anyone with access to the tool | [HubSpot](/integrations/hubspot), [Salesforce](/integrations/salesforce), [Vagaro](/integrations/vagaro) | | Phone providers | Numbers you already own at another carrier | Whoever administers your phone system | [RingCentral](/integrations/telephony/ringcentral), [Twilio](/integrations/telephony/twilio/import-number) | | Email domain | Sending your agent's email from your own address | Whoever manages your DNS | [Email domain](/integrations/email/bring-your-own-domain) | | Your own systems | Anything the app store does not cover | Someone technical, about an hour | [Build a custom action](/actions/build-a-custom-action) | Most setups use two of the four. Most people start with the app store, because a calendar or a CRM is what makes an agent useful beyond taking a message. ## When you would use one Connect a tool when your agent needs to know something it cannot be told in advance, or when the result of a call belongs somewhere your team already works. Two examples cover almost every case: * **A caller asks a question only your system can answer**, such as whether an appointment slot is free or where an order has got to. Your agent looks it up mid call and reads the answer back. * **A call produces something worth keeping**, such as a new lead or a summary. Your agent writes it into your CRM after the call, so nobody retypes it. If neither applies, your agent does not need an integration. A prompt and a knowledge base cover a great deal on their own. See [What your agent can learn](/knowledge/what-your-agent-can-learn). ## How it works Connecting a tool is three steps, and only the first one happens on the integration screen. 1. **Connect the tool once**, from the app store or the relevant settings screen. 2. **Add an action that uses it** on your agent's **Actions** tab. A connection on its own does nothing until an action calls it. 3. **Say when it applies** in your agent's **Prompt** tab. An action that is switched on but never mentioned in your instructions may never run. See [What are actions](/actions/what-are-actions) for what step two involves, and [Connect your tools](/actions/connect-your-tools) for the walkthrough. ## What else you can do here * [Send call details to your own system](/actions/send-data-to-your-systems) with a webhook, which works on every plan. * [Book appointments during a call](/actions/book-appointments) once a calendar is connected. * [Update your CRM](/actions/update-your-crm) after a call rather than during it. * [Check which tools Brilo supports today](/supported/integrations), which is the page that carries the current list. ## FAQ No, not for anything in the app store. You sign in to the tool through its own login screen, or paste a key from it, and pick what your agent may do with it, which takes about two minutes. A developer is only needed for a custom action or a webhook. See [Do I need a developer](/start/do-i-need-a-developer). Almost certainly, by forwarding. Any phone system that can forward a number to another number can send calls to a Brilo agent, and RingCentral and most cloud phone systems can. Importing the number itself into Brilo needs Twilio, Telnyx or Plivo. See [Use your existing number](/phone-numbers/use-your-existing-number). The app store and your own email domain start at the Pro plan. Bringing a phone number you already own and sending call details to your systems with a webhook work on every plan, including Free. See [Plans and what they include](/supported/plans). Yes, through a custom action for mid call lookups or a webhook for sending call details afterwards. Neither waits on Brilo to build anything, and both need someone technical on your side for about an hour. See [Build a custom action](/actions/build-a-custom-action). A connection on its own does nothing. Your agent also needs an action that uses the connection, added on its **Actions** tab, and a line in its prompt saying when to use it. Check both before assuming the connection failed. See [An action did not run](/actions/an-action-didnt-run). No. Connecting a tool is included in your plan and there is no per connection charge. What the actions then do can use your allowances, for example a text or an email your agent sends after updating a record. See [What counts towards my usage](/account/what-counts-towards-my-usage). Connect a tool when your agent needs an answer during the call, because a webhook cannot reply mid conversation. Use a webhook when you only need the call details afterwards, for reporting or record keeping. See [Send data to your systems](/actions/send-data-to-your-systems). Disconnecting stops Brilo reaching that tool. Anything already written there stays, because it belongs to that tool rather than to Brilo. Any action that relied on the connection fails until you reconnect, so remove or switch off those actions too. ## Related * [Supported integrations](/supported/integrations) for the current list of tools * [Connect your tools](/actions/connect-your-tools) for the setup walkthrough * [What are actions](/actions/what-are-actions) for how a connection gets used * [Build a custom action](/actions/build-a-custom-action) when your tool is not listed * [An action did not run](/actions/an-action-didnt-run) when a connection misbehaves This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.