account_answer_question
ChatGPTAnswers questions about an account by searching and analyzing account record, meeting transcription, and other related data in the time range if specified. Example questions include: - What specific challenges or pain points is the account experiencing? - What are the desired outcomes or business goals the account aims to achieve?
account_create
ChatGPTCreates a new account in Outreach. The current user is automatically assigned as one of the account's assigned users. The current user is set as the owner if no owner is specified in the input. Returns the created account record including its id only. IMPORTANT: Every field value used to create the account MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field. ALWAYS call input_fields_fetch with resource="Account" and action="Create" before calling this tool. input_fields_fetch returns the full list of available standard fields, their types, and any required custom fields with validation rules. This ensures you know exactly which fields are available and which are required before creating the account. Example: input: name: "Acme Corp" additional_fields: - field_name: "domain" value: "acme.com" - field_name: "companyType" value: "Enterprise" - field_name: "industry" value: "Technology" - field_name: "custom1" value: "NA"
account_get_by_id
ChatGPTRetrieve an account using its unique identifier and return the corresponding Account object which includes default fields: id, name, company_type, owner, touched_at, industry, default_connection Use the additional_fields param to include additional account fields in the response. For custom fields (e.g. "Current CRM") which are not already included in the additional_fields parameter description or default fields, first call the filter_fields_fetch tool with entity_type="account" to discover relevant custom fields, then pass that ID (ex. "custom8") in additional_fields. Never guess custom field IDs. Only use when you know the corresponding label. Note: This tool returns only summary information (id, name) for the owner. To get full details about the owner, use the user_get_by_id tool with the owner's id.
account_search
ChatGPTSearch for accounts. Default fields returned: id, name, company_type, owner, touched_at, industry, default_connection. Filters (all optional): name (partial or full), owner_ids, team_id, ids, created date, account plan updated date, last contacted date. - Use last_contacted_before/last_contacted_after to find accounts with or without recent sales activity (sales rep engagement over emails, calls, meetings). - Use additional_field_filters to filter by field values with AND logic. Additional output fields: - Use additional_fields to include extra fields in results. For both additional_fields and additional_field_filters, call filter_fields_fetch tool with entity_type="account" first to discover valid field IDs and labels. Never guess field IDs.
account_search_by_external_id
ChatGPTSearch for accounts using id of the associated object in external systems, such as Saleforce or Dynamics. The search will return a list of Accounts. The Account contains the same information returned by account_get_by_id tool.
calendar_events_fetch
ChatGPTRetrieve a list of calendar events (meetings) based on optional filter criteria. A calendar event represents a scheduled meeting or appointment on a user's calendar. Use this tool to fetch scheduled meetings which have not yet occurred or to review past meetings regardless of whether they had transcripts or were processed by Kaia's meeting intelligence features. Use the kaia_meeting_fetch tool to retrieve contents about meetings which have already occurred (transcripts, etc). Use this tool to explore meetings from calendar metadata (e.g. scheduled date, source, cancellation status, etc). Notes: - Multiple filters are combined with AND logic. - Use limit to control how many results are returned. Response: - Each event includes the title, time range, associated prospect/account/opportunity, and attendees. - The 'count' field indicates the total number of matching events, which may exceed the limit. When count > limit, state both the total and the number shown, e.g., "Showing 10 of 247 total events." When count <= limit, state only the count, e.g., "Found 3 calendar events."
current_user
ChatGPTReturns the user id and email of the caller
emails_search
ChatGPTFetches outbound emails for a specific account or opportunity. IMPORTANT: This tool ONLY returns emails sent BY reps, not emails received from prospects. If the user asks about received/inbound emails, use state='replied' to find emails that got replies, then use email_fetch_thread to retrieve the reply content. If a user query does not reference an account or opportunity: 1. DO NOT call this tool with null values for account_id or opportunity_id 2. Ask the user: "Which account or opportunity would you like to search for emails in?" 3. Wait for the user to provide the information before proceeding 4. A tool call will likely be made to map the account or opportunity name from a user to account_id or opportunity_id Only call this tool after the user has provided one of these identifiers. Additionally, use user_id to filter emails sent or received by a specific user. If a user asks about "my emails" or "emails I've sent/received", use the current user id as user_id.
filter_fields_fetch
ChatGPTFetch fields for a specific entity type (ex. account) which can be used as: - filter attributes on that entity's search tool (ex. account_search, opportunity_search, prospect_search) through the additional_field_filters parameter. - additional output fields on that entity's search or get tools through the additional_fields parameter. Use this tool to retrieve up to 250 additional fields which can be used to retrieve the necessary data to answer user queries that can't be answered with built-in filters and args on existing entity search or get tools. ONLY Supported entity types: - prospect - account - opportunity Response format: - 'id' is the internal id used only for API calls. - 'label' is the human friendly name displayed in the UI that users will be familiar with. - 'validation_type' describes the data type (ex. numerical, inclusion, string, date). - 'validation_definition' describes accepted values for 'inclusion' and 'currency' validation_types. For 'inclusion' and 'currency' fields, the filter value must exactly match one of the entries in validation_definition. Example Response: { "entity_type": "account", "count": 2, "custom_fields": [ { "id": "amount", "label": "amount", "description": "The $ value of the opportunity in annual revenue.", "validation_type": "numerical", "validation_definition": null }, { "id": "custom3", "label": "Account Priority", "validation_type": "inclusion", "validation_definition": [ "Low", "Medium", "High" ] } ] }
input_fields_fetch
ChatGPTFetch the available input fields for a resource create/update action. Returns a ResourceInputSchema with three sections: - standard_fields: typed optional fields (e.g. companyType, industry, assignedTeams). - ref_types: definitions of non-scalar types referenced by standard_fields (e.g. TeamRelationship, UserRelationship — each with its 'id' field). - custom_fields: organization-specific custom fields with validation metadata. Supported resources: Account Supported actions: Create Response structure: resource (str): The resource type (e.g. 'Account'). action (str): The action type (e.g. 'Create'). standard_fields (list): Standard optional fields, each containing: - name: camelCase GQL field name (e.g. 'companyType', 'assignedTeams') - type: concise type string (e.g. 'string', 'int', 'float', 'TeamRelationship', 'list[UserRelationship]', 'list[string]') - required: whether the field is required for the action - description: description of the field ref_types (list): Non-scalar type definitions referenced by standard_fields. Each contains: - name: type name (e.g. 'TeamRelationship', 'UserRelationship') - description: description of the type - fields: list of fields in this type, each with name, type, required custom_fields (list): Custom fields with validation rules, each containing: - name: internal field identifier (e.g. 'custom1') - label: human-readable label (e.g. 'Region') - required: whether the field is required - description: description of the custom field - validation_type: validation kind ('numerical', 'inclusion', 'string', 'currency', 'date') - validation_definition: accepted values for 'inclusion' type, currency code for 'currency' type, etc. Example response: { "resource": "Account", "action": "Create", "standard_fields": [ {"name": "companyType", "type": "string", "required": false, "description": "Company type of the account"}, {"name": "assignedTeams", "type": "list[TeamRelationship]", "required": false, "description": "Teams assigned to the account"} ], "ref_types": [ {"name": "TeamRelationship", "description": "A relationship reference to a Team entity.", "fields": [{"name": "id", "type": "int", "required": true, "description": "ID of the related entity"}]}, {"name": "UserRelationship", "description": "A relationship reference to a User entity.", "fields": [{"name": "id", "type": "int", "required": true, "description": "ID of the related entity"}]} ], "custom_fields": [ {"name": "custom1", "label": "Region", "required": true, "description": "Region", "validation_type": "inclusion", "validation_definition": ["NA", "EMEA", "APAC"]} ] }
kaia_meeting_search
ChatGPTSearch across recorded calls and meetings captured by Kaia. Returns matching recordings with transcripts, topics, summaries, and associated account/opportunity info. Use this tool to find recordings by keyword, topic, account, opportunity, participant, host, date range, or title. Kaia captures two kinds of recordings: - Voice calls (phone calls): sourceType = "voice" - Meetings (video/screen-share conferences, e.g. Zoom, Teams): sourceType ≠ "voice" When the user says "calls", filter to voice calls. When they say "meetings", filter to non-voice. When the intent covers both (e.g. "conversations", "recordings"), do not filter by sourceType. FILTER FORMAT: Pass a JSON list of filter objects. Each filter has the shape: {attribute, value, operator}. - attribute: the field to filter on (see supported attributes below) - value: list of string values to match - operator: (optional) defaults to "is". Supported: "is", "isNot" (plus date-specific operators for 'meeting.startTime', see below) All filters are combined with AND logic. SUPPORTED FILTER ATTRIBUTES: - 'search' — full-text keyword search across transcripts, notes, action items, meeting title, participant/account/opportunity names. Syntax: Single word: value: ["budget"] Implicit AND: value: ["budget planning"] Explicit OR: value: ["\"budget\" OR \"planning\""] Exact phrase: value: ["\"budget planning\""] - 'transcript.text' — search only within transcript text (more precise than 'search'). Example: [{attribute: "transcript.text", value: ["budget"], operator: "is"}] - 'topic.type' — detected topic name. General topics: 'budgetpricing', 'competitor', 'demotrial', 'discovery', 'eventmarketing', 'legal', 'logistics', 'nextstep', 'organization', 'product', 'purchase', 'salespitch', 'stakeholder', 'support'. MEDDPICC topics (prefix 'salesMethodology:'): 'salesMethodology:champion', 'salesMethodology:competitor', 'salesMethodology:metrics', 'salesMethodology:economicbuyer', 'salesMethodology:decisionprocess', 'salesMethodology:decisioncriteria', 'salesMethodology:paperprocess', 'salesMethodology:implicatepain'. Auto-enrichment: non-built-in names (e.g. "Salesforce") are automatically mapped to custom topic IDs if a match is found. Built-in types 'competitor' and 'product' automatically include all active custom topics of that type. Example: value: ["competitor", "Salesforce"] finds meetings tagged with any built-in competitor topic, all custom competitor topics, and the custom topic named 'Salesforce'. IMPORTANT: always pair a topic.type filter with include: [{attribute: "topic", includeType: "matching"}] to receive the matching topic segments in the results. Do NOT include transcript. - 'meeting.accountid' — account id - 'meeting.opportunityid' — opportunity id - 'meeting.participant.userid' — participant user id (not just host) - 'meeting.host.userid' — host user id - 'meeting.sourcetype' — value: ["voice"], operator: "is" for calls; value: ["voice"], operator: "isNot" for meetings. - 'meeting.startTime' — date/range filter. Use ONLY these operators (no others are valid): "is" — exact date match: value: ["2026-03-10"], operator: "is" "between" — date range: value: ["2026-03-01", "2026-03-05"], operator: "between" Relative operators (value must be ["0"], operator is one of the following exact strings): "last7Days" — past 7 days (use for "this week" or "last 7 days") "last30Days" — past 30 days "last90Days" — past 90 days "lastMonth" — the previous calendar month "thisMonth" — the current calendar month "today" — today only "untilToday" — from the beginning of time until today "ytd" — year to date - 'meeting.title' — filter by keyword in meeting title - 'meeting.duration' - filter by meeting duration in minutes. Supported operators include: "gte" - greater than or equal to "lte" - less than or equal to "between" - duration between value[0] and value[1] All attributes accept multiple comma-separated values. FILTER EXAMPLES: filter: [{attribute: "search", value: ["Amplify OR budget"]}] filter: [{attribute: "topic.type", value: ["competitor", "Salesforce"], operator: "is"}, {attribute: "meeting.accountid", value: ["123"]}] filter: [{attribute: "topic.type", value: ["salespitch"], operator: "isNot"}] filter: [{attribute: "meeting.sourcetype", value: ["voice"], operator: "is"}] filter: [{attribute: "meeting.sourcetype", value: ["voice"], operator: "isNot"}] INCLUDE FORMAT: Controls which artifact types are returned alongside each matching meeting. Only include artifact types relevant to the query to avoid unnecessary data. attribute values: - 'transcript' — transcript segments - 'topic' — detected topics includeType values: - 'matching' — return only artifacts that match the current filter/search INCLUDE EXAMPLES: Required for keyword search only: [{attribute: "transcript", includeType: "matching"}] Required for topic search only: [{attribute: "topic", includeType: "matching"}] Only when searching both simultaneously: [{attribute: "transcript", includeType: "matching"}, {attribute: "topic", includeType: "matching"}] Do NOT include transcript when topic.type is used as a filter — it returns unrelated segments and inflates the response. PAGINATION: Use 'first' (default 10, max 30) to control page size. Use 'after' with the end_cursor from a previous response to fetch the next page.
opportunity_answer_question
ChatGPTAnswers questions about an opportunity by searching and analyzing opportunity record, meeting transcription, and other related data in the time range if specified. Example questions include: - What business goals is the buyer aiming to achieve? - What specific challenges is the buyer trying to solve?
opportunity_create
ChatGPTCreates a new opportunity record in Outreach. The current user is automatically assigned as the owner if no owner is specified in the input. Returns an opportunity record with only the id field populated; all other fields are not set. IMPORTANT: Every field value used to create the opportunity MUST be explicitly provided by the user. Never infer, guess, or fabricate field values. If the user has not supplied a value for a field, do not include that field. ALWAYS call input_fields_fetch with resource="Opportunity" and action="Create" before calling this tool. input_fields_fetch returns the full list of available standard fields, their types, and any required custom fields with validation rules. This ensures you know exactly which fields are available and which are required before creating the opportunity. Example: input: name: "Q1 Enterprise Deal" closeDate: "2026-05-17T16:48:12.000Z" additional_fields: - field_name: "amount" value: 50000 - field_name: "opportunityStage" value: {"id": 3} - field_name: "custom1" value: "Inbound"
opportunity_get_by_id
ChatGPTRetrieve a opportunity and associated sales methodology using its unique identifier and return the corresponding Opportunity object including: id: int name: str | None account: Account | None (only id and name are returned) amount: int | None close_date: str | None created_at: str | None health_score: float | None next_step: str | None last_contacted_at: str | None updated_at: str | None assigned_users: list[User] (only id and name are returned for each user) opportunity_stage: OpportunityStage | None owner: User | None (only id and name are returned) primary_prospect: Prospect | None (only id and name are returned) default_connection: DataConnection | None sales_methodology: SalesMethodology | None (only present when include_sales_methodology=True) fields: list[SalesMethodologyField] SalesMethodologyField contains the definition of a sales methodology field and the opportunity's value for that field, and includes: order: int | None label: str | None name: str | None label_short: str | None type: str | None definition: str | None value: str | None (the opportunity's value for this field) use type and definition if set to determine how to interpret the value field. For example, when type is "RELATIONSHIP", definition is "PROSPECT", and value is "1280273", it means the value is id of the prospect resource. To get more details about the resource, use the corresponding get_by_id tool with the id, or other appropriate tools. In this example, use prospect_get_by_id with id 1280273 to get more details about the prospect. Note: sales_methodology is only available from this tool, not from opportunity_search or other opportunity tools. This tool returns only summary information (id, name) for nested objects such as owner, assigned_users, and primary_prospect. The account field contains the parent account's id and name — use account.id (not the opportunity id) for account-scoped lookups. To get full details about the owner or an assigned user, use the user_get_by_id tool with the user's id. To get full details about the primary prospect, use the prospect_get_by_id tool with the prospect's id.
opportunity_search
ChatGPTSearch for opportunities. Default fields returned: id, account, amount, close_date, created_at, health_score, name, next_step, last_contacted_at, updated_at, assigned_users, opportunity_stage, owner, primary_prospect, default_connection. Filters (all optional): ids, name, account_id, owner_ids, is_open, created date range, close date range, health score range. - Use additional_field_filters to filter by field values with AND logic. Additional output fields: - Use additional_fields to include extra fields in results. For both additional_fields and additional_field_filters, call filter_fields_fetch tool with entity_type="opportunity" first to discover valid field IDs and labels. Never guess field IDs. The Opportunity contains the same information returned by opportunity_get_by_id tool, except sales_methodology which is only available via opportunity_get_by_id. Each opportunity result includes the parent account (account.id, account.name). The response includes: - count: the TOTAL number of matching opportunities (server-side, not limited by the limit parameter). - opportunities: the list of opportunity records (up to limit items). When the user asks about health score without specifying exact numbers, use health_score_low and health_score_high to filter: - any mention of health score without a specific range → health_score_low=0, health_score_high=100 to only return opportunities that have a valid health score When filtering by health score range, sort by health_score ascending to show the most critical opportunities first (sort=["health_score"]). A null/missing health_score means the score is unknown/unavailable — NOT that the score is 0 or low. When presenting results filtered by health score, note any records with missing health score values.
opportunity_search_by_external_id
ChatGPTSearch for opportunities using id of the associated object in external systems, such as Saleforce or Dynamics. The search will return a list of Opportunities. The Opportunity contains the same information returned by opportunity_get_by_id tool, except sales_methodology which is only available via opportunity_get_by_id.
opportunity_stage_fetch
ChatGPTReturns a list of opportunity stages with optional filtering. Opportunity stages represent the different phases in a sales process (e.g., 'Discovery', 'Negotiation', 'Closed Won'). Supported filter attributes: - id - name - isClosed Examples: - filter:[] → returns all opportunity stages - filter:[{"attribute": "isClosed", "operator": "is", "value": "true"}] → only stages that are subtypes of 'closed' - filter:[{"attribute": "id", "operator": "is", "value": ["1", "2"]}] → only stages with id 1 or 2 - filter:[{"attribute": "name", "operator": "is", "value": ["Discovery"]}] → only stages with name that exactly matches 'Discovery' Notes: - Partial string matching is not supported for 'name'. - Multiple filters are combined with AND logic (all must match). Response: - Each stage includes id, name, isActive, isWon, and isClosed fields. - The response 'count' field indicates the total number of matching stages, which may exceed the number of records returned when a limit is applied.
prospect_create
ChatGPTCreates a new prospect in Outreach. The current user is automatically assigned as one of the prospect's assigned users. The current user is set as the owner if no owner is specified in the input. Returns the created prospect record including its id only. IMPORTANT: Every field value used to create the prospect MUST be explicitly provided by the user. NEVER infer, guess, or fabricate field values. Do NOT make up field names. If the user has not supplied a value for a field, do not include that field. At least one of first_name or last_name must be provided. ALWAYS call input_fields_fetch with resource="Prospect" and action="Create" before calling this tool. input_fields_fetch returns the full list of custom fields with validation rules. This ensures you know exactly which fields are available and which are required before creating the prospect. HOW TO BUILD THE INPUT — follow these steps in order: Step 1: Set first_name and/or last_name from the user's request. Step 2: Set owner and assigned_users if specified by the user. Step 3: Collect ALL remaining data the user provided (standard fields like title, company, emails, AND custom fields like custom1, custom2) and place them into additional_fields. Custom fields (custom1 through custom150) are always strings. Step 4: Check input_fields_fetch results for any field with required: true. If ANY required field is missing from custom_fields, STOP and ask the user for the value. Step 5: Verify additional_fields is NOT null and NOT empty [] if you collected any values in Steps 3-4. custom_fields handling: Any field whose name starts with "custom" (e.g. custom1, custom2, …, custom150) MUST be placed inside additional_fields — they are NOT top-level parameters. Each entry has a field_name (e.g. "custom1") and a value (always a string for custom fields). Example — user says "Create prospect Jane Smith, VP of Sales at Acme Corp, set custom1 to NA": input: first_name: "Jane" last_name: "Smith" additional_fields: - field_name: "title" value: "VP of Sales" - field_name: "company" value: "Acme Corp" - field_name: "custom1" value: "NA"
prospect_get_by_id
ChatGPTRetrieve a prospect using its unique identifier and return the corresponding Prospect object including: id: int name: str | None owner: User | None (only id and name are returned) account: Account | None (only id, name, company_type, touched_at, and industry are returned) assigned_users: list[User] (only id and name are returned for each user) campaign_name: str | None engaged_score: float | None engaged_at: str | None touched_at: str | None stage: Stage | None default_connection: DataConnection | None Note: This tool returns only summary information for nested objects. To get full details about the owner or an assigned user, use the user_get_by_id tool with the user's id. To get full details about the account, use the account_get_by_id tool with the account's id. To get multiple prospects by their IDs, use the prospect_search tool with the ids parameter.
prospect_search
ChatGPTSearch for prospects using: - the supported filters: name (partial or full name), ids (list of prospect IDs), account_ids, opportunity_ids, and owner_ids. - additional_field_filters to filter by field values with AND logic. At least one filter (name, ids, account_ids, opportunity_ids, owner_ids, additional_field_filters) SHOULD be provided; calling with no filters returns all prospects in the system. Returns a list of Prospects. Each prospect contains the same information returned by prospect_get_by_id tool. Default fields returned: id, name, owner, account, assigned_users, campaign_name, engaged_score, engaged_at, stage, default_connection. Additional output fields: - Use additional_fields to include extra fields in results. For both additional_fields and additional_field_filters, call filter_fields_fetch tool with entity_type="prospect" first to discover valid field IDs and labels. Never guess field IDs. Both custom_fields and standard_fields can be used for filtering and additional output. The response includes: - count: the TOTAL number of matching prospects (server-side, not limited by the limit parameter). - prospects: the list of prospect records (up to limit items). When count > limit, state both the total and the number shown, e.g., "Showing 10 of 50 total prospects." When count <= limit, state only the count, e.g., "Found 3 prospects."
prospect_search_by_external_id
ChatGPTSearch for prospects using id of the associated object in external systems, such as Saleforce or Dynamics. The search will return a list of Prospects. The Prospect contains the same information returned by prospect_get_by_id tool.
sequence_add_prospects
ChatGPTAdds prospects to a sequence in Outreach by creating a batch operation. Returns a BatchRecord containing the batch ID and status. After receiving the batch response, use the batch_get_by_id tool with the returned batch ID to check its progress and report the final state (total, failures, pending) to the user. Required inputs: - prospect_ids: list of prospect IDs to add to the sequence. - sequence_id: ID of the target sequence. Optional inputs allow controlling mailbox, starting template, opportunity association, batch confirmation, and scheduling. IMPORTANT: Prospect IDs and sequence ID must be explicitly provided by the user. NEVER guess or fabricate IDs.
sequence_search
ChatGPTSearch for sequences using additional_filters for field-level filtering with AND logic. Returns a list of Sequences. Each sequence contains: - id, name, owner, engagement_score, sequence_steps The response includes: - count: the TOTAL number of matching sequences (server-side, not limited by the limit parameter). - sequences: the list of sequence records (up to limit items). - page_info: cursor pagination info (end_cursor, has_next_page, etc.) When count > limit, state both the total and the number shown, e.g., "Showing 10 of 50 total sequences." When count <= limit, state only the count, e.g., "Found 3 sequences."
sequence_state_search
ChatGPTSearch for sequence states — records that track an individual prospect's involvement and progress through the steps of a specific outreach sequence. Each sequence state ties one prospect to one sequence and captures their current execution state within that sequence (e.g., 'active', 'bounced', 'paused', 'finished'). A sequence state is NOT the same as a prospect stage. Prospect stages (e.g., 'Attempting to Contact', 'Closed - Unresponsive') describe the prospect's overall disposition in the pipeline. Sequence states describe whether a prospect is currently progressing through a specific sequence's steps. Use this tool when: - The user asks about prospects involved in a specific sequence - The user asks who has been contacted, bounced, replied, or is active in a sequence - The user wants to check a prospect's progress through sequence steps - The user asks about outreach activity tied to a sequence Do NOT use this tool to list the org-level prospect disposition stages — use stage_fetch for that. Supports filtering by account, opportunity, or state. Returns matching sequence states and total count. Each SequenceState includes: id: int prospect: Prospect | None sequence: Sequence | None sequence_step: SequenceStep | None state: str | None user: User | None updated_at: str | None Supports pagination via limit and offset parameters.
stage_fetch
ChatGPTReturns the list of prospect lifecycle stages configured for the organization. Stages are org-level configuration labels that classify where a prospect sits in the outreach pipeline. They describe the prospect's overall disposition, NOT their enrollment in a specific sequence. Example stage names: - 'Not Started' - 'Not Started - Added to Sequence' - 'Attempting to Contact' - 'In Progress with Rep' - 'Closed - Unresponsive' - 'Closed - Not Interested - Unsubscribe' - 'Closed - Using Competitive Product' - 'Closed - Left Company' - 'Closed - Bad Timing' Use this tool when: - The user asks "what stages do we have?" or "list all prospect stages" - You need to resolve a stage name to its ID for filtering prospects by stage - The user wants to know the available disposition categories for prospects Do NOT use this tool to find which prospects are enrolled in a sequence or to check a prospect's progress through sequence steps — use sequence_state_search for that. Response: - Each stage includes id and name fields. - The response 'count' field indicates the total number of stages, which may exceed the number of records returned when a limit is applied.
user_get_by_id
ChatGPTRetrieve an user using its unique identifier and return the corresponding User object including: id: int name: str | None first_name: str | None last_name: str | None email: str | None teams: list[Team] (only id and name are returned for each team) Note: This tool returns only summary information (id, name) for teams. To get full details about a team, use the team_get_by_id tool with the team's id. To get multiple users by their IDs, use the user_search tool with the ids parameter.
user_search
ChatGPTSearch for users using: - the supported filters: name (partial or full name) and ids (list of user IDs). - additional_filters to filter by field values with AND logic. By default, locked and guest users are excluded (locked=false, guest=false). To include locked or guest users, pass the corresponding filter with value ["true"] in additional_filters. PREFERRED over calling team_get_by_id repeatedly: when you need users from multiple teams, use a single user_search call with a team filter (e.g. {"attribute": "team", "operator": "is", "value": ["1", "2", "3"]}) instead of calling team_get_by_id for each team. Returns a list of Users. Each user contains the same information returned by user_get_by_id tool. The response includes: - count: the TOTAL number of matching users (server-side, not limited by the limit parameter). - users: the list of user records (up to limit items). When count > limit, state both the total and the number shown, e.g., "Showing 10 of 50 total users." When count <= limit, state only the count, e.g., "Found 3 users."
account_get_by_id
Claudeaccount_search_by_ext_id
Claudeaccount_search_by_name
Claudeemails_search
Claudefetch_kaia_meetings
Claudeopportunity_get_by_id
Claudeopportunity_search_by_ext_id
Claudeopportunity_search_by_name
Claudeprospect_get_by_id
Claudeprospect_search_by_ext_id
Claudeprospect_search_by_name
Claudesequence_search_by_name
Claudeuser_get_by_id
Claudeuser_search_by_ext_id
Claudeuser_search_by_nam
Claude
