All servers / Finance / HubSpot (Mindstone)
HubSpot (Mindstone)
HubSpot CRM objects, associations and marketing tools.
Tested by ConnectATDScore 85 out of 100. Tested 2026-11-17 on package version 0.5.0. Package: @mindstone/mcp-server-hubspot · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 19 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 8 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (18.0 seconds including download)
- Tools offered: 106
- Last published: 2026-11-16
- Weekly downloads (npm): 307
- License: FSL-1.1-MIT · Direct dependencies: 3
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
list_hubspot_accountsno parametersList all connected HubSpot accounts and their authentication status. ALWAYS call this FIRST before any HubSpot CRM operations to: 1. Check if any HubSpot accounts are connected 2. Verify authentication status (valid, expired, needs re-auth) 3. Get the email address to use for subsequent operations If no accounts are connected, guide the user to connect one using authenticate_hubspot_account. Example workflow: 1. User: "Show me my HubSpot contacts" 2. Agent: Call list_hubspot_accounts first 3. If accounts exist and valid → proceed with search_hubspot_contacts 4. If no accounts → tell user to connect: "You need to connect your HubSpot account first. Would you like me to start the authentication?" 5. If auth expired → call authenticate_hubspot_account to refresh
authenticate_hubspot_account1 of 1 parameter describedConnect a new HubSpot account or re-authenticate an existing one. This tool initiates the OAuth flow to connect a HubSpot account: 1. Returns an authorization URL that the user must click 2. User signs into HubSpot and grants permissions 3. Authentication completes automatically via callback WHEN TO USE: - When list_hubspot_accounts shows no connected accounts - When an account shows status "expired" or "error" - When user explicitly asks to connect/reconnect HubSpot WHEN NOT TO USE: - If list_hubspot_accounts shows a valid, active account - Without checking list_hubspot_accounts first (wastes user time) After calling this tool: 1. Present the auth_url to the user as a clickable link 2. Tell them to click it and authorize in their browser 3. Call complete_hubspot_auth to wait for completion 4. Or if auto_complete is enabled, it will complete automatically
complete_hubspot_auth1 of 1 parameter describedWait for HubSpot OAuth authorization to complete. Call this AFTER authenticate_hubspot_account has returned an auth_url and the user has clicked it. This tool: 1. Waits for the OAuth callback (up to 2 minutes) 2. Exchanges the authorization code for access tokens 3. Saves the account credentials 4. Returns success with the connected email IMPORTANT: Only call this if auto_complete was false in authenticate_hubspot_account response. If auto_complete was true, authentication completes automatically and you don't need this tool.
remove_hubspot_account1 of 1 parameter describedDisconnect a HubSpot account and delete its stored credentials. Use this when: - User wants to disconnect their HubSpot account - User wants to switch to a different HubSpot account - Troubleshooting authentication issues (remove and re-add) This permanently removes the account's access tokens. The user will need to re-authenticate to use HubSpot again.
search_hubspot_contacts5 of 5 parameters describedSearch for contacts in HubSpot CRM. USE THIS WHEN: - User asks "find contact [name/email]" or "look up [person]" - Need to find a contact before updating, associating, or viewing details - Preparing for a meeting and need contact info RETURNS: Array of contacts with id, properties (email, firstname, lastname, etc.) EXAMPLES: 1. Find by email: filters=[{propertyName:"email", operator:"EQ", value:"john@acme.com"}] 2. Find by name: query="John Smith" 3. Find by company: filters=[{propertyName:"company", operator:"CONTAINS_TOKEN", value:"Acme"}] OPERATORS: EQ, NEQ, LT, LTE, GT, GTE, CONTAINS_TOKEN (partial match), IN (list) COMMON PROPERTIES to request: email, firstname, lastname, phone, company, jobtitle, lifecyclestage, hubspot_owner_id
get_hubspot_contact2 of 2 parameters describedGet full details for a single contact by ID. USE THIS WHEN: - You already have a contact ID (from search or association) - Need complete contact information - Preparing a detailed contact profile RETURNS: Single contact object with all requested properties PREREQUISITE: Get contactId from search_hubspot_contacts first
create_hubspot_contact1 of 1 parameter describedCreate a new contact in HubSpot CRM. USE THIS WHEN: - User says "add contact" or "create contact for [person]" - Logging a new lead or prospect - Contact doesn't exist (verify with search first!) REQUIRED: email (strongly recommended - used for deduplication) NOTE: The server automatically sets hs_object_source_detail_2 for source attribution. COMMON PROPERTIES: - email, firstname, lastname - phone, mobilephone - company, jobtitle - address, city, state, zip, country - lifecyclestage: "lead", "marketingqualifiedlead", "salesqualifiedlead", "opportunity", "customer" - hubspot_owner_id: assign to a team member (RECOMMENDED — get IDs from list_hubspot_owners) COMMON MISTAKES: - NOT specifying hubspot_owner_id — if omitted, the contact may be assigned to the HubSpot integration account used by your host, not the intended owner. Use list_hubspot_owners to find the correct owner ID. - If list_hubspot_owners returns empty (e.g., free accounts), you may proceed without hubspot_owner_id. RETURNS: Created contact with id and properties
update_hubspot_contact2 of 2 parameters describedUpdate an existing contact's properties. USE THIS WHEN: - User says "update contact" or "change [field] for [contact]" - Need to correct or add information - Changing lifecycle stage or owner assignment PREREQUISITE: Get contactId from search_hubspot_contacts first RETURNS: Updated contact object
delete_hubspot_contact1 of 1 parameter describedPermanently delete a contact from HubSpot. USE THIS WHEN: - User explicitly asks to delete/remove a contact - Cleaning up duplicate or test records WARNING: This is permanent. Associated engagements may be orphaned. PREREQUISITE: Get contactId from search_hubspot_contacts first
search_hubspot_companies5 of 5 parameters describedSearch for companies/organizations in HubSpot CRM. USE THIS WHEN: - User asks "find company [name]" or "look up [organization]" - Need company info for account research - Finding companies to associate with contacts or deals RETURNS: Array of companies with id, properties (name, domain, industry, etc.) EXAMPLES: 1. Find by name: query="Acme Corp" 2. Find by domain: filters=[{propertyName:"domain", operator:"EQ", value:"acme.com"}] 3. Find by industry: filters=[{propertyName:"industry", operator:"EQ", value:"COMPUTER_SOFTWARE"}] COMMON PROPERTIES to request: name, domain, industry, numberofemployees, annualrevenue, phone, city, country, hubspot_owner_id
get_hubspot_company2 of 2 parameters describedGet full details for a single company by ID. USE THIS WHEN: - You have a company ID (from search or association) - Need complete company profile for account research PREREQUISITE: Get companyId from search_hubspot_companies or get_hubspot_associations
create_hubspot_company1 of 1 parameter describedCreate a new company in HubSpot CRM. USE THIS WHEN: - User says "add company" or "create account for [organization]" - Company doesn't exist (verify with search first!) REQUIRED: name COMMON PROPERTIES: - name (company name) - domain (website domain, used for deduplication) - industry (e.g., "COMPUTER_SOFTWARE", "FINANCIAL_SERVICES") - numberofemployees, annualrevenue - phone, address, city, state, zip, country - hubspot_owner_id: assign to team member (RECOMMENDED — get IDs from list_hubspot_owners) COMMON MISTAKES: - NOT specifying hubspot_owner_id — if omitted, the company may be assigned to the HubSpot integration account used by your host, not the intended owner. Use list_hubspot_owners to find the correct owner ID. - If list_hubspot_owners returns empty (e.g., free accounts), you may proceed without hubspot_owner_id. RETURNS: Created company with id and properties
update_hubspot_company2 of 2 parameters describedUpdate an existing company's properties. USE THIS WHEN: - User says "update company" or "change [field] for [company]" - Need to correct or add company information PREREQUISITE: Get companyId from search_hubspot_companies first
delete_hubspot_company1 of 1 parameter describedPermanently delete a company from HubSpot. WARNING: This is permanent and may affect associated contacts and deals. PREREQUISITE: Get companyId from search_hubspot_companies first
search_hubspot_deals5 of 5 parameters describedSearch for deals/opportunities in HubSpot CRM. USE THIS WHEN: - User asks "find deal [name]" or "show my deals" - Need to check pipeline status - Looking for deals by stage, amount, or owner RETURNS: Array of deals with id, properties (dealname, amount, dealstage, etc.) EXAMPLES: 1. Find by name: query="Acme Enterprise" 2. Find by stage: filters=[{propertyName:"dealstage", operator:"EQ", value:"qualifiedtobuy"}] 3. Find deals > $10k: filters=[{propertyName:"amount", operator:"GT", value:"10000"}] 4. Find by owner: filters=[{propertyName:"hubspot_owner_id", operator:"EQ", value:"12345"}] NOTE: dealstage values are IDs, not names. Use list_hubspot_pipelines to get valid stage IDs. COMMON PROPERTIES: dealname, amount, dealstage, pipeline, closedate, hubspot_owner_id, hs_deal_stage_probability
get_hubspot_deal2 of 2 parameters describedGet full details for a single deal by ID. USE THIS WHEN: - You have a deal ID (from search or association) - Need complete deal information including custom properties PREREQUISITE: Get dealId from search_hubspot_deals or get_hubspot_associations
create_hubspot_deal2 of 2 parameters describedCreate a new deal/opportunity in HubSpot CRM. USE THIS WHEN: - User says "create deal" or "add opportunity" - Logging a new sales opportunity REQUIRED: dealname, hubspot_owner_id IMPORTANT: Use list_hubspot_pipelines first to get valid pipeline and dealstage IDs! FALLBACK FIELDS (set by the server only if not provided): - hubspot_owner_id: FALLBACK ONLY — if not provided via the top-level parameter, falls back to the HubSpot integration account used by your host. This is usually the WRONG person on team accounts. - hs_object_source_detail_2: records that this deal was created via your MCP host COMMON PROPERTIES (inside the properties object): - dealname (deal/opportunity name) - amount (deal value as string, e.g., "10000") - pipeline (pipeline ID from list_hubspot_pipelines, e.g., "default") - dealstage (stage ID from list_hubspot_pipelines, e.g., "qualifiedtobuy") - closedate (expected close date, format: "YYYY-MM-DD") WORKFLOW: 1. list_hubspot_pipelines to get pipeline/stage IDs 2. list_hubspot_owners to find the correct deal owner 3. create_hubspot_deal with valid pipeline/stage IDs AND hubspot_owner_id 4. create_hubspot_association to link to contact/company COMMON MISTAKES: - Using this tool when the user says "lead" or "create a lead" — leads are a separate HubSpot object type. Use create_hubspot_lead instead. - NOT specifying hubspot_owner_id — if omitted, the deal is silently assigned to the HubSpot integration account used by your host, NOT the intended deal owner. This causes incorrect assignment notifications and pipeline confusion. ALWAYS call list_hubspot_owners to find the correct owner ID. - Using display names instead of IDs for pipeline/dealstage — always use list_hubspot_pipelines to get valid IDs first. RETURNS: Created deal with id and properties
update_hubspot_deal2 of 2 parameters describedUpdate an existing deal's properties. USE THIS WHEN: - User says "update deal" or "move deal to [stage]" - Changing deal amount, stage, or close date - Reassigning deal to different owner COMMON UPDATES: - dealstage: move to different pipeline stage (use stage ID from list_hubspot_pipelines) - amount: update deal value - closedate: update expected close date - hubspot_owner_id: reassign to different team member PREREQUISITE: Get dealId from search_hubspot_deals first
delete_hubspot_deal1 of 1 parameter describedPermanently delete a deal from HubSpot. WARNING: This is permanent. Deal history and associations will be lost. PREREQUISITE: Get dealId from search_hubspot_deals first
search_hubspot_tickets5 of 5 parameters describedSearch for tickets in HubSpot with filters
get_hubspot_ticket2 of 2 parameters describedGet a single ticket by ID
create_hubspot_ticket1 of 1 parameter describedCreate a new ticket in HubSpot. Common properties: - subject (required) - content - hs_pipeline - hs_pipeline_stage - hs_ticket_priority
update_hubspot_ticket2 of 2 parameters describedUpdate an existing ticket
delete_hubspot_ticket1 of 1 parameter describedDelete a ticket from HubSpot
search_hubspot_leads5 of 5 parameters describedSearch for leads in HubSpot CRM. NOTE: Requires Sales Hub Professional or Enterprise. USE THIS WHEN: - User asks "find leads" or "show my leads" - Need to find leads by name or filter criteria - Reviewing lead pipeline or status RETURNS: Array of leads with id, properties (hs_lead_name, etc.) EXAMPLES: 1. Find by name: query="John" 2. Find by status: filters=[{propertyName:"hs_lead_status", operator:"EQ", value:"NEW"}] 3. Find by owner: filters=[{propertyName:"hubspot_owner_id", operator:"EQ", value:"12345"}] OPERATORS: EQ, NEQ, LT, LTE, GT, GTE, CONTAINS_TOKEN (partial match), IN (list) COMMON PROPERTIES to request: hs_lead_name, hs_lead_status, hs_pipeline, hs_pipeline_stage, hubspot_owner_id, createdate
get_hubspot_lead2 of 2 parameters describedGet full details for a single lead by ID. NOTE: Requires Sales Hub Professional or Enterprise. USE THIS WHEN: - You already have a lead ID (from search or association) - Need complete lead information - Reviewing a specific lead's properties and status RETURNS: Single lead object with all requested properties PREREQUISITE: Get leadId from search_hubspot_leads first
create_hubspot_lead2 of 2 parameters describedCreate a new lead in HubSpot CRM. NOTE: Requires Sales Hub Professional or Enterprise. IMPORTANT: This tool creates a HubSpot Lead object (pipeline/stage tracking in Sales Hub). DO NOT use create_hubspot_deal when the user says "lead" — deals and leads are separate HubSpot object types. REQUIRED: - properties.hs_lead_name (the lead's display name) - contactId (leads MUST be associated with a contact at creation — HubSpot API requirement) The contactId is used to create a LEAD_TO_PRIMARY_CONTACT association automatically. COMMON PROPERTIES: - hs_lead_name (required — lead display name) - hs_lead_status: "NEW", "OPEN", "IN_PROGRESS", "CONNECTED", "ATTEMPTED_TO_CONTACT" - hubspot_owner_id: assign to a team member (get IDs from list_hubspot_owners) WORKFLOW: 1. search_hubspot_contacts to find/create the contact 2. create_hubspot_lead with contactId and properties 3. Optionally create_hubspot_association to link to a company or deal RETURNS: Created lead with id and properties
update_hubspot_lead2 of 2 parameters describedUpdate an existing lead's properties. NOTE: Requires Sales Hub Professional or Enterprise. USE THIS WHEN: - User says "update lead" or "change lead status" - Changing lead status, owner, or other properties COMMON UPDATES: - hs_lead_status: change lead status - hubspot_owner_id: reassign to different team member PREREQUISITE: Get leadId from search_hubspot_leads first RETURNS: Updated lead object
delete_hubspot_lead1 of 1 parameter describedPermanently delete a lead from HubSpot. NOTE: Requires Sales Hub Professional or Enterprise. WARNING: This is permanent. The lead record will be removed. PREREQUISITE: Get leadId from search_hubspot_leads first
search_hubspot_tasks4 of 4 parameters describedSearch for tasks in HubSpot
get_hubspot_task2 of 2 parameters describedGet a single task by ID
create_hubspot_task1 of 1 parameter describedCreate a new task in HubSpot. Common properties: - hs_task_subject (required) - hs_task_body - hs_timestamp (due date in ms) - hs_task_status (NOT_STARTED, IN_PROGRESS, COMPLETED) - hs_task_priority (LOW, MEDIUM, HIGH) - hubspot_owner_id
update_hubspot_task2 of 2 parameters describedUpdate an existing task
delete_hubspot_task1 of 1 parameter describedDelete a task from HubSpot
search_hubspot_notes5 of 5 parameters describedSearch for notes in HubSpot CRM. USE THIS WHEN: - User asks "find the note about..." or "what notes are on this deal?" - Need to locate a note before reading or updating it RETURNS: Array of notes with id and properties (hs_note_body, hs_timestamp, hubspot_owner_id) Text search (query) matches against hs_note_body. Use filters for precise matching (e.g. filters=[{propertyName:"hs_lastmodifieddate", operator:"GT", value:"2026-01-01"}]).
get_hubspot_note3 of 3 parameters describedGet a single note by ID, including its full body. PREREQUISITE: Get the noteId from search_hubspot_notes first (or from a record's associations via get_hubspot_associations with toObjectType "notes").
update_hubspot_note2 of 2 parameters describedUpdate an existing note's properties (e.g. edit hs_note_body). PREREQUISITE: Get the noteId from search_hubspot_notes or get_hubspot_note first. Only the provided properties are changed; omitted properties are left as-is.
delete_hubspot_note1 of 1 parameter describedPermanently delete (archive) a note by ID. This cannot be undone from the CRM UI recycle bin for engagements — confirm with the user first.
create_hubspot_note2 of 2 parameters describedCreate a note in HubSpot and optionally associate it with records. Properties: - hs_note_body (required) - The note content (supports HTML) - hs_timestamp - When the note was created (ISO8601 or Unix ms) - hs_attachment_ids - Semicolon-separated file IDs to attach (e.g., "123" or "123;456") Get file IDs from upload_hubspot_file or import_hubspot_file_from_url. TO ATTACH FILES TO A RECORD: 1. Upload file with upload_hubspot_file → get file id 2. Create note with hs_attachment_ids: "<file_id>" and associations to the record Or use the convenience tool attach_file_to_record for a one-step workflow.
create_hubspot_association3 of 5 parameters describedCreate an unlabeled association between two HubSpot objects (v3 API). For labeled associations (e.g., "Primary Contact", "Contract Signatory", "Decision Maker"), use create_hubspot_labeled_association instead. Common association types: - contact_to_company - deal_to_contact - deal_to_company - ticket_to_contact - line_item_to_deal
get_hubspot_associations2 of 3 parameters describedGet all associations of a specific type for an object. Useful for pivoting between object types in either direction, e.g.: - deal -> contacts / companies / line_items - line_item -> deals (resolves a line item back to its parent deal) - ticket -> contacts / companies - contact -> deals / companies RETURNS: { results: [{ id, type }] } — array of associated record IDs.
delete_hubspot_association2 of 5 parameters describedRemove an association between two objects
list_hubspot_association_labels2 of 2 parameters describedList available association labels between two object types using the v4 API. Returns all available labels (both HubSpot-defined and custom) with their typeId values. Use the typeId from this response when calling create_hubspot_labeled_association. Object type values: "contacts", "companies", "deals", "tickets", "products", "line_items", or custom object names. RETURNS: Array of labels with { category, typeId, label } - category: "HUBSPOT_DEFINED" (built-in labels like "Primary") or "USER_DEFINED" (custom labels) - typeId: Numeric ID needed for create_hubspot_labeled_association - label: Human-readable name (e.g., "Primary Contact", "Contract Signatory")
create_hubspot_labeled_association6 of 6 parameters describedCreate a labeled association between two records using the v4 API. Unlike create_hubspot_association (v3, unlabeled), this creates associations WITH labels like "Primary Contact", "Contract Signatory", "Decision Maker", etc. WORKFLOW: 1. Call list_hubspot_association_labels to discover available labels and their typeIds 2. Call this tool with the desired associationCategory and associationTypeId associationCategory: - "HUBSPOT_DEFINED": Built-in labels (e.g., Primary Contact, typeId varies by object pair) - "USER_DEFINED": Custom labels created in HubSpot Settings → Objects → Associations
list_hubspot_properties1 of 1 parameter describedList all properties for a HubSpot object type. Supports standard types (contacts, companies, deals, tickets, tasks, leads) and custom objects. Note: For "leads", this listing endpoint works but get_hubspot_property may return SCOPE_MISSING due to a HubSpot API scope limitation.
get_hubspot_property2 of 2 parameters describedGet a single property definition by object type and property name. NOTE: The "leads" object type may return SCOPE_MISSING (403) because HubSpot requires crm.schemas.leads.read scope which is not always granted during OAuth. If this happens, use list_hubspot_properties instead (which works for leads). This is a known HubSpot API limitation, not a bug.
create_hubspot_property8 of 8 parameters describedCreate a new custom property on a HubSpot object. VALID TYPE/FIELDTYPE COMBINATIONS: - string: text, textarea, phonenumber, html - number: number - date: date - datetime: date - enumeration: select, radio, checkbox, booleancheckbox - bool: booleancheckbox
update_hubspot_property5 of 5 parameters describedUpdate an existing property definition. Note: type and fieldType CANNOT be changed after creation.
delete_hubspot_property2 of 2 parameters describedArchive a property from HubSpot. This ARCHIVES the property (not a hard delete).
list_hubspot_property_groups1 of 1 parameter describedList property groups for a HubSpot object type
create_hubspot_property_group4 of 4 parameters describedCreate a new property group for an object type
list_hubspot_owners1 of 1 parameter describedList all HubSpot users who can own CRM records. USE THIS WHEN: - Need to assign a contact, deal, or company to a team member - User asks "who can I assign this to?" or "show me the sales team" - Creating/updating records with hubspot_owner_id property RETURNS: Array of owners with: - id (use this as hubspot_owner_id when creating/updating records) - email, firstName, lastName - teams[] (team memberships) WORKFLOW EXAMPLE: 1. User: "Assign the Acme deal to Sarah" 2. Call list_hubspot_owners to find Sarah's owner ID 3. Call update_hubspot_deal with hubspot_owner_id: "sarah's_id"
get_hubspot_owner1 of 1 parameter describedGet details for a specific HubSpot owner by ID. USE THIS WHEN: - You have an owner ID and need their name/email - Resolving hubspot_owner_id from a record to display owner name PREREQUISITE: Get ownerId from list_hubspot_owners or from a record's hubspot_owner_id property
list_hubspot_pipelines1 of 1 parameter describedList all sales pipelines and their stages. USE THIS WHEN (CRITICAL for deal operations): - BEFORE creating a deal (to get valid pipeline and dealstage IDs) - BEFORE updating deal stage (to get valid stage ID) - User asks "what are the deal stages?" or "show me the pipeline" RETURNS: Array of pipelines, each containing: - pipelineId (use as "pipeline" property) - label (display name) - stages[] with: - stageId (use as "dealstage" property) - label (display name like "Qualified", "Proposal Sent") - displayOrder (stage position) - metadata.probability (win probability %) EXAMPLE RESPONSE: { "pipelineId": "default", "label": "Sales Pipeline", "stages": [ {"stageId": "appointmentscheduled", "label": "Appointment Scheduled"}, {"stageId": "qualifiedtobuy", "label": "Qualified to Buy"}, {"stageId": "closedwon", "label": "Closed Won"} ] } IMPORTANT: Stage IDs are internal identifiers, NOT display names. Always use this tool first!
get_hubspot_pipeline2 of 2 parameters describedGet details for a specific pipeline including all stages. USE THIS WHEN: - You know the pipeline ID and need its stages - Working with a specific pipeline (not the default) PREREQUISITE: Get pipelineId from list_hubspot_pipelines if you don't know it
search_hubspot_calls4 of 4 parameters describedSearch for logged calls in HubSpot CRM. USE THIS WHEN: - User asks "show recent calls" or "find calls with [contact]" - Need call history for meeting prep - Looking for specific call recordings or notes RETURNS: Array of calls with id, properties EXAMPLE FILTERS: 1. Recent calls: filters=[{propertyName:"hs_timestamp", operator:"GT", value:"1704067200000"}] 2. By owner: filters=[{propertyName:"hubspot_owner_id", operator:"EQ", value:"12345"}] 3. Outbound only: filters=[{propertyName:"hs_call_direction", operator:"EQ", value:"OUTBOUND"}] PROPERTIES to request: - hs_call_title, hs_call_body (notes/transcript) - hs_call_direction: "INBOUND" or "OUTBOUND" - hs_call_status: "COMPLETED", "BUSY", "NO_ANSWER", "FAILED", "CONNECTING", "CALLING_CRM_USER" - hs_call_duration (milliseconds) - hs_timestamp (Unix ms when call occurred) - hubspot_owner_id
search_hubspot_meetings4 of 4 parameters describedSearch for logged meetings in HubSpot CRM. USE THIS WHEN: - User asks "show meetings" or "find meetings with [contact]" - Need meeting history for relationship context - Looking for past meeting notes RETURNS: Array of meetings with id, properties EXAMPLE FILTERS: 1. Upcoming: filters=[{propertyName:"hs_meeting_start_time", operator:"GT", value:"1704067200000"}] 2. Completed: filters=[{propertyName:"hs_meeting_outcome", operator:"EQ", value:"COMPLETED"}] PROPERTIES to request: - hs_meeting_title, hs_meeting_body (notes/agenda) - hs_meeting_start_time, hs_meeting_end_time (Unix ms) - hs_meeting_outcome: "SCHEDULED", "COMPLETED", "RESCHEDULED", "NO_SHOW", "CANCELLED" - hs_meeting_location - hubspot_owner_id
get_hubspot_call2 of 2 parameters describedGet full details for a single call by ID. USE THIS WHEN: - You have a call ID and need complete details - Retrieving call notes or recording info PREREQUISITE: Get callId from search_hubspot_calls or get_contact_engagements
get_hubspot_meeting2 of 2 parameters describedGet full details for a single meeting by ID. USE THIS WHEN: - You have a meeting ID and need complete details - Retrieving meeting notes or attendee info PREREQUISITE: Get meetingId from search_hubspot_meetings or get_contact_engagements
search_hubspot_emails4 of 4 parameters describedSearch logged 1:1 sales email engagements in HubSpot CRM. USE THIS WHEN: - User asks "show the last email thread with this account" or "find emails about [topic]" - Meeting prep: recent email activity with a contact or company RETURNS: Array of email engagements with id, properties PROPERTIES to request: - hs_email_subject, hs_email_direction ("INCOMING_EMAIL"/"OUTGOING_EMAIL"), hs_email_status - hs_email_from_email, hs_email_to_email - hs_timestamp (Unix ms) - hs_email_text / hs_email_html (body — see SCOPE NOTE) SCOPE NOTE: HubSpot silently redacts email BODIES unless the connected app holds the sales-email-read scope. Without it you still get subjects, senders, and timestamps, and the response carries a notes field warning that bodies are redacted. To unlock bodies, enable sales-email-read on the HubSpot app and reconnect the account. EXAMPLE FILTERS: 1. Recent: filters=[{propertyName:"hs_timestamp", operator:"GT", value:"1704067200000"}] 2. By subject: filters=[{propertyName:"hs_email_subject", operator:"CONTAINS_TOKEN", value:"contract"}]
get_hubspot_email2 of 2 parameters describedGet full details for a single logged email engagement by ID. PREREQUISITE: Get emailId from search_hubspot_emails or get_contact_engagements. SCOPE NOTE: the email body (hs_email_text / hs_email_html) is redacted by HubSpot unless the connected app holds the sales-email-read scope; the response carries a notes field warning when redaction applies. Subject, sender, recipients, and timestamps are always returned.
create_hubspot_call2 of 2 parameters describedLog a call in HubSpot CRM. USE THIS WHEN: - User says "log a call" or "record that I called [contact]" - Documenting a phone conversation - Adding call notes after a conversation REQUIRED: hs_timestamp (Unix timestamp in milliseconds) COMMON PROPERTIES: - hs_timestamp: when call occurred (REQUIRED, Unix ms, e.g., Date.now()) - hs_call_title: brief description - hs_call_body: notes, transcript, or summary - hs_call_direction: "INBOUND" or "OUTBOUND" - hs_call_status: "COMPLETED", "BUSY", "NO_ANSWER", "FAILED" - hs_call_duration: call length in milliseconds - hubspot_owner_id: who made the call ASSOCIATIONS (link call to records): - contactIds: ["contact_id_1", "contact_id_2"] - companyIds: ["company_id"] - dealIds: ["deal_id"] WORKFLOW: 1. search_hubspot_contacts to get contact ID 2. create_hubspot_call with associations.contactIds RETURNS: Created call with id
create_hubspot_meeting2 of 2 parameters describedLog a meeting in HubSpot CRM. USE THIS WHEN: - User says "log a meeting" or "record meeting with [contact]" - Documenting a completed meeting - Scheduling a future meeting in CRM REQUIRED: - hs_timestamp (Unix ms) - hs_meeting_start_time (Unix ms) - hs_meeting_end_time (Unix ms) COMMON PROPERTIES: - hs_timestamp: when meeting was logged (Unix ms) - hs_meeting_start_time: meeting start (Unix ms) - hs_meeting_end_time: meeting end (Unix ms) - hs_meeting_title: meeting subject - hs_meeting_body: notes, agenda, or action items - hs_meeting_outcome: "SCHEDULED", "COMPLETED", "RESCHEDULED", "NO_SHOW", "CANCELLED" - hs_meeting_location: location or video link - hubspot_owner_id: meeting organizer ASSOCIATIONS (link meeting to records): - contactIds: attendee contact IDs - companyIds: company IDs - dealIds: related deal IDs WORKFLOW: 1. search_hubspot_contacts to get attendee contact IDs 2. create_hubspot_meeting with associations RETURNS: Created meeting with id
get_contact_engagements2 of 2 parameters describedGet all recent activity (calls, meetings) for a contact. USE THIS WHEN: - User asks "what's the history with [contact]?" or "show activity for [person]" - Preparing for a meeting and need relationship context - Need a quick activity summary RETURNS: Object with arrays for each engagement type: { calls: [{id, properties}], meetings: [{id, properties}] } This is a convenience tool that fetches multiple engagement types in one call. For more control, use search_hubspot_calls or search_hubspot_meetings directly. PREREQUISITE: Get contactId from search_hubspot_contacts first
search_hubspot_products5 of 5 parameters describedSearch for products in your HubSpot product catalog. USE THIS WHEN: - User asks about products, SKUs, or pricing - Looking up specific products by name or SKU - Finding products to add to a deal as line items COMMON PROPERTIES: - name: Product name - hs_sku: Stock keeping unit - price: Unit price - description: Product description - hs_cost_of_goods_sold: Cost/COGS - hs_recurring_billing_period: P1M (monthly), P1Y (yearly) SEARCH BY TEXT: Use "query" for free-text search (name, SKU) SEARCH BY FILTER: Use "filters" for exact matches RETURNS: Array of products with id and properties
get_hubspot_product2 of 2 parameters describedGet a specific product by ID. USE THIS WHEN: - You have a product ID and need full details - Looking up product pricing or SKU details RETURNS: Product object with all requested properties
create_hubspot_product1 of 1 parameter describedCreate a new product in the product catalog. USE THIS WHEN: - Adding new products to sell - Setting up product catalog REQUIRED: name RECOMMENDED: price, hs_sku, description EXAMPLE: { "properties": { "name": "Enterprise License", "price": "10000", "hs_sku": "ENT-001", "description": "Annual enterprise license" } } RETURNS: Created product with id
update_hubspot_product2 of 2 parameters describedUpdate an existing product's properties. USE THIS WHEN: - Changing product price - Updating SKU or description - Modifying any product attribute RETURNS: Updated product
search_hubspot_line_items4 of 4 parameters describedSearch for line items in HubSpot. Line items connect products to deals for revenue tracking. Each line item represents a product/service with quantity and price on a deal. COMMON PROPERTIES: - name: Line item name (often matches product) - quantity: Number of units - price: Unit price - amount: Total (quantity × price) - hs_discount_percentage: Applied discount - hs_product_id: Source product ID RETURNS: Array of line items
get_hubspot_line_item3 of 3 parameters describedGet a specific line item by ID. To resolve a line item back to its parent deal in the same call, pass `associations: ['deals']`. The response then includes an `associations` object with `{ deals: { results: [{ id, type }] } }`. RETURNS: Line item object. Includes `associations` only when the `associations` parameter is provided.
create_hubspot_line_item2 of 2 parameters describedCreate a line item and optionally associate with a deal. Line items link products to deals for revenue tracking. This is the KEY tool for adding products to a deal. WORKFLOW: 1. search_hubspot_products to find product ID 2. search_hubspot_deals to find deal ID 3. create_hubspot_line_item with dealId association REQUIRED PROPERTIES: - name: Line item name - quantity: Number of units (string, e.g. "1") - price: Unit price (string, e.g. "1000.00") OPTIONAL: - hs_product_id: Link to product catalog - hs_discount_percentage: Discount to apply - dealId: Associate immediately with deal EXAMPLE: { "properties": { "name": "Enterprise License - Annual", "quantity": "2", "price": "10000", "hs_product_id": "123456" }, "dealId": "789" } RETURNS: Created line item with id
search_hubspot_object6 of 6 parameters describedSearch records of ANY HubSpot object type, including custom objects. USE THIS WHEN: - The object type isn't covered by a dedicated tool (contacts/companies/deals/tickets/leads/tasks/notes/products/line_items) — e.g. a tenant-defined custom object like "p_widgets" or "2-1234567" - Prefer the dedicated search_hubspot_<object> tools for standard objects objectType: the CRM object type name — standard plural names ("contacts") or custom object names/IDs ("p_widgets", "2-1234567"). Custom object names are visible in HubSpot under Settings → Data Management → Custom Objects, or via list_hubspot_properties on a known type. The query parameter uses HubSpot's native full-text search across the object's default searchable properties. Use filters for precise property matching. REQUIRES the crm.objects.custom.read OAuth scope for custom object types. On a 403 the account's plan or the connected app's scopes are the likely cause — reconnecting alone won't help unless the scope is enabled on the app.
get_hubspot_object4 of 4 parameters describedGet a single record of ANY HubSpot object type by ID, including custom objects. PREREQUISITE: Get the record ID from search_hubspot_object first. REQUIRES the crm.objects.custom.read OAuth scope for custom object types.
create_hubspot_object2 of 2 parameters describedCreate a record of ANY HubSpot object type, including custom objects. Use list_hubspot_properties with the same objectType first to discover the object's properties and their expected values. To link the new record to other records, follow up with create_hubspot_association (or create_hubspot_labeled_association). REQUIRES the crm.objects.custom.write OAuth scope for custom object types.
list_hubspot_forms3 of 3 parameters describedList all forms in HubSpot. Forms collect leads through your website, landing pages, or embedded forms. FORM TYPES: - hubspot: Standard HubSpot forms - captured: Non-HubSpot forms (collected via tracking) - flow: Pop-up forms - blog_comment: Blog comment forms RETURNS: Array of forms with id, name, formType, createdAt
get_hubspot_form1 of 1 parameter describedGet detailed information about a specific form. RETURNS: Form with id, name, configuration, fieldGroups (form fields)
get_hubspot_form_submissions3 of 3 parameters describedGet submissions for a specific form. USE THIS WHEN: - Reviewing lead capture performance - Checking recent form submissions - Analyzing lead sources RETURNS: Array of submissions with: - submittedAt: Submission timestamp - values: Field name/value pairs - pageUrl: Where form was submitted NOTE: Uses formGuid (same as formId for most forms)
get_hubspot_analytics_report5 of 5 parameters describedGet website traffic analytics report. This is the ONLY reporting API available from HubSpot. HubSpot does not have a public API for creating, listing, or managing custom reports or dashboards. For custom report needs, users must use the HubSpot UI directly. ⚠️ REQUIRES Marketing Hub Professional or Enterprise. Will return 403 error on free accounts. BREAKDOWN OPTIONS: - totals: Overall traffic metrics - sessions: Session-based metrics - sources: Traffic by source (organic, direct, etc.) - geolocation: Traffic by country/region - utm-campaigns: By UTM campaign - utm-sources: By UTM source - utm-mediums: By UTM medium - pages: By page URL TIME PERIODS: - totals: Aggregate for date range - daily: Day-by-day breakdown - weekly: Week-by-week - monthly: Month-by-month DATE FORMAT: YYYYMMDD (e.g., "20260101") RETURNS: { totals: {views, visits, leads, ...}, breakdowns: [{breakdown: "...", metrics: {...}}, ...] }
list_hubspot_marketing_emails2 of 2 parameters describedList marketing emails in HubSpot. RETURNS: Array of emails with: - id, name, subject - state: DRAFT, SCHEDULED, PUBLISHED, etc. - type: REGULAR, AB_EMAIL, BLOG_EMAIL, etc. - createdAt, stats (if available)
get_hubspot_marketing_email1 of 1 parameter describedGet details of a specific marketing email by ID. USE THIS WHEN: - User asks "show me the follow-up email" or "what's in email X" - Need email content, subject, template path, or configuration RETURNS: Full email object including: - id, name, subject, previewText - state, type, templatePath - content/body (if available) - stats summary
get_hubspot_email_statistics3 of 3 parameters describedGet aggregated email performance statistics. RETURNS: { aggregations: {sent, delivered, opened, clicked, bounced, unsubscribed}, emails: [{emailId, counters: {...}}] } Use this to analyze email campaign performance across multiple emails.
list_hubspot_lists2 of 2 parameters describedList all contact lists (segments) in HubSpot. RETURNS: Array of lists with {listId, name, processingType, size, createdAt} processingType values: - MANUAL: Static list, manually managed - DYNAMIC: Auto-updates based on filter criteria - SNAPSHOT: Point-in-time capture, does not update Use get_hubspot_list to see a dynamic list's filter criteria.
get_hubspot_list1 of 1 parameter describedGet details of a specific list/segment by ID. RETURNS: {listId, name, processingType, objectTypeId, filterBranch, size, createdAt, updatedAt} For DYNAMIC lists, filterBranch contains the criteria that determine membership. For MANUAL/SNAPSHOT lists, filterBranch is usually empty. To get the contacts IN this list, use list_hubspot_list_members.
list_hubspot_list_members3 of 3 parameters describedGet contact IDs that are members of a list/segment. IMPORTANT: Returns contact IDs only, NOT full contact records. To get contact details (email, name, etc.), use batch_read_hubspot_contacts. WORKFLOW for exporting a segment: 1. Call list_hubspot_list_members(listId) to get contact IDs 2. Call batch_read_hubspot_contacts(ids, properties) to get details 3. Repeat with pagination cursor if needed RETURNS: {results: [{recordId, membershipTimestamp}], paging: {next: {after}}}
batch_read_hubspot_contacts2 of 2 parameters describedFetch multiple contacts by ID in a single request (up to 100). USE THIS TO: Hydrate contact IDs from list_hubspot_list_members into full records. WORKFLOW: 1. list_hubspot_list_members(listId) → get recordIds 2. batch_read_hubspot_contacts(ids, ['email', 'firstname', 'lastname']) → get details RETURNS: {results: [{id, properties: {email, firstname, ...}, createdAt, updatedAt}]} Common properties: email, firstname, lastname, phone, company, jobtitle, lifecyclestage
add_hubspot_list_members2 of 2 parameters describedAdd records to a HubSpot list/segment. USE THIS WHEN: - User asks "add these contacts to the Q3 webinar list" or "put this deal on the nurture list" WORKFLOW: 1. list_hubspot_lists → find the listId 2. search_hubspot_contacts (or another search tool) → find the record IDs 3. add_hubspot_list_members with both IMPORTANT: only MANUAL and SNAPSHOT lists accept membership changes. DYNAMIC lists compute membership from their filter criteria — HubSpot rejects the write; edit the list's filters (in the HubSpot UI) instead. REQUIRES the crm.lists.write OAuth scope. On a 403 the account's plan, the signed-in user's permissions, or the connected app's scopes are the likely cause.
remove_hubspot_list_members2 of 2 parameters describedRemove records from a HubSpot list/segment. USE THIS WHEN: - User asks "take these contacts off the webinar list" or "clean up this segment" IMPORTANT: only MANUAL and SNAPSHOT lists accept membership changes. DYNAMIC lists compute membership from their filter criteria — HubSpot rejects the write; edit the list's filters (in the HubSpot UI) instead. REQUIRES the crm.lists.write OAuth scope. On a 403 the account's plan, the signed-in user's permissions, or the connected app's scopes are the likely cause.
list_hubspot_kb_articles2 of 2 parameters describedList Knowledge Base articles in HubSpot via the GraphQL API (read-only). USE THIS WHEN: - User asks "show me KB articles" or "what's in the knowledge base?" - Need to browse all KB articles with pagination - Looking for a specific article to retrieve with get_hubspot_kb_article RETURNS: - KB articles with id, title, body, slug, URL, language, and metadata - Total count and pagination support via limit/offset SCOPES REQUIRED: cms.knowledge_base.articles.read and collector.graphql_query.execute (a 403 usually means the account's plan or the signed-in user's permissions don't include the knowledge base — reconnecting alone won't add it) COMMON MISTAKES: - Expecting write operations — KB tools are read-only (no create/update/delete API exists) Requires Service Hub Professional or Enterprise.
get_hubspot_kb_article1 of 1 parameter describedGet full details for a single HubSpot Knowledge Base article by ID via the GraphQL API (read-only). USE THIS WHEN: - You already have an articleId and need full content/details - Need the complete article body, metadata, or URL RETURNS: - Full KB article object with id, title, body, slug, URL, language, and metadata WORKFLOW: 1. Get articleId from list_hubspot_kb_articles or search_hubspot_kb_articles 2. Call get_hubspot_kb_article for complete details SCOPES REQUIRED: cms.knowledge_base.articles.read and collector.graphql_query.execute (a 403 usually means the account's plan or the signed-in user's permissions don't include the knowledge base — reconnecting alone won't add it) COMMON MISTAKES: - Using a knowledgeBaseId/contentGroupId instead of an articleId - Assuming search result snippets are full article content — use this tool for the full body Requires Service Hub Professional or Enterprise.
search_hubspot_kb_articles2 of 2 parameters describedSearch published HubSpot Knowledge Base content by query text via the Site Search API (read-only). USE THIS WHEN: - User asks to find KB content by keyword or phrase - Looking up published help articles or troubleshooting docs RETURNS: - Search matches with title, URL, and snippet metadata from HubSpot site search WORKFLOW: 1. Call search_hubspot_kb_articles with a clear query 2. Use get_hubspot_kb_article for full article details when needed IMPORTANT: Only finds PUBLISHED articles. This tool searches the public site index and does not include draft or scheduled content. Use list_hubspot_kb_articles to browse all articles. COMMON MISTAKES: - Expecting drafts in results — site search only indexes published content - Using this as the only retrieval path when you need all articles Requires Service Hub Professional or Enterprise.
upload_hubspot_file3 of 3 parameters describedUpload a file to HubSpot's file manager from a local file path. USE THIS WHEN: - User wants to upload a document, image, or attachment to HubSpot - Preparing a file to attach to a CRM record (contact, deal, company, ticket) - Storing branding assets, proposals, contracts, etc. RETURNS: { id, name, path, url, size, access } - The "id" is the file ID used to attach files to records via notes WORKFLOW to attach a file to a record: 1. upload_hubspot_file → get file "id" 2. create_hubspot_note with hs_attachment_ids set to the file id, and associations to link to the record ACCESS LEVELS: - PRIVATE (default): Only accessible via signed URL, not publicly visible - PUBLIC_NOT_INDEXABLE: Publicly accessible but search engines won't index - PUBLIC_INDEXABLE: Fully public and indexable by search engines
import_hubspot_file_from_url4 of 4 parameters describedImport a file into HubSpot's file manager from a URL. USE THIS WHEN: - User wants to import a file from the web into HubSpot - Adding a file from a public URL to attach to a record - Importing images, documents, or media from external sources This tool handles the async import process automatically (polls until complete, up to 30s). Returns the final file object with its ID once ready. WORKFLOW to attach an imported file to a record: 1. import_hubspot_file_from_url → get file { id, name, path, url, size } 2. create_hubspot_note with hs_attachment_ids set to the file id, and associations to link to the record ACCESS LEVELS: - PRIVATE (default): Only accessible via signed URL - PUBLIC_NOT_INDEXABLE: Publicly accessible, not indexed - PUBLIC_INDEXABLE: Fully public and indexable
get_hubspot_file2 of 2 parameters describedGet details of a file in HubSpot's file manager by ID. USE THIS WHEN: - Need to check file details (name, size, URL, access level) - Verifying a file exists before attaching to a record - Getting a viewable URL for a private file (use getSignedUrl: true) RETURNS: { id, name, path, url, size, type, access, createdAt, updatedAt } For private files, the url will 404. Set getSignedUrl to true to get a temporary viewable URL.
delete_hubspot_file1 of 1 parameter describedDelete a file from HubSpot's file manager. WARNING: This marks the file as deleted and makes its content inaccessible. Notes that reference this file will no longer display the attachment.
attach_file_to_record4 of 4 parameters describedUpload a file and attach it to a CRM record in one step. This is a convenience tool that combines: 1. Uploading a file to HubSpot's file manager 2. Creating a note with the file attached 3. Associating the note with the specified record(s) USE THIS WHEN: - User says "attach this file to [contact/deal/company]" - Adding a document, proposal, or contract to a record - Uploading meeting notes or attachments to a contact ACCEPTS EITHER: - filePath: Local file path to upload - fileUrl: Public URL to import RETURNS: { fileId, noteId, fileName, associations }
list_hubspot_workflows1 of 1 parameter describedList all automation workflows in HubSpot (v4 BETA API). Returns workflow metadata: id, name, type, isEnabled, timestamps. Use get_hubspot_workflow with the flow id for full structure (actions, triggers, branches). RELATED TOOLS: - get_hubspot_workflow (inspect one workflow) - create_hubspot_workflow (create a workflow) - update_hubspot_workflow (replace workflow configuration) - activate_hubspot_workflow / deactivate_hubspot_workflow (toggle state) - delete_hubspot_workflow (permanently delete) - enrol_in_hubspot_workflow (enrol specific records) REQUIRES: automation scope, plus a plan that includes workflows (Operations Hub, or Marketing/Sales Hub Professional or Enterprise). A 403 means the connection can't access workflows — most often the account's plan or the signed-in user's permissions, less commonly the scope isn't authorised for the app. Reconnecting alone won't add it; resolve the underlying cause first, then reconnect HubSpot to pick up the change. NOTE: This uses the v4 Automation API which is in BETA — response shape may change.
get_hubspot_workflow1 of 1 parameter describedGet full workflow structure including actions, triggers, and branches (v4 BETA API). Returns the complete workflow graph with: - Enrollment criteria (triggers and conditions) - Actions (each with actionTypeId, fields, and connection to next action) - Branch logic Useful for analyzing workflow structure and identifying potential issues. Call list_hubspot_workflows first to discover available flow IDs. RELATED TOOLS: - create_hubspot_workflow (create new workflows) - update_hubspot_workflow (replace workflow configuration) - activate_hubspot_workflow / deactivate_hubspot_workflow (toggle workflow status) - enrol_in_hubspot_workflow (manually enrol records) - delete_hubspot_workflow (permanently delete workflow) REQUIRES: automation scope and a plan that includes workflows (see list_hubspot_workflows for what a 403 means). NOTE: This is a BETA API — treat unknown fields cautiously as the response shape may change.
create_hubspot_workflow4 of 4 parameters describedCreate a new HubSpot workflow. ⚠️ BETA API — this uses the v4 Automation API. Endpoint behavior may change. WORKFLOW TYPES: - CONTACT_FLOW: Triggered by contact enrollment - COMPANY_FLOW: Triggered by company enrollment - DEAL_FLOW: Triggered by deal enrollment - TICKET_FLOW: Triggered by ticket enrollment EXAMPLE minimal workflow: { "name": "New Lead Notification", "type": "CONTACT_FLOW" } To add actions and enrollment criteria, use the fields from get_hubspot_workflow as a reference for the expected structure.
update_hubspot_workflow4 of 4 parameters describedUpdate a workflow via PUT (full replace semantics). IMPORTANT: This endpoint behaves like a replacement update. Include all fields you want to preserve (name/actions/enrollmentCriteria), not just changed fields. Use get_hubspot_workflow first, then submit the updated full structure.
delete_hubspot_workflow2 of 2 parameters describedPermanently delete a workflow. WARNING: This is irreversible. The workflow and its history are removed. Set confirm=true to acknowledge permanent deletion.
activate_hubspot_workflow1 of 1 parameter describedActivate a workflow (sets isEnabled to true).
deactivate_hubspot_workflow1 of 1 parameter describedDeactivate a workflow (sets isEnabled to false).
enrol_in_hubspot_workflow3 of 3 parameters describedEnrol specific records into a workflow. Uses the v4 BETA enrollment endpoint. A 403 means the connection can't access workflows (most often plan or user permissions, less commonly app authorisation) — reconnecting alone won't fix it; resolve the cause, then reconnect. A 404 may mean your portal requires the v3 enrollment endpoint.
list_hubspot_ticket_threads5 of 5 parameters describedList conversation threads associated with a HubSpot support ticket. Use this when you need to read the actual customer messages on a ticket — for example, to draft a reply for an unassigned ticket. Tickets in HubSpot only expose the initial `subject` and `content` fields; the full back-and-forth lives on Conversations threads. Typical workflow: 1. search_hubspot_tickets to find candidate tickets 2. list_hubspot_ticket_threads(ticketId) to find the thread(s) attached to a ticket 3. list_hubspot_thread_messages(threadId) to read the message history 4. (optional) get_hubspot_thread_message_original_content if a message is truncated REQUIRES: `conversations.read` OAuth scope (added May 2026). On a 403: accounts connected before then must reconnect to grant it; otherwise reconnecting won't help — the account's plan or the signed-in user's permissions are the likely cause. RETURNS: { results: [{ id, status, latestMessageTimestamp, ... }], paging? }
list_hubspot_thread_messages3 of 3 parameters describedList messages on a conversation thread, in chronological order. Each message includes `text` and/or `richText` body, `sender`, `recipients`, `createdAt`, `type` (MESSAGE | COMMENT | WELCOME_MESSAGE), and `truncationStatus`. If `truncationStatus` indicates the body was truncated, call get_hubspot_thread_message_original_content with the same threadId/messageId to fetch the full body. REQUIRES: `conversations.read` OAuth scope (added May 2026). On a 403: accounts connected before then must reconnect to grant it; otherwise reconnecting won't help — the account's plan or the signed-in user's permissions are the likely cause. RETURNS: { results: [...messages], paging? }
get_hubspot_thread_message_original_content2 of 2 parameters describedFetch the full, untruncated original content of a single conversation message. Use this only when the message returned from list_hubspot_thread_messages has a `truncationStatus` indicating its body was truncated. For untruncated messages, the body is already present in list_hubspot_thread_messages and this call is unnecessary. REQUIRES: `conversations.read` OAuth scope (added May 2026). On a 403: accounts connected before then must reconnect to grant it; otherwise reconnecting won't help — the account's plan or the signed-in user's permissions are the likely cause.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.