​
What can you do with it?

The HubSpot integration enables comprehensive CRM management including contacts, deals, and support tickets. You can search for existing records, create new entries, update information, and manage associations between different objects. This integration supports full lifecycle management from initial contact through deal closure and ongoing support, making it ideal for sales teams and customer service operations.

​
How to use it?

​
Basic Command Structure

/your-hubspot-connection [action] [required-parameters] [optional-parameters]

​
Parameters

Required:

  • action - The operation you want to perform (search, create, update, fetch)

Optional:

  • object_type - The HubSpot object type (contact, deal, ticket)

  • properties - Specific properties to retrieve or update

​
Tools

​
Search Contacts

Search for contacts using various filters and properties

Parameters:

  • email (optional) - Email address to search for
  • firstname (optional) - First name to search for
  • lastname (optional) - Last name to search for
  • query (optional) - General search query
  • properties (optional) - Properties to return in results
  • limit (optional) - Maximum number of results (default: 10)

Example:

/your-hubspot-connection
action: search_contact
email: john.doe@example.com
properties: firstname, lastname, email, phone

Response:

{
  "total": "[Number of matching contacts]",
  "results": "[Array of contact objects with requested properties]"
}

​
Create Contact

Create a new contact record

Parameters:

  • email (required) - Contact email address
  • firstname (optional) - Contact first name
  • lastname (optional) - Contact last name
  • phone (optional) - Contact phone number

Example:

/your-hubspot-connection
action: create_contact
email: newcontact@example.com
firstname: Jane
lastname: Smith
phone: 1234567890

Response:

{
  "id": "[Created contact ID]",
  "properties": "[Contact properties object]"
}

​
Update Contact

Update existing contact properties

Parameters:

  • contact_id (required) - The ID of the contact to update
  • properties (required) - Object containing properties to update

Example:

/your-hubspot-connection
action: update_contact
contact_id: 123
firstname: Updated First Name
phone: 9876543210

Response:

{
  "id": "[Contact ID]",
  "properties": "[Updated contact properties]"
}

​
Create Deal

Create a new deal and optionally associate it with a contact

Parameters:

  • dealname (required) - Name of the deal
  • dealstage (required) - Current stage of the deal
  • amount (optional) - Deal amount
  • closedate (optional) - Expected close date
  • contact_id (optional) - ID of contact to associate with

Example:

/your-hubspot-connection
action: create_deal
dealname: New Business Deal
dealstage: appointmentscheduled
amount: 5000
closedate: 2025-03-01T12:00:00Z
contact_id: 123

Response:

{
  "id": "[Created deal ID]",
  "properties": "[Deal properties object]"
}

​
Update Deal

Update deal properties including stage and amount

Parameters:

  • deal_id (required) - The ID of the deal to update
  • dealstage (optional) - New deal stage
  • amount (optional) - Updated deal amount
  • dealname (optional) - Updated deal name
  • closedate (optional) - Updated close date

Example:

/your-hubspot-connection
action: update_deal
deal_id: 789
dealstage: presentationscheduled
amount: 7500
dealname: Updated Deal Name

Response:

{
  "id": "[Deal ID]",
  "properties": "[Updated deal properties]"
}

​
Create Ticket

Create a support ticket and optionally associate it with a contact

Parameters:

  • subject (required) - Ticket subject
  • content (required) - Ticket description
  • priority (optional) - Ticket priority (HIGH, MEDIUM, LOW)
  • pipeline (optional) - Pipeline ID (default: 0)
  • pipeline_stage (optional) - Pipeline stage ID (default: 1)
  • contact_id (optional) - ID of contact to associate with

Example:

/your-hubspot-connection
action: create_ticket
subject: Technical Support Required
content: Customer is experiencing login issues
priority: HIGH
contact_id: 123

Response:

{
  "id": "[Created ticket ID]",
  "properties": "[Ticket properties object]"
}

​
Update Ticket

Update ticket properties including status and priority

Parameters:

  • ticket_id (required) - The ID of the ticket to update
  • pipeline_stage (optional) - New pipeline stage
  • priority (optional) - Updated priority
  • content (optional) - Updated description

Example:

/your-hubspot-connection
action: update_ticket
ticket_id: 321
pipeline_stage: 2
priority: MEDIUM
content: Updated ticket description with customer feedback

Response:

{
  "id": "[Ticket ID]",
  "properties": "[Updated ticket properties]"
}

​
Fetch Deals

Retrieve a list of deals with pagination and filtering

Parameters:

  • limit (required) - Maximum number of results per page
  • after (optional) - Pagination cursor from previous response
  • properties (optional) - Properties to return
  • associations (optional) - Associated objects to retrieve
  • archived (optional) - Whether to return archived results

Example:

/your-hubspot-connection
action: fetch_deals
limit: 10
properties: dealname, amount, dealstage, closedate
associations: contact, company

Response:

{
  "results": "[Array of deal objects]",
  "paging": "[Pagination information including next cursor]"
}

​
Fetch Tickets

Retrieve support tickets with filtering and sorting

Parameters:

  • limit (optional) - Maximum number of results (default: 50)
  • properties (optional) - Properties to return
  • priority_filter (optional) - Filter by priority (HIGH, MEDIUM, LOW)
  • sort (optional) - Sort order (default: -createdate)

Example:

/your-hubspot-connection
action: fetch_tickets
limit: 50
properties: subject, content, hs_pipeline_stage, hs_ticket_priority
priority_filter: HIGH

Response:

{
  "total": "[Total number of tickets]",
  "results": "[Array of ticket objects]"
}

​
Notes

When searching for contacts, you can use multiple filter groups with OR logic between groups and AND logic within groups. Deal stages and ticket priorities use specific HubSpot values that should match your portal configuration. Association type IDs are predefined: use typeId 3 for contact-to-deal associations and typeId 16 for contact-to-ticket associations. Properties can be specified multiple times in fetch operations for granular control over returned data.