App authorisation
The three ways an app in the catalogue connects, how an app that needs your own app is set up, and what Vertical AI stores for a connection.
Every app in the catalogue connects in one of three ways. The way is a property of the app, not something you select, and each card under All apps shows it as a badge.
It is worked out on the server from the app's own authentication configuration rather than trusted from the browser.
The three ways an app connects
| Badge | What you do | What happens |
|---|---|---|
| Sign in | Sign in on the service's own page | Our connection broker holds a shared app for the service. You sign in to the service and approve access. No credentials are typed into Vertical AI. |
| API key | Paste a key on the next page | You supply an API key or token for the service. It is collected on our connection broker's hosted page, not in a Vertical AI form. |
| Your own app | Register an app with the service, then sign in | The service only lets an app it knows sign in, and there is no shared app for it, so you register one of your own. |
A few apps need no account at all. They show Sign in too, but connect straight away with no sign-in and no consent screen.
Your own app
Xero and Jobber are examples. The setup sheet on the Connected apps page walks you through it in the Sign in step:
- Create an app in the service's developer settings.
- Paste the redirect address the sheet shows. It is on our own domain, for
example
https://app.verticalai.com.au/api/connected-apps/oauth-callback, and each environment shows its own. It passes the service's reply on to our connection broker, unchanged. - Copy the app's client ID and secret into the sheet, then sign in as usual.
If the app signs out, Sign in again brings you back to this step to enter the details again, and the new values replace the old ones. To replace a secret on an app that still works, disconnect it and set it up again.
HighLevel connects with Sign in
HighLevel has a Vertical AI-provided app, so it shows Sign in: you sign in, and there are no credentials to enter.
Why an assistant cannot connect one
An app that needs your own app cannot be connected by asking an assistant. The client secret would have to pass through the language model to get there, which is not allowed, so the assistant refuses and points you to Connected apps in the app.
See connect your assistant for what an assistant can do with connections.
What is stored
When you connect an app, Vertical AI stores the app, its scope, and who connected it, plus an opaque reference to the account held by our connection broker. That reference is not a secret and not a token.
What is never stored
Vertical AI never receives, stores, or logs the access token for a connected account. The client ID and secret you enter for your own app are passed on to our connection broker when you connect, and Vertical AI does not keep them.
Tool arguments, which can contain caller information, are not written to logs either. The Recent activity list on an app shows which ability was used, by which agent and when, never the arguments.
For credentials you do hold yourself, such as an API key used in a webhook tool's header, see variables and secrets.