Claude Introhive connectorWhat Claude can do in your Introhive account.
The Claude Introhive connector exposes 1 tool. That one tool reads, 0 write anything, and 0 are left undocumented. Below: what Claude can ask your firm's relationship data, what stays out of reach, and who holds the keys.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can query Introhive
Before a pitch, someone usually digs through Introhive by hand to find who at the firm actually knows the client. With the connector, you type the question to Claude instead, and it pulls the answer from your firm's relationship data: contacts, meetings, email patterns and engagement scores, summarized right where you are working.
A warm path to a prospect. Ask who in the firm is best placed to introduce you to a target executive, and why. Claude sends that question to ask_introhive and comes back with the colleagues and the strength of their ties.
A brief before the meeting. A partner wants the last few interactions with a company summarized before walking in. Same tool, and the summary lands in the chat, with meetings and email history behind it.
An early warning on accounts. Introhive's own description of the connector names pinpointing at-risk accounts among its uses. You ask, and the answer comes back from engagement trends rather than from memory.
What it will not do matters as much. Introhive states the tool cannot create, change or delete a record. It has no access to revenue, deals, pipelines or contracts, cannot cross-check a CSV you upload into the chat, and does not draw on industry fields. Nothing runs on its own either: no alert fires when a score drops, Claude only looks when you ask. For flows that react by themselves, you need an automation tool, a different job; the Integrations hub lists that side.
Five words to know first
The Claude vocabulary this page uses, in under a minute.
- Connector
- A link you set once between Claude and an account you already hold, so Claude can work in that account while it answers you.
- Tool
- One named action a connector gives Claude. Claude chooses which tools to call by itself, and the directory sheet lists them by name.
- Authorization
- The service's own sign-in screen, where you hand over the access Claude will use. Granted once per person and revocable.
- Approval
- The confirmation Claude waits for, inside the chat, before it does something that would change your account.
- MCP
- The open standard connectors are built on: it is what lets an assistant such as Claude talk to an outside service like Introhive.
Connect Introhive to Claude in three steps
- 01
Find Introhive in Claude
Open Claude's settings, then Customize and Connectors, and look for Introhive in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch the connector on before each member can sign in.
- 02
Start the connection
Press Connect on the Introhive row, then sign in with your own Introhive credentials in the window Introhive opens. If the link breaks later, use Disconnect and connect again from the same row.
- 03
Check the authorization screen
Read the screen Introhive shows before you accept. It belongs to the service, not to Claude, and it decides what the access covers. You can withdraw that access later from the Introhive side as well.
The one tool, and what it reads
Introhive gives Claude 1 tool: 1 that read your account, 0 that change something in it.
A single tool carries the whole connector. Its name stays exactly as Claude shows it.
- 1 read
What Claude reads (1)
1 toolOne tool that queries your relationship data and leaves every record untouched.
ask_introhive
Takes a question in plain language and answers it from your firm's relationship data: who knows whom, how strong those ties are, recent meetings, email patterns and network paths.
What Claude checks with you first
By default, Claude pauses and asks before any action it takes on an account in your name. Here the only tool reads, and no source describes a confirmation specific to it.
On Team and Enterprise workspaces, owners decide whether members may let certain actions run without a prompt each time. They can also restrict what a connector may do for the whole organization, and nobody overrides that from a personal account. Claude works with the rights of the person who signed in: Introhive says access mirrors what that person sees in its web app, with minor differences at the edges.
Which plans include it
None of the 819 sheets in the official directory shows plan availability, so the answer per connector is published nowhere.
The published rule is general: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables a connector for the organization before members can each connect. The Introhive sheet in the directory is the only place showing its live state.
Where this connector stops
Claude calls the tool while it answers you. Nothing starts by itself when a score falls or a meeting is logged.
Everything known here comes from Introhive's own guide: no Claude help page covers this connector. By default its sheet exposes reading only, and a tool list is an observed floor rather than a promise, since an administrator can open actions that no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet it neither picks a publisher's tools nor guarantees how they behave.
Need help connecting Introhive to Claude?
A person reads every message.
