
About
Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration.
name: hubspot-automation description: "Automate HubSpot CRM operations (contacts, companies, deals, tickets, properties) via Rube MCP using Composio integration." risk: critical source: community date_added: "2026-02-27"
HubSpot CRM Automation via Rube MCP
Automate HubSpot CRM workflows including contact/company management, deal pipeline tracking, ticket search, and custom property creation through Composio's HubSpot toolkit.
Prerequisites
- Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
- Active HubSpot connection via
RUBE_MANAGE_CONNECTIONSwith toolkithubspot - Always call
RUBE_SEARCH_TOOLSfirst to get current tool schemas
Setup
Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.
- Verify Rube MCP is available by confirming
RUBE_SEARCH_TOOLSresponds - Call
RUBE_MANAGE_CONNECTIONSwith toolkithubspot - If connection is not ACTIVE, follow the returned auth link to complete HubSpot OAuth
- Confirm connection status shows ACTIVE before running any workflows
Core Workflows
1. Create and Manage Contacts
When to use: User wants to create new contacts or update existing ones in HubSpot CRM
Tool sequence:
HUBSPOT_GET_ACCOUNT_INFO- Verify connection and permissions (Prerequisite)HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA- Search for existing contacts to avoid duplicates (Prerequisite)HUBSPOT_READ_A_CRM_PROPERTY_BY_NAME- Check property metadata for constrained values (Optional)HUBSPOT_CREATE_CONTACT- Create a single contact (Required)HUBSPOT_CREATE_CONTACTS- Batch create contacts up to 100 (Alternative)
Key parameters:
HUBSPOT_CREATE_CONTACT:propertiesobject withemail,firstname,lastname,phone,companyHUBSPOT_CREATE_CONTACTS:inputsarray of{properties}objects, max 100 per batchHUBSPOT_SEARCH_CONTACTS_BY_CRITERIA:filterGroupsarray with{filters: [{propertyName, operator, value}]},propertiesarray of fields to return
Pitfalls:
- Max 100 records per batch; chunk larger imports
- 400 'Property values were not valid' if using incorrect property names or enum values
- Always search before creating to avoid duplicates
- Auth errors from GET_ACCOUNT_INFO mean all subsequent calls will fail
2. Manage Companies
When to use: User wants to create, search, or update company records
Tool sequence:
HUBSPOT_SEARCH_COMPANIES- Search existing companies (Prerequisite)HUBSPOT_CREATE_COMPANIES- Batch create companies, max 100 (Required)HUBSPOT_UPDATE_COMPANIES- Batch update existing companies (Alternative)HUBSPOT_GET_COMPANY- Get single company details (Optional)HUBSPOT_BATCH_READ_COMPANIES_BY_PROPERTIES- Bulk read companies by property values (Optional)
Key parameters:
HUBSPOT_CREATE_COMPANIES:inputsarray of{properties}objects, max 100HUBSPOT_SEARCH_COMPANIES:filterGroups,properties,sorts,limit,after(pagination cursor)
Pitfalls:
- Max 100 per batch; chunk larger sets
- Store returned IDs immediately for downstream operations
- Property values must match exact internal names, not display labels
3. Manage Deals and Pipeline
When to use: User wants to search deals, view pipeline stages, or track deal progress
Tool sequence:
HUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE- Map pipeline and stage IDs/names (Prerequisite)HUBSPOT_SEARCH_DEALS- Search deals with filters (Required)HUBSPOT_RETRIEVE_PIPELINE_STAGES- Get stage details for one pipeline (Optional)HUBSPOT_RETRIEVE_OWNERS- Get owner/rep details (Optional)HUBSPOT_GET_DEAL- Get single deal details (Optional)HUBSPOT_LIST_DEALS- List all deals without filters (Fallback)
Key parameters:
HUBSPOT_SEARCH_DEALS:filterGroupswith filters onpipeline,dealstage,createdate,closedate,hubspot_owner_id;properties,sorts,limit,afterHUBSPOT_RETRIEVE_ALL_PIPELINES_FOR_SPECIFIED_OBJECT_TYPE:objectTypeset to'deals'
Pitfalls:
- Results nested under
response.data.results; properties are often strings (amounts, dates) - Stage IDs may be readable strings or opaque numeric IDs; use
labelfield for display - Filters must use internal property names (
pipeline,dealstage,createdate), not display names - Paginate via
paging.next.afteruntil absent
4. Search and Filter Tickets
When to use: User wants to find support tickets by status, date, or criteria
Tool sequence:
HUBSPOT_SEARCH_TICKETS- Search with filterGroups (Required)HUBSPOT_READ_ALL_PROPERTIES_FOR_OBJECT_TYPE- Discover available property names (Fallback)HUBSPOT_GET_TICKET- Get single ticket details (Optional)HUBSPOT_GET_TICKETS- Bulk fetch tickets by IDs (Optional)
Key parameters:
HUBSPOT_SEARCH_TICKETS:filterGroups,properties(onl
