Connectors in Vibe
How Vibe finds a tool in a connected app, which connectors a chat is allowed to touch, and what it asks you before running anything.
Once an app is connected, Vibe can act in it: post to a Slack channel, read a brief out of Notion, drop a file in Drive. This page is about what Vibe does with a connector during a chat. Connecting and disconnecting apps is on Connectors.
Vibe reaches your apps through one skill, connectors, which has exactly two
tools:
Prop
Type
There is no third tool. Anything Vibe does in Slack, Gmail, or Drive is a
runTool call against a slug that searchTools returned.
What Vibe is allowed to touch
Vibe never sees your whole connector catalogue. The set it can use is worked out per chat:
/connectors.If the chat belongs to a project, keep only the connectors that project enabled.
If the chat does not belong to a project, keep everything you connected.
If that leaves nothing, both tools return no_connectors and Vibe tells you to
connect an app rather than trying something else.
A project's list is set in the Connectors section of its workspace rail, and
is stored per project. The app reads it from GET /api/projects/{id}/connectors
and saves it with PUT to the same path. Your account-wide list comes from
GET /api/connectors.
Project scope is the real boundary
A chat inside a client project cannot reach a connector that project has not enabled, even though the account is connected to it.
How a request runs
Vibe searches before it runs, every time. It is not allowed to guess a tool slug, because slugs and their argument schemas come from the app, not from Klipeo.
You ask for the outcome in plain words, such as posting an export link to a channel.
Vibe calls searchTools with a description of that outcome. The panel shows
"Searching connected apps".
It reads the schema of the best match and fills only the fields that schema defines.
It asks you to approve the run, then calls runTool. The panel shows
"Running" and the slug.
It reports back in a sentence or two, with whatever link or id the app returned.
Approvals
runTool always stops for approval. Reading is not exempt.
| Tool | Approval | Why |
|---|---|---|
searchTools | Never asks | It only looks up tool definitions, it does not touch your data |
runTool | Always asks | Classified as an external publish, the same gate as uploading to YouTube or TikTok |
The reason is that Klipeo cannot tell from a slug what an app tool will do. A
single runTool call can send, post, delete, or share, so the gate is applied to
the tool itself rather than to a guess about its intent. The approval card gives
you Approve and Skip; Skip declines that step and lets the turn carry on.
Check the destination, not just the action
The approval is your only chance to catch the wrong channel, the wrong recipient, or the wrong document. Read the arguments on the card before you approve.
Connecting from the composer
You do not have to leave the chat to connect an app. Open the plus menu in the Vibe composer and pick Connectors. The row reads "N connected", or "YouTube, TikTok, Drive, and more" before you connect anything.
You can also type @ in the composer. The connector palette shows every
available app with connected apps first. Pick a connected app to add it as
explicit context for the request, or choose Connect beside another app to
open its consent screen. Start typing after @ to filter the list; arrow keys
and Enter work the same way as the / Skill palette.
The submenu has a Search connectors box, a row per app with either a
Connected pill or a Connect action that opens the provider's consent
screen, and a Manage connectors link to /connectors at the bottom. The same
list appears as taller plain rows in the phone bottom sheet.
Limits and failure states
Vibe itself needs an active paid plan, so connector actions are only available to paid accounts. Connector runs do not spend credits on their own; the model tokens spent deciding and calling are metered like any other Vibe work. See Credits & Billing.