Skip to main content
Connect a tool once and your agent can use it on every call. Connections live in the app store, which needs the Pro plan or above, and each one takes about two minutes: you sign in to the tool and choose what your agent may do with it. Anything not in the app store can still be reached with a custom action.

​
Before you start

  • The Pro plan or above for the app store. Webhooks work on every plan, including Free.
  • An account in the tool with permission to do what you want your agent to do.
  • Prefer a shared business account over a personal one, because a connection made with somebody’s personal login stops working when they leave.

​
Steps

1

Open the app store

In your dashboard, open the app store to see what you can connect.
2

Choose your tool and sign in

Pick the tool and sign in to it. You are authorising Brilo through the tool’s own login rather than handing over a password.
3

Add an action that uses it

A connection on its own does nothing. Open your agent’s Actions tab and add the action you want, for example booking an appointment or creating a contact.
4

Tell your agent when to use it

In the Prompt tab, say when the action applies. An action switched on but never mentioned in your instructions may never run.
5

Test it end to end

Make a call that should trigger the action, then check the tool itself rather than trusting the call went well.

​
You will know it worked when

  • The tool shows as connected in the app store.
  • A test call produces the change you expected inside that tool.
  • The call record shows the action ran.

​
What connecting a tool lets your agent do

Two different things, and it is worth knowing which you need.
  • Look something up during the call, so your agent can tell a caller their order status or find a free appointment. This has to happen while the caller waits, so it needs to be quick.
  • Write something after the call, so a lead or a summary lands where your team works. The caller never waits for this.

​
When your tool is not in the app store

You have two routes, and neither waits on Brilo to build anything:
  • A custom action lets your agent reach your own system during a call, including reading data back to the caller.
  • A webhook sends the details of every call to your system after it ends.
Both need someone technical for about an hour. If your tool is popular and missing, tell support@brilo.ai: what customers ask for is how the list grows.

​
If it did not work

The connection failed while signing in. Check you are using an account with permission to do what the action needs, and that you completed the tool’s own consent screen. The connection works but the action does not. The action is separate from the connection. Check the action exists in this agent’s Actions tab and that your instructions say when to use it. The connection keeps dropping. Access has expired or been revoked. Reconnect with a shared account rather than a personal one. Anything else: An action did not run.

​
FAQ

Google Calendar for bookings, plus HubSpot, Jobber, Shopify, and Apollo.io for CRM, field service, ecommerce, and enrichment. Check the app store in your dashboard for the current list, which changes more often than this page. See Supported integrations.
No, not for anything in the app store. You sign in to the tool and pick what your agent may do. Only custom actions and webhooks need someone technical.
Pro or above. Webhooks are available on every plan including Free, so sending call details to your own system does not require an upgrade. See Plans and what they include.
No. Connecting tools is included in your plan. What the actions do can use your allowances, for example an email your agent sends after updating a record.
Yes, and each action picks the connection it uses. Keep it to what your agent actually needs: every extra action is another decision it makes mid call.
In the app store next to the tool. A connection that used to work and now does not is the usual sign that access was revoked, often because a password changed or somebody left.
Disconnecting stops Brilo reaching the tool. Anything already written there stays, since it belongs to that tool rather than to Brilo. Actions that relied on the connection will fail until you reconnect.