Claude item connectorWhat Claude can do in your item account.
The Claude item connector exposes 22 tools. 11 read your CRM, from records to saved views and notes, and 11 write: objects, lists, notes and tasks. Below: what Claude reaches in item, what item keeps out of the connector on purpose, and where two sources disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can work in your CRM
Before a call, you open item, search the company, scroll the timeline, check the deal and read the last notes. With the connector, you ask Claude "where are we with this account?" and it pulls contacts, companies, deals, notes and history itself. After the call, it can log the note, move the deal forward and set the follow-up task, all from the same conversation.
Prepare a meeting in one question. ask_item_assistant hands complex requests to item's own assistant in read-only mode: synthesis across emails, meetings, recordings and timelines. search_objects and get_object handle precise lookups when you already know what you want.
Keep records current without retyping. update_object changes fields on a contact, company or deal, create_note attaches the meeting summary to the right record, and create_task schedules the follow-up for a teammate or for item's AI.
Work from your saved views and lists. execute_view runs a saved view with its filters and sorting, and add_to_list drops an account into the right list for a campaign.
What it won't do, by item's own choice: no external messages, no calendar writes, no Slack or LinkedIn sending, no enrichment that could spend credits, no raw SQL and no bulk changes through the connector. And nothing happens unprompted: Claude only touches the CRM when you ask in a conversation. Updating a deal every time a form comes in is automation work, a different job; the Integrations hub gathers that side.
The vocabulary in one minute
Five words you will see while plugging item into Claude.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in it while answering you.
- Tool
- One named action a connector opens to Claude. Claude decides which to use as it answers; the directory lists them by name.
- Authorization
- The service's own sign-in screen, where you give Claude the access it will use afterwards. Granted once per person, revocable.
- Approval
- The confirmation Claude waits for before finishing something that changes your account, shown in the conversation at that moment.
- MCP
- The common standard connectors rely on: it is what lets an assistant like Claude talk to an outside service.
Plug item into Claude in three steps
- 01
Find item in Claude
In Claude's settings, open Customize, then Connectors, and look for item. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before each member connects their own CRM account.
- 02
Sign in to item
Click Connect on its row; item opens its authorization page in your browser. Sign in with the item account Claude should use. If the link breaks later, Disconnect and connect again.
- 03
Review the access requested
Read the screen before you allow it. It is item's, not Claude's, and it sets what the access covers. You can also remove that access later from the item side.
The 22 tools, sorted by what they do
item gives Claude 22 tools: 11 that read your account, 11 that change something in it.
Two groups: what Claude reads and what it changes in your CRM. Tool names stay in English, as Claude shows them.
- 11 read
- 11 write
What Claude reads (11)
11 toolsEleven tools that look up records, views, lists, notes and tasks without altering them.
ask_item_assistant
Hands a natural-language question to item's own assistant, in read-only mode, for requests that need analysis or synthesis across object types, emails, meetings, recordings and timelines. A thread ID keeps follow-ups in the same conversation.
search_objects
Runs a structured, read-only search over CRM objects by query, object type, field or relationship, with a limit and an offset to page through results.
get_object
Fetches a single CRM object from its type slug and its ID.
list_object_types
Lists the active system and custom object types of your organization, so Claude knows the exact type names before searching.
get_object_schema
Returns the field definitions of one object type. item recommends calling it before any field-level work, so Claude targets fields that actually exist.
list_views
Shows the saved views of an object type, with their filters, columns, sorting and view type, so Claude can pick the right one.
execute_view
Runs a saved view and returns its records already filtered, sorted and paginated, exactly as the view defines them in item, page after page.
list_lists
Browses the lists available in your organization, with an optional filter by name or object type.
get_list
Returns a list's details along with its member records, once Claude has the list ID from list_lists.
search_notes
Looks through the notes attached to CRM records and returns the ones that match.
search_tasks
Finds tasks by status, by scheduled, created or completed dates, by assignee, by linked objects or by free text. item recommends it to pin down a task's ID before update_task or delete_task acts on it.
What Claude changes (11)
11 toolsEleven tools that create, edit or remove CRM data. Only delete_task has a confirmation described by its source; the others fall under the general rule below.
create_object
Approval: see the ruleAdds a new CRM object, such as a contact, company or deal, with the field values you give.
update_object
Approval: see the ruleChanges fields on an existing CRM object identified by its type and ID.
delete_object
Approval: see the ruleRemoves an existing CRM object identified by its type and ID.
create_list
Approval: see the ruleSets up a new list for a given object type, ready to receive records.
add_to_list
Approval: see the rulePuts a contact, a company or a custom object into an existing list.
remove_from_list
Approval: see the ruleTakes a single object out of a list, one object per call.
create_note
Approval: see the ruleAttaches a new note to a CRM record, for instance the summary of a call or a meeting.
edit_note
Approval: see the ruleRewrites an existing note on a record.
create_task
Approval: see the ruleSchedules work for a person or for item's AI, whether immediate, scheduled, reactive, recurring or blocked.
update_task
Approval: see the ruleCompletes, cancels, reassigns or reschedules a task, adds notes, links objects, or resumes a blocked AI task with new context.
delete_task
Asks you firstRemoves a task from item. The publisher describes it as running only after confirmation.
What Claude asks before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. The request shows up in the conversation when it matters.
On Team and Enterprise, workspace owners decide whether members can let some actions pass without being asked again. They can also cap what a connector does for the whole organization, keeping CRM lookups open while closing every change, for instance; nobody gets around that from their own account. Claude works with the rights of the person who connected and nothing more. On the publisher's side, the tools you see also vary with your permissions and with the integrations hooked up to your account.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. Connector by connector, the answer isn't published anywhere: it's a genuine hole in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner turns the connector on for the organization first. The publisher's guide says something more specific, set against this rule in the limits section. For the current state on your account, check the item sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; nothing changes in the CRM when a deal closes or a contact replies.
The tool list is an observed floor, not a promise: an administrator can open actions that appear on no public sheet. The directory badge isn't a security audit, and Anthropic says on every sheet that it doesn't choose the tools a publisher exposes or guarantee they behave as described. Plug in what comes from a publisher you know. This connector is documented by item alone, with no Claude help article.
On which plans can Claude use the item connector?
- Claude help center, general connector rule ↗September 2026Remote connectors are open to all users; on Team and Enterprise, an Owner must first enable each one.
- item MCP guide ↗June 2026The publisher describes adding item as a custom connector "for Pro or Max plans", with an Owner step for Team and Enterprise.
What this page followsAnthropic's rule covers every connector; item's older page (June 2026) describes adding a custom connector by hand and names plans in that context, while item now has its own sheet in the directory. Neither settles it for your account: check the item sheet in the directory on your own account.
Need help connecting item to Claude?
A person reads every message.
