Connected apps
Connect a third-party service so the agent can act in it during a call, and choose exactly which of its actions the agent can use.
A connected app is a third-party service the agent can act in while a call is running.
- Connect your calendar and the agent can read open times.
- Connect your CRM and it can create a contact.
You write no URL, no method and no parameters for any of this. You connect the account once, then pick which of the app's actions the agent is allowed to call.
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.
The catalogue
The catalogue holds over a thousand applications. Filter it by keyword or by category.
How many actions an app has
Each entry shows how many actions the app exposes. A small utility exposes a handful of actions; the largest exceed eight hundred.
Which of them the agent actually loads is your choice, and it matters for call latency. See choosing which actions an agent gets.
Connecting an app
You connect an app from the agent that will use it.
- Open the agent's Tools page and choose Add tool.
- Choose the App category. The catalogue opens. Search for the service by name.
- Press Connect on the app. For an app that needs no authentication the button reads Add and there is nothing further to do.
- Finish the sign-in in the window that opens. You are approving access on the service's own site, not on ours.
- Back in Meddle, pick the actions this agent should be able to call, and save.
How the app authorises
Apps differ in what they ask for at step 3. App authorisation covers the four connect kinds, including the apps that need an OAuth application of your own.
After the sign-in
The authorisation window times out after 60 seconds. If it expires, close it and press Connect again.
Once the sign-in completes the connection goes active for that agent. Its actions appear in the agent's tool list alongside its builtin and webhook tools, and the model chooses between all of them the same way.
Connecting a new app requires workspace admin access, because the connected account is billed to the workspace.
Where a connection lives
A connection is recorded at one of two scopes.
Workspace connections
A workspace connection is available to every agent in the workspace, but it is not switched on for any of them. It is an offer, not a default.
Connecting your CRM at the workspace does not silently hand every agent a set of write-capable CRM actions. Each agent has to opt in, and until it does the agent loads nothing from that app.
Agent connections
An agent connection is that agent's own account for the app, with its own authorisation. This is what lets two agents in the same workspace use two different calendars, or two different inboxes, under the same service. Connecting from an agent's Tools page creates one of these.
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 bare workspace connection the agent never opted into contributes nothing to the call.
Choosing which actions an agent gets
Every connection carries a list of the actions the agent may call. It has three states.
| Selection | Effect |
|---|---|
| Not set | The agent loads the provider's recommended subset for that app. This is the default and it is deliberately small. |
| A list | The agent loads exactly those actions and nothing else. |
| Empty | The agent loads none of the app's actions. The connection stays in place. |
Keep the list short
Every action loaded becomes a tool description the model reads on every turn, so loading a whole eight-hundred-action platform makes the agent slower and less reliable at picking the right tool. Pick the handful the agent genuinely needs.
Seeing what the agent will load
The agent's Tools page shows the selected actions as individual rows under the app. Browsing an app's full action list, rather than the recommended subset, is available from the same panel.
Zoho Bookings
Zoho Bookings is a Meddle-built integration. It appears at the top of the catalogue when you browse it, 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.
The two actions
| Action | What it does |
|---|---|
| Get available slots | Reads open appointment times on the business's Zoho calendar for a given day. The agent calls this before offering a time. |
| Book appointment | Books an appointment at a time the caller chose. The agent collects a name and email address first. |
Connections default to the Australian Zoho data centre.
Reviewing and revoking
Settings then Connected apps lists every connection across the workspace in one place, with the app, whether it is workspace-wide or scoped to a named agent, its current health, and a Revoke action.
Opening the list re-checks each connection's health against the authorisation provider, so an account that expired or was revoked at the service shows as failed here rather than silently failing on a call.
Revoking a connection removes it from every agent using it. New apps are connected from an agent's Tools page rather than from this list.
When a connection fails
If a connection fails mid-life, 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.