Claude Sybill connectorWhat Claude can do in your Sybill account.
The Claude Sybill connector exposes 5 tools, 5 in read and 0 in write. Claude asks Sybill AI about your calls, lists and opens meetings with their transcripts, and filters CRM deals. Here is what it reads, what it leaves alone, and how far your access goes.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query Sybill
Sybill's directory description presents it as the context layer for a revenue team: calls, deals and pipeline, grounded in transcripts, summaries and CRM data. With the connector, you ask Claude. It searches your recorded conversations and CRM deals through Sybill, reads the summary or the transcript it needs, and answers within the calls and deals your own login can open.
Walking into a meeting prepared. Claude finds the relevant calls through list_conversations, filtered by attendees, dates or CRM deal, then pulls the summary, transcript and participants of the latest one with get_conversation.
Spotting deals that slip. With list_deals, Claude narrows the pipeline by stage, owner, close date or last activity, and get_deal brings back the contacts, owner and stage of the one that worries you.
Asking a broad question in one go. ask_sybill hands a plain question to Sybill AI, about your calls, deals, people or companies, and returns its answer.
What it will not do: the directory sheet shows no tool that edits a deal, logs a note or schedules anything, and nothing runs by itself when a call ends; Claude works only while it answers you. Sybill's documentation also names a few more tools than the directory sheet lists. The Claude connectors hub gathers the other sales connectors, and the Integrations page covers automation platforms.
Five words before you connect
The Claude vocabulary behind this connector, in one minute.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work with it while it answers you.
- Tool
- One named thing the connector lets Claude do on that account. Claude picks the ones it needs, and the directory lists them by name.
- Authorization
- Sybill's own sign-in screen, where you give Claude the access it will use afterwards. Granted once per person, and it can be withdrawn.
- Approval
- The confirmation Claude waits for before it goes ahead with something that changes an account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service such as Sybill.
Connecting Sybill to Claude in three steps
- 01
Find Sybill in Claude
Open Claude's settings, go to Customize then Connectors, and search for Sybill. On a Team or Enterprise workspace, an Owner or Primary Owner first enables the connector so each member can then sign in with their own account.
- 02
Start the connection
Click Connect on its row. Sybill opens its own window and asks you to sign in with your Sybill account. If the link breaks later, use Disconnect, then connect again: that is usually enough.
- 03
Read the authorization screen
Check Sybill's authorization screen before you accept. It belongs to Sybill, not to Claude, and it sets what the access covers. You can also take that access back later from the Sybill side.
The 5 Sybill tools, sorted by what they do
Sybill gives Claude 5 tools: 5 that read your account, 0 that change something in it.
All five consult your Sybill data, and Sybill's API documentation describes each one. Names stay as Claude shows them.
- 5 read
What Claude reads (5)
5 toolsFive tools that look up calls, transcripts and deals without changing them.
ask_sybill
Passes a question in plain words to Sybill AI, which can draw on your calls, deals, people, companies and emails, then returns its answer. A short question usually comes back at once; a longer one may come back marked as still running.
list_conversations
Brings back the recorded meetings your login can see, page by page, and narrows them by date range, meeting type, title, attendees, or the CRM deal they belong to.
get_conversation
Opens one meeting in full: its summary, the transcript, recording links, the participants and the CRM information attached to it when Sybill has them.
list_deals
Pages through the CRM deals your account can access, filtered by name, pipeline stage, open or closed status, owner, close date, amount range or date of last activity.
get_deal
Reads a single deal in detail, returning its summary, linked contacts, owner, pipeline and current stage whenever Sybill holds that information.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before any action it takes on an account in your place. The approval shows up in the conversation at the moment it matters.
On Team and Enterprise workspaces, owners decide whether a member may let some actions through without being asked again. They can also limit what a connector may do for the whole organisation, keeping reads and closing writes for instance, and nobody overrides that from their own account. Claude also works with your rights and nothing more: Sybill's documentation scopes conversations and deals to what is available to the signed-in user, so a call you cannot open stays closed to Claude.
Which plans include it
None of the 819 sheets in the official directory displays availability by plan. Connector by connector, the answer is published nowhere: it is a real gap in the catalogue.
What is published is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organisation before each member signs in. For the current state of this one, check its sheet in the official directory. Note that only Sybill documents it; no Claude help article covers it.
Where the Claude Sybill connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing fires when a call is transcribed or a deal changes stage.
The tool list is an observed floor, not a promise: an administrator can open actions that no public sheet shows. By default, this sheet exposes reads only. The partner badge in the directory is not a security audit, and Anthropic states on every sheet that it does not choose the tools a publisher exposes and cannot guarantee they behave as announced. Connect only what comes from a publisher you trust, here Sybill itself.
Need help connecting Sybill to Claude?
A person reads every message.
