This article is auto-synced from its in-app version in Tai.
Preview. Connectors are in preview — available to companies in the preview program, and still evolving. Building and test-driving connectors in the Connector Lab is currently limited to system administrators; it will open up more widely as the preview matures.
Connectors give your agents access to external systems — your booking data, flight APIs, and other services your company uses.
When you'd use this
Connect an agent to live data from an external source so it can answer from real information instead of general knowledge — for example, looking up booking details or checking live flight status. Ask the Connector Builder to create one by describing the system in plain language, or browse the connectors already configured for your company.
Steps
Browse connectors
In the Workbench sidebar, open Connectors, then All Connectors.
The catalogue lists every connector available to your company — built-in connectors (managed by Nezasa) and any custom connectors your company has built.
Use the search bar or the Ownership, Status, or Type filters to narrow the list.
Click a connector name to open its detail page, where you can see its type, description, and which agents are using it.
Build a connector with AI guidance
In the sidebar, open Connectors, then All Connectors or Connector Lab.
Click Create connector, give it a name and an optional one-line description, and continue — you land straight in the Connector Builder.
In the Builder chat, describe the system you want to connect (a REST API, a database, a reporting feed). The assistant proposes a plan for your approval before it generates anything.
If the target needs authentication, enter the values the assistant asks for in the Builder's Credentials panel — they're saved against this connector and are never shared in the chat.
The assistant self-tests every operation against the real target, then submits the finished connector for verification automatically (contract, egress, and intent checks). When the verification report appears next to the chat, review it and click Activate to make the connector live.
If what the assistant built no longer matches the name or description you gave the connector, the review panel offers the corrected text — click Update connector to apply it. Nothing you typed is changed unless you click.
An activated connector can fetch data but can't yet write to your systems.
Test-drive a connector
In the sidebar, open Connectors, then Connector Lab.
Select an active connector from the picker — its credential status shows as configured or not.
Click Start test drive and ask the chat a question that needs the connector's data. Each call the connector makes shows up in the invocation trace alongside the chat.
Assign a connector to an agent
In the sidebar, click Agents and open the agent you want to update.
On the General tab, find the Connectors field.
Select one or more connectors from the picker.
Click Save changes.
Tips and limits
An agent can only query connectors explicitly assigned to it — there is no implicit access to other connectors.
Custom connector code never runs inside the TAI application itself. It executes in a separate, sandboxed runtime with strict time and resource limits. The code does not call external services itself: it hands each request back to TAI, which checks it against the hosts the connector declared and makes the call on its behalf.
Connector credentials are managed securely and are never exposed to agents or users directly — not even to the connector's own generated code: TAI attaches credentials at call time, outside the sandbox.
A connector built through the Builder keeps its own credential values, separate from the shared provider credentials under Settings → Credentials — see Credentials.
Some skills declare required connectors. If you assign such a skill to an agent, you must also assign its required connector.
Preview features may change as they evolve toward general availability.
Related