What the app store is
The app store is a grid of tools Brilo can talk to, at App Store in your dashboard sidebar. Each tile opens a page for that tool showing what it does, a Connect button, and any connections you have already made to it. The app store is available from the Pro plan up. See Plans and what they include for what each plan covers.A connection belongs to your workspace, not to you. Anyone on your team with the right permission
can use it, and it keeps working when you are away. See
Who can do what.
How connecting works
Connecting takes one of two shapes, and the app store shows you which one you are in as soon as you click Connect.- Sign in to the tool. A window opens on the tool’s own login page. You sign in there and approve what Brilo may do. Brilo never sees your password. This covers most tools, including HubSpot, Google Calendar, Shopify and Slack.
- Enter details from the tool. A short form asks for values you copy out of that tool, such as a web address and a pair of keys. Tools that work this way have their own guide, listed under Guides for individual apps below.
What you can connect
The grid holds the tools most Brilo customers ask for, across CRM, calendar, helpdesk, ecommerce, messaging and project tracking. The list changes without a change to this page, so your dashboard is always the accurate answer. For the current list with a note on what each tool does, see Supported integrations.Searching for an app that is not on the grid
The grid is a curated set, not everything Brilo can reach. Type a tool’s name into the search box at the top of the app store and it searches the full catalogue, which is much larger than the grid. If the search finds nothing either, your tool is not in the catalogue yet. You can still reach it:- A custom action lets your agent call your tool during a conversation, including reading the answer back to the caller. See Build a custom action.
- A webhook sends the details of every call to your system after it ends, which suits reporting rather than mid call lookups. See Send data to your systems.
Guides for individual apps
Tools that ask you for details rather than a sign in have a guide of their own.
Every other tool in the grid uses the sign in flow described above, so
Connect your tools is the guide to follow.
Checking and removing a connection
Open the tool’s page in the app store to see its connections. Each one carries a status.
Removing a connection stops Brilo reaching the tool straight away. Anything already written there
stays, because it belongs to that tool. Any action that used the connection fails until you
reconnect, so switch those actions off as well.
If it did not work
The app store is not in your sidebar. The app store starts at the Pro plan. See Plans and what they include, or use a webhook, which works on every plan. The tool is not in the grid. Search for it by name first, because the grid is smaller than the catalogue. If search finds nothing, use a custom action or a webhook. The sign in window closed without connecting. Browser pop up blockers are the usual cause. Allow pop ups for your dashboard and try again. Signing in with an account that lacks permission in the tool has the same effect. The connection shows as inactive after working for weeks. Access was revoked on the other side, often because a password changed or the person who connected it left. Reconnect it, ideally with a shared business account. Anything else: An action did not run.FAQ
Which plan do I need for the app store?
Which plan do I need for the app store?
Pro or above. Webhooks are available on every plan including Free, so sending call details to
your own system does not need an upgrade. Bringing a phone number you already own also works on
every plan. See Plans and what they include.
Do I need a developer to connect an app?
Do I need a developer to connect an app?
No. You sign in to the tool through its own login screen, or paste a couple of values the tool
gives you, and the whole thing takes about two minutes. Only custom actions and webhooks need
someone technical. See Do I need a developer.
Does Brilo see my password when I connect an app?
Does Brilo see my password when I connect an app?
No. Signing in happens on the tool’s own login page, and the tool hands Brilo an access token
rather than your password. For the apps that ask for keys instead, those keys are encrypted
before they are stored and are only used to reach your own account.
Why can I not find my tool in the app store?
Why can I not find my tool in the app store?
The grid shows a curated set rather than everything. Search for the tool by name, because search
covers the full catalogue. If search finds nothing, the tool is not supported yet, and a custom
action or webhook is the route. Tell support which tool you need.
Can I connect two accounts of the same tool?
Can I connect two accounts of the same tool?
Not for the apps with their own guide. A workspace holds one Salesforce connection and one
Vagaro connection, so to switch accounts you remove the existing connection on the app’s page
and connect the other one. Vagaro actions each pick a location, so one connection still serves
every location the keys reach.
Why does my connection keep failing or disconnecting?
Why does my connection keep failing or disconnecting?
Access was almost certainly changed on the tool’s side. A password change, a revoked token, an
expired trial or somebody leaving the company all break a connection. Reconnect using a shared
business account rather than a personal login, which survives staff changes.
What happens to my data if I remove a connection?
What happens to my data if I remove a connection?
Removing a connection stops Brilo reaching the tool immediately. Records already written there
stay, because they belong to that tool rather than to Brilo. Actions that used the connection
fail until you reconnect, so switch them off in the meantime.
Related
- Connect your tools for the step by step walkthrough
- Supported integrations for the current list of tools
- Connect Salesforce and Connect Vagaro for the apps with their own setup
- What are actions for what to do once a tool is connected
- An action did not run when a connection misbehaves
