hubspot-update-deal_skill

This skill updates HubSpot deals by ID, allowing stage, amount, name, or close date changes to keep records accurate.
  • Python

2

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill abdullahbeam/nexus-design-abdullah --skill hubspot-update-deal

  • SKILL.md2.6 KB

Overview

This skill updates an existing deal in HubSpot CRM. It performs targeted edits such as changing the deal stage, amount, name, or close date and returns the updated deal record. Designed for quick edits when you know the deal ID. Includes pre-flight config checks and clear success or error responses.

How this skill works

The skill accepts a required deal ID and one or more update fields (name, amount, stage, closedate). It validates configuration, applies the requested property updates to the HubSpot deal, and returns the updated properties in JSON. If a deal ID is not known, run a search first to locate the correct ID before calling this skill.

When to use it

  • Move a deal to a new stage (e.g., move to Closed Won or Closed Lost).
  • Update the deal value after a contract change or negotiation.
  • Change the deal name to match a new contact or account naming convention.
  • Set or correct the expected close date for forecasting and reports.
  • Quickly correct property typos or update multiple fields on a single deal.

Best practices

  • Always run the config check prior to making updates to ensure authentication and scopes are valid.
  • Provide the deal ID to avoid ambiguity; if you only know the company name, search for the deal first and confirm the ID.
  • Only send the fields that need changing to minimize unintended updates.
  • Use valid stage IDs (see common stages) and ISO date format (YYYY-MM-DD) for close dates.
  • Handle API errors (401, 403, 404, 400, 429) by retrying, fixing scopes, or verifying the ID before repeating the update.

Example use cases

  • Move deal 5840795376 to the "closedwon" stage and set the close date to 2025-12-13.
  • Update deal 5840795376 amount to 75000 after a pricing revision.
  • Rename a deal to match the finalized contract: change dealname to "Acme Corp - Enterprise".
  • Close a deal as lost by setting dealstage to "closedlost" and adding context in notes.
  • Batch workflow: search for deals by company, then update the stage for matched IDs.

FAQ

Search deals by name first to retrieve the ID, then run the update with that ID.

What date format should I use for close dates?

Use YYYY-MM-DD (ISO) format for close dates to ensure correct parsing.

What if I get a 403 error?

Ensure your OAuth token includes the crm.objects.deals.write scope and reauthorize if necessary.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
hubspot-update-deal skill by abdullahbeam/nexus-design-abdullah | VeilStrat