add_to_list
ChatGPTAdd a contact, company, or custom object to a list
ask_item_assistant
ChatGPTAsk the Item assistant a natural-language question in read-only mode. Prefer this tool for complex requests that require analysis, multi-step reasoning, synthesis across object types, emails, meetings, meeting recordings, timelines, or a large number of CRM objects. Use the direct structured tools only for simple deterministic lookups or explicit internal Item mutations. Thread continuity is important: if a previous ask_item_assistant response returned thread_id, always pass the most recent thread_id on every follow-up so the Item assistant can continue the same conversation. Omit thread_id only when intentionally starting a brand-new Item assistant thread.
create_list
ChatGPTCreate a new list for organizing Item objects of a single object type. Requires a name and the object type slug, with an optional description. Members are added separately with add_to_list.
create_note
ChatGPTCreate a new note
create_object
ChatGPTCreate a new object in the system. objectSlug is required, and include all field values for the object. Duplicate guard for contacts and companies: before calling this tool, search internally for an existing record. If you used enrichment, search internally AGAIN using enriched identifiers such as domain, website, email, company name, or LinkedIn URL, and only create if that second search still finds no clear match.
create_task
ChatGPTCreate a task in Item, assigned to a teammate or to the Item AI. A task runs immediately by default, at a future datetime when scheduled_for is set, or in response to an event (received email, calendar event, record change, webhook, or form submission) when a trigger is set. scheduled_for and trigger are mutually exclusive; a multi-step workflow with dependent steps belongs in a single task with one planned_steps entry per action.
delete_object
ChatGPTDelete an existing object in the system. id and objectSlug are required.
delete_task
ChatGPTDelete a task. Always asks for the user's confirmation before deletion. This action cannot be undone — there is no UI to restore deleted tasks via the assistant.
edit_note
ChatGPTEdit an existing note. For title or content, provide both the exact value you read and its replacement; a newer human edit returns a conflict.
execute_view
ChatGPTExecute an accessible saved Item view with its configured filters, sorting, and columns. Results are paginated.
get_list
ChatGPTGet details for one Item list along with its member records, including the full field data for each member. Supports limit and offset for paginating large lists. List IDs come from list_lists.
get_object
ChatGPTFetch one item CRM object by object_slug and object_id. Returns the same object shape as search_objects.
get_object_schema
ChatGPTGet field definitions for one item object type by slug. Use before constructing structured filters, field-aware UI, or performing field updates.
list_lists
ChatGPTBrowse available lists for the organization. Supports optional search by name and filtering by object type slug.
list_object_types
ChatGPTList active system and custom object types available to this item organization. Call this tool before searching for objects to get the list of available object types.
list_views
ChatGPTList all saved views for an object type. Views are pre-configured filters, columns, and sorting that users have saved. Use this to discover available views before executing them with execute_view.
remove_from_list
ChatGPTRemove a single object from a list. Requires the list ID, object ID, and object type ID.
search_notes
ChatGPTSearch for notes
search_objects
ChatGPTStructured read-only search over Item CRM objects. Use for deterministic object lookup by query, object type, field, relationship, limit, and offset.
search_tasks
ChatGPTSearch the user's tasks by status, scheduled/created/completed dates, assignee, associated objects (contact, company, custom object), and an optional free-text query string. Internal lookup tool — the result is consumed by the model only. This tool DOES NOT render a card. Do NOT summarize the result back to the user as a list, table, or bulleted enumeration — the search is a programmatic lookup, not a user-facing display. When to use: - Use search_tasks whenever you need to look up a task to act on — e.g. resolving a task_id for update_task, delete_task, or to re-open a terminal human task. - Use list_tasks (not this tool) when the user explicitly wants to see their tasks ("show me my tasks", "what's on my plate?"). list_tasks renders a rich task-list card; search_tasks does not. Input shape is identical to list_tasks. The same filters apply: - query: free-text search across the task title and planned steps. Whitespace-separated terms are AND-ed together; each term must appear in either the title or the planned steps. Use when the user names a task by content (e.g. "the task about Rosa", "the enrichment task"), and pass only the CONTENT words — never record-type words like "follow-up", "task", "reminder" or "to-do", which exclude every matching task whose title happens not to contain them. Pass null when the user identifies the task by who it involves rather than by content. - status: one of the user-facing labels (Pending, Scheduled, In-progress, Awaiting Trigger, Input Needed, Pending Approval, Completed, Failed, Canceled), or null to search ALL statuses. Pass null whenever the user hasn't named a state. Same for assignee_type. - Date ranges (scheduled_after / scheduled_before, created_after / created_before, completed_after / completed_before), assignee filters (assignee_type, assignee_user_id, created_by_user_id), and association filters (contact_id, contact_company_id, custom_object_id) all behave the same way as in list_tasks. scheduled_after/scheduled_before EXCLUDE undated tasks — omit them unless the user asked about a time window. contact_company_id matches both tasks linked directly to the company and tasks linked to one of its contacts. - query may be combined with metadata filters to narrow results (e.g. query: "Rosa" together with created_after / created_before covering yesterday). Examples: - "Push the prep call task to Friday" → first call search_tasks { query: "prep call" } to resolve the task id, then update_task { task_id, scheduled_for: '...' }. - "Cancel the follow-up I asked you to do for Rosa" → search_tasks { query: "Rosa" } — "follow-up" is a record type, not content, so it does NOT belong in query — then update_task { task_id, status: 'cancelled' }. - "Reassign the Acme outreach task to Bob" → search_tasks { query: "Acme outreach" } (also resolve Bob's user_id via internal_search), then update_task { task_id, assignee_user_id }.
update_object
ChatGPTUpdate an existing object in the system. objectSlug and id are required.
update_task
ChatGPTUpdate an existing Item task. Supports marking a task succeeded or cancelled, adding completion notes, resuming a blocked or errored AI task with new context (resume: true), changing the linked contact, company, or custom object, editing the plan (planned_steps) of a non-terminal AI task, renaming the task, and rescheduling via scheduled_for. Task IDs come from search_tasks.
add_to_list
Claudeask_item_assistant
Claudecreate_list
Claudecreate_note
Claudecreate_object
Claudecreate_task
Claudedelete_object
Claudedelete_task
Claudeedit_note
Claudeexecute_view
Claudeget_list
Claudeget_object
Claudeget_object_schema
Claudelist_lists
Claudelist_object_types
Claudelist_views
Clauderemove_from_list
Claudesearch_notes
Claudesearch_objects
Claudesearch_tasks
Claudeupdate_object
Claudeupdate_task
Claude