Connectors
A connector is how an agent reaches one of your company’s systems. Each connector gives the agents it is granted to a set of tools — search a mailbox, look up an order, create a record — and the agent calls those tools while it works a task, the same way it uses the browser on its computer.
You add connectors yourself. Open Connectors from the sidebar: your own connectors are listed at the top, and Add a connector below offers ready-made ones that AptiveAI hosts and keeps up to date. Pick one, sign in, and it is yours; your team then decides which agents may use it.
Adding a connector
Section titled “Adding a connector”Add a connector shows what it offers as one grid of tiles, with a search box. The box suggests the categories below; Show or Hide one to narrow the tiles:
| Category | Connectors |
|---|---|
| Email & calendar | Outlook, Gmail, Google Calendar |
| Files & docs | Google Drive, OneDrive, DocuSign |
| Messaging | Microsoft Teams, Slack, Twilio SMS, Telegram, AptiveAI Messaging |
| Work tracking | Trello |
| Advanced | Custom MCP server, HTTP API, and the Browser workflow tile that starts a new one |
Browser workflows your team built, or that AptiveAI published to your company, come first in the grid, ahead of every category.
Clicking one opens a panel with what it does, the tools it brings and how it signs in. A hosted connector signs in with the provider itself — Sign in with Microsoft, Google or Slack, where the provider’s own page asks you to choose the account and AptiveAI never sees your password — or takes a token or key you paste in (Trello, Telegram, Twilio SMS). The panel also asks:
- Name — optional. Shown on its pills as “Outlook · Work”; left blank, the connector is named after the account. Connect a second account of the same kind to have two.
- Who can use it — Change… opens the share box. It starts private; Everyone in ‹workspace› is for owners and admins.
- Workspace — only if you are in more than one workspace: where the connector lives. Your main workspace is chosen unless you pick another.
Connect finishes it, and the connector’s tools are read from the service. Owners and admins can add a connector for the whole workspace; anyone can add one for themselves.
To let agents text or email people outside AptiveAI Agents — drivers, customers, suppliers — an owner of your enterprise turns on AptiveAI Messaging, a connector AptiveAI runs for you: email is included in your plan (up to 250 a day), texts are charged to your enterprise wallet.
Kinds of connector
Section titled “Kinds of connector”| Kind | What it connects |
|---|---|
| Hosted connectors | The ready-made services above. AptiveAI hosts the connector and its server, and keeps its tools up to date — see Server versions |
| Custom MCP server | Any server that speaks the Model Context Protocol over Streamable HTTP — a vendor’s official one or an open-source one. Its tools are read from the server when you connect |
| HTTP API | Any API described by an OpenAPI 3 document: one tool per operation |
| Browser workflow | A website with no API, taught to your agents once — see Browser workflows |
Custom MCP server
Section titled “Custom MCP server”Give it a Name, the Server URL and the Authentication it uses: none,
an API key sent as Authorization: Basic, Authorization: Bearer or a
custom header, or The server’s own sign-in, for a vendor’s hosted server that
sends you to its sign-in page. A server that does not say how to sign in, is not
served over https, or does not meet the sign-in’s security requirements is
refused with a message saying which.
HTTP API
Section titled “HTTP API”An HTTP API connector is built from the API’s own description. Its schema comes
either from a URL (fetched over https, reachable without a credential) or
from a pasted document in JSON or YAML — the format is detected. The
connector calls the API at its Base URL (the document’s first server when
left blank), authenticating with an API key sent as Authorization: Basic,
Authorization: Bearer or a custom header, or with none.
Connecting imports every operation as a tool. When the API changes, the connector is re-imported and its tools reclassified.
Reads, writes and approval
Section titled “Reads, writes and approval”Every tool is either a read or a write. A read goes ahead as soon as the agent calls it. A write — anything that changes something in your system — stops the task and asks first.
How a tool is classed, in order:
- A choice made by hand on the connector wins (shown as Set by hand).
- Otherwise the API document’s own flag for a consequential operation decides.
- Otherwise the HTTP method decides:
GET,HEAD,OPTIONSandTRACEare reads; everything else is a write.
When the agent reaches a write, the task shows an approval card — This agent is about to change something in a connected system, so it is waiting for you — naming the connector and the tool, and what it will send. You answer with:
| Button | Effect |
|---|---|
| Approve | Run this call once, then carry on |
| Approve all | Run this, and stop asking for the rest of this task |
| Decline | Skip this call and tell the agent why — the card has a box for what to do instead |
How much a task may do before it asks is its approval level.
Approving a write to a connector covers every later write to that same connector for the rest of the task, not just that one operation.
Ids the agent did not make up
Section titled “Ids the agent did not make up”A connector checks every id an agent passes to it — a message id, an order number. The id must be one the connector itself returned earlier in the same task, or one a person typed into the conversation. Anything else is not sent, and the agent is told to look the id up again. This stops an agent acting on an id it guessed or mistyped.
Files a connector returns
Section titled “Files a connector returns”When a connector answers with a file, or with a result too large to hand the agent whole, the file is kept with the task and the agent is given its path and a preview. It can then open or process the file on its computer like any other. Size limits and how long such a file is kept are in Files.
Data is never cut in the middle
Section titled “Data is never cut in the middle”What a connector returns reaches the agent whole, or the agent is told it did not:
- A large result is kept as a file rather than trimmed, and the agent reads what it needs from that file.
- It works out totals and counts from the data itself, with code, rather than retyping figures or adding them up in its head.
- If part of a result could not be kept, the agent is told — and stopped from sending anything that depends on it. What you see in the transcript is described in When a connector’s data comes back incomplete.
The detail, including how a file you need later is brought back, is in Files a connector returns.
Status
Section titled “Status”| Status | What it means |
|---|---|
| Connected | Working. Agents granted it can use it |
| Reconnect | Its sign-in or key was rejected. Use Sign in again (or Enter a new key) on its panel; agents using it fail until then, and the workspace is notified |
| Unavailable | The system could not be reached. It is tested again automatically whenever a task starts |
| Not connected | Added, but not connected yet |
A server error or one bad call does not mark a connector as needing reconnection — only a rejected sign-in or key does. A connector made from a browser workflow shows an error instead when its workflow was deleted or is no longer available to your company.
When a task starts while a connector is broken, its tools are held back from that task and the transcript says how many granted tools are not available.
Server versions and Refresh tools
Section titled “Server versions and Refresh tools”A hosted connector runs on a server AptiveAI looks after, and that server is released from time to time. Its release is shown beside hosted by AptiveAI on the connector’s entry — for example v0.1.1 — with the day it was deployed.
A connection keeps the tools it read when you connected it. When the server moves on, the connector’s panel tells whoever manages it: Outlook’s server was updated to v0.1.2. This connection’s tools may be from an earlier release. Review its tools to pick up any changes. — or, for a rebuild of the same release, …was redeployed on ….
Refresh tools reads the server’s tools again and shows what would change — tools Added, Removed or Changed (their description, name, inputs, paging, or whether they read or write) — or The stored tools already match the server. Nothing changes until you press Apply changes; if the server changed while you were reviewing, you are shown the new comparison first. An agent granted a removed tool can no longer call it. A new tool that writes is marked writes, asks first.
The Connectors page
Section titled “The Connectors page”The list shows each Connector with its Status, who can use it (Access) and who it was Made by, with a filter box. A person in more than one workspace also gets a Workspace column and a Workspace filter, to narrow the list to one.
Click a connector to open its panel:
- Made by — who added it, and where it lives.
- Settings — for a connector with settings, such as a browser workflow’s site address.
- Tools — each marked as a read or as Writes — asks first (Set by hand when someone chose that for it), with the tools each agent may use.
- Used by — every agent granted it, and whether the grant is Enabled or Off. A deleted agent keeps its grant and is listed last with a Deleted badge, so recovering it brings it back equipped. Grants are changed in the agent’s own builder, not here.
- Who can use it — the share box.
- Actions: Name…, Test connection (Check it still answers), Sign in again or Enter a new key, Disconnect (Remove it for everyone using it) and, for a browser workflow’s connector, Edit browser workflow.
Test connection shows whether it Works or Didn’t work, what was performed, how long it took and how many tools it found, and what to do next when it fails.
A connector you can use but not change shows You can use this connector. Only someone who can edit it can change it.
Available to personal agents
Section titled “Available to personal agents”Each connector carries an Available to personal agents switch. A personal agent may only be granted connectors that have it on. Turning it off takes the connector away from every personal agent at its next task; the grants are kept, so turning it back on restores them.
Who may do what
Section titled “Who may do what”| Action | Who |
|---|---|
| See a connector, its status and tools | Everyone it is shared with, and its owner |
| Add a connector for yourself | Everyone |
| Add a connector for the whole workspace | Owners and admins |
| Change its name, settings or sign-in, test it or disconnect it | Whoever can edit it: its owner and people it is shared with as editors |
| Grant a connector to an agent | Owners and admins |
| Turn Available to personal agents on or off | Owners and admins |
| Build, change, publish or delete a browser workflow | See that page |
Granting a connector is also one of the actions that needs paid access.