Query HubSpot CRM for deals, contacts, and companies, then review deal stages and sales pipeline metrics. Useful for looking up a named account, checking deal status, or examining filtered groups of deals.
Query HubSpot CRM for deals, contacts, companies, and sales metrics. Use this skill when the user asks about sales pipeline, deal status, or customer CRM data.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
https://api.hubapi.comAuthorization: Bearer $HUBSPOT_PRIVATE_APP_TOKEN or legacy
HUBSPOT_ACCESS_TOKENHUBSPOT_PRIVATE_APP_TOKEN preferred,
HUBSPOT_ACCESS_TOKEN legacyserver/lib/hubspot.ts| Function | Description |
|---|---|
getDealPipelines() | All deal pipelines with stages |
getVisiblePipelines(pipelines) | Filter to visible pipelines |
getMetricsPipelines(pipelines) | Filter to metrics-relevant pipelines |
getDealProperties() | HubSpot deal property metadata |
getAllDeals(extraProperties?) | All deals (paginated, up to ~10k) |
getDealOwners() | HubSpot owner id → owner name map |
computeSalesMetrics(deals, pipelines, filter?) | Compute won/lost/pipeline metrics |
# Search deals for a named account/deal
pnpm action hubspot-deals --query="Example Corp" --limit=10 --properties=dealname,amount,dealstage
# Structured cohort: products field = Publish, closed-won New Business deals
pnpm action hubspot-deals --product=Publish --pipeline="New Business" --closedStatus=won --closedDateFrom=2025-06-01 --closedDateTo=2026-06-01
# List deals
pnpm action hubspot-deals --properties=dealname,amount,dealstage
# Find custom fields before requesting them
pnpm action hubspot-deal-properties --search=nbm
getAllDeals paginates using limit=100 and HubSpot after token (up to 100 pages)hubspot-deals --query="Customer" uses HubSpot search and should be the first path for named account/deal deep dives. Avoid pulling every deal first.hubspot-deals filters (product, pipeline, closedStatus, closedDateFrom, closedDateTo) and report the returned filters/count in the methodology.query for property-specific filters. query="Publish" is broad full-text search across deals and can include records where products is not Publish.hubspot-deals cannot express the needed CRM endpoint/filter/body/pagination, use provider-api-catalog --provider=hubspot, optionally provider-api-docs, then provider-api-request --provider=hubspot with the exact HubSpot API request.hubspot-deals returns normalized stage_name, pipeline_name, owner_name, is_closed_won, and is_deal_closed fields under deal.propertiesnbm_meeting_booked_date, nbm_meeting_complete_date, and hs_manual_forecast_category through hubspot-deals; do not use warehouse SQL as the first path unless HubSpot is unavailable and the user approves the fallbackhs_v2_date_entered stage property names with embedded stage IDs when they exist in the connected portalcomputeSalesMetrics infers won/lost stages from probability metadata or label text; identifies POV stages by names containing "proof of value", "pov", "poc"/crm/v3/objects/deals/{id}/associations/companies, then contacts via /crm/v3/objects/companies/{id}/associations/contactsTable: your-project-id.dbt_staging.hubspot_companies
company_name, company_id, company_domain_nameupcoming_renewal_date, customer_stage, hs_csm_sentimentcompany_owner_name, root_org_idcustomer_segmentation, current_enterprise_arr, company_statusdim_hs_contacts.builder_user_id → BigQuery usage dataNo reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Generate, refine, export, and place brand images or videos from an Assets library into another app. The skill covers choosing a library, handling image batches and video runs, and updating selected assets after feedback.
Prepare a customer account health, renewal, or contract usage readout. Verify the account identity, use approved metric definitions, compare contracted capacity with actual usage, and trace findings to sources, time windows, and known gaps.
Create focused app actions that agents can call as tools and frontend code can use through client hooks. Use them to add provider integrations or fetch UI data, with validated inputs and structured results.
Use this checklist when adding a feature or integration to an agent-native app. It covers the user interface, agent-callable actions, instructions, and app-state sync so both the user and agent can work with the capability consistently.
Investigate complex questions by combining data from multiple sources, then summarize patterns, metrics, and evidence in a clear report. Save requested analyses as dashboards with instructions for future refreshes.
Use the Analytics admin surfaces to inspect and change workspace feature flags, review dashboard ownership and usage activity, or browse and edit databases connected from other agent-native apps. The skill guides administrators to the relevant view and actions.