How do I install the Hubspot Deals skill?

Run npx skillmds@latest add dipankar/hubspot-deals in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Hubspot Deals safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Hubspot Deals?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Hubspot Deals free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Hubspot Deals?

dipankar (@dipankar) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Hubspot Deals by dipankar — Agent Skill

Name: Hubspot Deals
Author: dipankar

File contents

HubSpot Deals (via `hubspot` CLI)

Deals track revenue opportunities through a sales pipeline. Each deal lives in a pipeline and a stage.

Auth

Set HUBSPOT_ACCESS_TOKEN. Optional --profile <name>.

Canonical commands

Intent	Command
List	`hubspot crm deals list --limit 20 --properties dealname,amount,dealstage,closedate`
Get by ID	`hubspot crm deals get 12345`
Create	`hubspot crm deals create --dealname "Q2 Expansion" --amount 50000 --stageid appointmentscheduled`
Create from JSON	`hubspot crm deals create --properties '{"dealname":"Q2","amount":"50000","pipeline":"default","dealstage":"appointmentscheduled"}'`
Update stage	`hubspot crm deals update 12345 --properties '{"dealstage":"contractsent"}'`
Close-won	`hubspot crm deals update 12345 --properties '{"dealstage":"closedwon","closedate":"2025-06-01T00:00:00Z"}'`
Delete	`hubspot crm deals delete 12345 --yes`
Search by stage	`hubspot crm deals search --filter-groups '[{"filters":[{"propertyName":"dealstage","operator":"EQ","value":"closedwon"}]}]'`
Open deals	`hubspot crm deals search --filter-groups '[{"filters":[{"propertyName":"dealstage","operator":"NOT_IN","values":["closedwon","closedlost"]}]}]'`
Batch create	`hubspot crm deals batch-create --inputs '[...]'`

Pipelines and stages

Deal stages are pipeline-specific. Always list them before creating or moving deals:

hubspot crm pipelines list deals
hubspot crm pipelines stages deals <pipeline_id>

Use the internal dealstage id (e.g. appointmentscheduled, qualifiedtobuy, contractsent, closedwon, closedlost), not the display label.

Common properties

dealname, amount, dealstage, pipeline, closedate, hubspot_owner_id, dealtype, description, hs_priority.

Associating deals

# Associate deal 12345 with contact 67890
hubspot crm associations create deals 12345 contacts 67890

# And with company 54321
hubspot crm associations create deals 12345 companies 54321

Output / errors

Standard {success, data, paging}. Error codes: AUTH_ERROR (3), VALIDATION_ERROR (5), NOT_FOUND (6), RATE_LIMIT (7).

Scopes

Read: crm.objects.deals.read
Write: crm.objects.deals.write

Tips

amount is a string (HubSpot returns all numeric properties as strings). Quote it in JSON.
closedate must be ISO-8601 UTC.
Use --output json-pretty only when the user explicitly wants to read the JSON.

---name: hubspot-dealsdescription: Use when the user wants to search, read, create, update, or manage HubSpot CRM deals (opportunities, pipeline revenue, deal stages) via the `hubspot` command-line tool.---# HubSpot Deals (via `hubspot` CLI)Deals track revenue opportunities through a sales pipeline. Each deal lives in a pipeline and a stage.## AuthSet `HUBSPOT_ACCESS_TOKEN`. Optional `--profile <name>`.## Canonical commands| Intent | Command || --- | --- || List | `hubspot crm deals list --limit 20 --properties dealname,amount,dealstage,closedate` || Get by ID | `hubspot crm deals get 12345` || Create | `hubspot crm deals create --dealname "Q2 Expansion" --amount 50000 --stageid appointmentscheduled` || Create from JSON | `hubspot crm deals create --properties '{"dealname":"Q2","amount":"50000","pipeline":"default","dealstage":"appointmentscheduled"}'` || Update stage | `hubspot crm deals update 12345 --properties '{"dealstage":"contractsent"}'` || Close-won | `hubspot crm deals update 12345 --properties '{"dealstage":"closedwon","closedate":"2025-06-01T00:00:00Z"}'` || Delete | `hubspot crm deals delete 12345 --yes` || Search by stage | `hubspot crm deals search --filter-groups '[{"filters":[{"propertyName":"dealstage","operator":"EQ","value":"closedwon"}]}]'` || Open deals | `hubspot crm deals search --filter-groups '[{"filters":[{"propertyName":"dealstage","operator":"NOT_IN","values":["closedwon","closedlost"]}]}]'` || Batch create | `hubspot crm deals batch-create --inputs '[...]'` |## Pipelines and stagesDeal stages are pipeline-specific. Always list them before creating or moving deals:```bashhubspot crm pipelines list dealshubspot crm pipelines stages deals <pipeline_id>```Use the internal `dealstage` id (e.g. `appointmentscheduled`, `qualifiedtobuy`, `contractsent`, `closedwon`, `closedlost`), not the display label.## Common properties`dealname`, `amount`, `dealstage`, `pipeline`, `closedate`, `hubspot_owner_id`, `dealtype`, `description`, `hs_priority`.## Associating deals```bash# Associate deal 12345 with contact 67890hubspot crm associations create deals 12345 contacts 67890# And with company 54321hubspot crm associations create deals 12345 companies 54321```## Output / errorsStandard `{success, data, paging}`. Error codes: `AUTH_ERROR (3)`, `VALIDATION_ERROR (5)`, `NOT_FOUND (6)`, `RATE_LIMIT (7)`.## Scopes- Read: `crm.objects.deals.read`- Write: `crm.objects.deals.write`## Tips- `amount` is a string (HubSpot returns all numeric properties as strings). Quote it in JSON.- `closedate` must be ISO-8601 UTC.- Use `--output json-pretty` only when the user explicitly wants to read the JSON.

Frequently asked questions

Hubspot Deals