Tools

Connected apps

Give your agents abilities in the apps your business already uses, set one up in three steps, and see what each app is doing on calls.

A connected app is a service your agents act in while a call is running: your calendar, your CRM, your inbox, your job or accounting system.

You connect the account once for the workspace, choose which agents use it, and choose what they may do with it. You write no URL, no method and no parameters.

Connected apps are one of several tool kinds. Tools covers builtin tools, webhook tools, prerequisites, and how the model decides to call any of them.

What your agents can do

The Connected apps page opens on the six jobs agents most often do on a call.

JobApps that do it
Book appointmentsGoogle Calendar, Outlook, Calendly
Know who is callingHubSpot, Salesforce, Pipedrive
Send emails and textsGmail, Outlook, and a texting app
Create jobsServiceM8, Jobber
Pass calls to your teamSlack, Microsoft Teams
Check invoices and ordersXero, Shopify, QuickBooks

Each job is a card. It names the app doing the job, says whether it works, and offers the one button that fixes it.

The card saysWhat it meansThe button
WorkingThe app is connected and at least one agent uses itManage
No agents yetThe app is connected but no agent uses itChoose agents
Signed outThe account stopped working, for example its sign-in expiredSign in again
Finish connectingA sign-in was started but not finishedFinish connecting
DisconnectedThe account was disconnectedConnect again
Not set upNone of the job's apps is connectedSet up

The small logos after Or or With are the other apps that can do the same job. Press one to set the job up with that app instead.

All apps

Every other app in the catalogue sits under All apps, below the jobs. It opens on a short list of popular apps. Choose a category, or Show all for the full catalogue of over a thousand apps. Search matches names, descriptions and categories from the first letter.

Each card says how the app connects: Sign in, API key or Your own app. App authorisation explains each.

Connected apps that are not part of a job are listed under Other connected apps.

Setting up an app

Press Set up on a job, or open an app under All apps. Setup is a sheet with three steps.

  1. Sign in. For a job, choose the app you use first. Then sign in to it on its own page and come back. An app that wants an API key asks for it on the next page. An app that needs your own app collects its details here first; see your own app.
  2. Choose agents. Switch on each agent that should use the app. Under They will be able to, the sheet lists what those agents may do and what they may never do. Choose Change what they can do to switch abilities on or off.
  3. Try it. Run one read-only check against the app. Google Calendar, for example, looks up today's free times. The check only reads from the app, so nothing changes there. A few apps have no safe check; for those, make a test call.

Setting up an app requires workspace admin access, because the connected account belongs to the workspace.

Your own app

Some apps, such as Xero and Jobber, only let an app they know sign in. For those you register your workspace as an app with the provider once:

  1. Create an app in the provider's developer settings.
  2. 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. Each environment shows its own address.
  3. Copy the app's client ID and secret into the sheet, then sign in as usual.

The redirect address passes the provider's reply straight on to our connection broker, unchanged. It does nothing else.

Abilities

An ability is a plain-language group of an app's actions, such as Book an appointment or Look up the caller. Agents get abilities, not the app's raw list of actions.

Abilities that administer the app, change who can see it, delete or cancel something, read a whole inbox, or create invoices and payments start switched off. For Google Calendar:

AbilityStarts
Check free timesOn
Book an appointmentOn
Move a bookingOn
Find a caller's bookingOn
Cancel a bookingOff
Manage calendars and sharingOff

Every ability an agent has becomes a tool description the model reads on every turn. Fewer abilities mean faster, steadier calls, so switch on only what the agent needs.

An app outside the six jobs has no abilities of its own. Agents get its recommended actions, and you can pick exact actions on each agent's Tools page.

Managing an app

Manage on a working job, or a connected app under All apps, opens the app's sheet:

  • How many times it was used in the last 30 days, the time since the last use, and how many agents use it.
  • When the connection was last checked.
  • What agents can do: the app's abilities. A switch here changes every agent that uses the app.
  • Recent activity: the app's last ten uses on calls, each with the ability, the agent, when, and whether it worked. It shows no call content and no arguments.
  • The agents that use the app, each with a switch.
  • Check it works: the same read-only check as setup.
  • Disconnect, which asks you to confirm first. Every agent that uses the app loses it from its next call. You can connect it again later.

If an app stops working, its job card says Signed out, and Sign in again on the card or in the sheet restores it. Nothing else changes. The sheet does not show the raw error from the service.

On the agent

On an agent's Build tab, the Tools row of the rail lists what the agent can do: the abilities its connected apps give it, each with the app's logo, then its other tools. A dot marks an app that needs fixing.

Add tool on that row opens Add a tool. Its App step asks what the agent should be able to do. Add tool then Connected app on the agent's Tools page opens the same step:

  • a switch for each job whose app is connected;
  • Fix for a job whose app needs attention;
  • Set up for a job with no app yet.

Fix and Set up open the job on the Connected apps page.

The agent's Tools page also shows each connected app, with the same ability switches and every action the app offers.

An app whose sign-in expired, or was started and never finished, stays on the Tools page marked Sign in, because the agent can't use it on calls until it is fixed. Opening it offers Sign in to the app, which brings you back to the agent when you're done, or Remove from this agent.

Where a connection lives

A connection is recorded at one of two scopes.

Workspace connections

The Connected apps page connects at the workspace. A workspace connection is an offer, not a default. Agents use it only once you switch them on in Choose agents or in the app's sheet, and until then they load nothing from it.

Agent connections

An agent connection is that agent's own account for the app, with its own authorisation. This lets two agents in the same workspace use two different calendars or two different inboxes under the same service. Agent connections are made through the REST API or an assistant connected over MCP.

What the runtime loads

At call time the runtime loads only the agent's own enabled, active connections. A pending connection, a disabled one, or a workspace connection the agent was never switched on for contributes nothing to the call.

Exact actions

Under the abilities, every connection carries the list of actions the agent may call. It has three states.

SelectionEffect
Not setThe agent loads the provider's recommended subset for that app.
A listThe agent loads exactly those actions and nothing else. Setting up an app through the sheet writes this list from the abilities you chose.
EmptyThe agent loads none of the app's actions. The connection stays in place.

Zoho Bookings

Zoho Bookings is a Vertical AI-built integration. It appears in the catalogue and when you search for Zoho or for bookings. Connecting it authorises a Zoho account with booking permissions and gives the agent two fixed actions.

ActionWhat it does
Get available slotsReads open appointment times on the business's Zoho calendar for a given day. The agent calls this before offering a time.
Book appointmentBooks an appointment at a time the caller chose. The agent collects a name and email address first.

The agent reaches Zoho in the data centre the account was connected in.

When a connection fails

Opening the Connected apps page re-checks, with our connection broker, the health of each connection not checked in the last five minutes. An account that expired or was revoked shows as Signed out rather than silently failing on a call.

If a connection fails mid-call, the agent does not invent a result. The action returns a short message telling the model the app is not connected, and the model recovers in the conversation, the same way any other tool failure is handled. See tool errors are instructions.

On this page