Update Deal (HubSpot)
HubSpot → Update Deal (HubSpot)
/v1/hubspot-update-deal{ "deal_id": "sample-value", "deal_name": "Jane Doe", "pipeline": "sample-value", "deal_stage": "sample-value", "amount": 1, "close_date": "sample-value", "deal_type": "sample-value", "priority": "sample-value", "analytics_source": "sample-value", "closed_lost_reason": "sample-value", "closed_won_reason": "sample-value", "creator_date": "sample-value", "deal_collaborator_owner_id": "sample-value", "description": "sample-value", "deal_stage_probability": "sample-value", "next_step": "sample-value" }
{ "ok": true, "data": { "deal_id": "rec_4f3a91", "created_at": "sample", "updated_at": "sample", "archived": true, "deal_name": "sample", "pipeline": "sample", "deal_stage": "sample", "amount": 1, "close_date": "sample", "deal_type": "sample", "description": "sample", "priority": "sample", "analytics_source": "sample", "closed_lost_reason": "sample", "closed_won_reason": "sample", "next_step": "sample", "deal_stage_probability": 1, "deal_collaborator_owner_id": "rec_4f3a91", "creator_date": "sample", "last_modified_date": "sample", "hubspot_owner_id": "rec_4f3a91" } }
Updates an existing HubSpot deal
Install
Add update deal (hubspot) to your MCP client.
Drop this into claude_desktop_config.json (or your client's equivalent) and the tool shows up in any chat.
{ "mcpServers": { "texau": { "command": "npx", "args": ["-y", "@texau/mcp-server"], "env": { "TEXAU_API_KEY": "..." } } } }
Tool name: texau__hubspot-update-deal
When to use this.
The "Update Deal (HubSpot)" action allows users to modify existing deals within the HubSpot CRM, ensuring that only specified properties are updated. Key input parameters include dealId, which identifies the deal to be updated, and optional fields such as dealname, pipeline, dealstage, amount, and closedate, among others. This flexibility enables users to tailor updates to their specific needs, whether adjusting deal amounts, changing stages, or updating descriptions. The output provides essential deal information, including deal_id, created_at, updated_at, and various deal attributes like priority and probability of winning. This action is particularly useful for sales teams looking to maintain accurate and up-to-date deal information, streamline their sales processes, and enhance collaboration among team members. As a part of the CRM category, it plays a crucial role in effective customer relationship management and sales tracking.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Update Deal (HubSpot)
Response
Output schema.
Every field returned in `data`. Click rows to expand nested objects.
deal_idDeal Idtextcreated_atCreated Atnullabletextupdated_atUpdated AtnullabletextarchivedArchivednullablebooleandeal_nameDeal NametextpipelinePipelinetextdeal_stageDeal StagetextamountAmountnumberclose_dateClose Datetextdeal_typeDeal TypenullabletextdescriptionDescriptionnullabletextpriorityPrioritynullabletextanalytics_sourceAnalytics Sourcenullabletextclosed_lost_reasonClosed Lost Reasonnullabletextclosed_won_reasonClosed Won Reasonnullabletextnext_stepNext Stepnullabletextdeal_stage_probabilityDeal Stage Probabilitynullablenumberdeal_collaborator_owner_idDeal Collaborator Owner Idnullabletextcreator_dateCreator Datenullabletextlast_modified_dateLast Modified Datenullabletexthubspot_owner_idHubspot Owner Idnullabletext
Integrate
Copy-pasteable snippets.
Real endpoint: https://v3-api.texau.com/api/v1/hubspot-update-deal. Auth: x-api-key.
/v1/hubspot-update-dealcurl -X POST 'https://v3-api.texau.com/api/v1/hubspot-update-deal' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"deal_id":"sample-value","deal_name":"Jane Doe","pipeline":"sample-value","deal_stage":"sample-value","amount":1,"close_date":"sample-value","deal_type":"sample-value","priority":"sample-value","analytics_source":"sample-value","closed_lost_reason":"sample-value","closed_won_reason":"sample-value","creator_date":"sample-value","deal_collaborator_owner_id":"sample-value","description":"sample-value","deal_stage_probability":"sample-value","next_step":"sample-value"}'
{ "ok": true, "data": { "deal_id": "rec_4f3a91", "created_at": "sample", "updated_at": "sample", "archived": true, "deal_name": "sample", "pipeline": "sample", "deal_stage": "sample", "amount": 1, "close_date": "sample", "deal_type": "sample", "description": "sample", "priority": "sample", "analytics_source": "sample", "closed_lost_reason": "sample", "closed_won_reason": "sample", "next_step": "sample", "deal_stage_probability": 1, "deal_collaborator_owner_id": "rec_4f3a91", "creator_date": "sample", "last_modified_date": "sample", "hubspot_owner_id": "rec_4f3a91" } }
Compose
How this fits a workflow.
The next 2 actions most operators chain after this one.
crm
List Contacts (HubSpot)
Retrieves all HubSpot contacts with email, name, phone, company, and custom properties.
Get Contact (HubSpot)
Retrieves a specific HubSpot contact by ID with all standard, demographic, and custom properties.
Create Company (HubSpot)
Creates a new company record in HubSpot with firmographic properties and optional associations.
Output
Results land in a TexAu table.
Sample rows below.
Real result preview coming soon.
| Input | Status | Score |
|---|---|---|
| [email protected] | valid | 96 |
| [email protected] | risky | 54 |
| [email protected] | invalid | 12 |
Workflow
A real example.
Trigger → update deal (hubspot) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.
Built for
Who runs this.
Reliability
Rate limits & reliability.
- Per-minute limitNo public cap
- Per-day limitPlan-defined
- RetriesAutomatic w/ backoff
- ModeSync
Errors
HTTP status codes.
What each response means and what to do about it.
| Code | Cause | Fix |
|---|---|---|
| 200 OK | Action ran. Data in `data`. | Read response. |
| 400 Bad Request | Missing or malformed input. | Validate against the input schema. |
| 401 Unauthorized | Missing or invalid `x-api-key`. | Re-issue from /api-platform. |
| 403 Forbidden | Workspace lacks plan tier. | Upgrade or contact sales. |
| 404 Not Found | Action key not recognized. | Verify the slug. |
| 429 Rate Limited | Per-minute or per-day cap hit. | Backoff; reduce concurrency. |
| 500 Server Error | Unexpected TexAu issue. | Retry with backoff. |
| 502 Bad Gateway | Upstream provider 5xx. | Retry; we surface root cause. |
| 504 Timeout | Upstream slower than maxLatency. | Switch to `isAsync` polling. |
Related
More HubSpot actions.
List Contacts (HubSpot)
Retrieves all HubSpot contacts with email, name, phone, company, and custom properties.
Get Contact (HubSpot)
Retrieves a specific HubSpot contact by ID with all standard, demographic, and custom properties.
Create Company (HubSpot)
Creates a new company record in HubSpot with firmographic properties and optional associations.
Search Contacts (HubSpot)
Search for HubSpot CRM contacts by email address or other filters and retrieve their properties.
FAQ.
Is this real-time?
Yes. Synchronous actions return in ~1–4 s. Long-running work uses async polling (see status 504 → switch to async).
Do I get charged on failure?
No. Verified failures cost zero credits. Provider miss / 5xx / timeout cascade to the next provider in the waterfall when applicable.
Does it work with Claude / Cursor via MCP?
Yes. Add the texau MCP server to your client config, then call `texau__hubspot-...` directly.
What CRMs can I push results to?
HubSpot, Salesforce, Pipedrive, Zoho, and GoHighLevel are bidirectional. Smartlead, Instantly, Lemlist, HeyReach, Apollo Sequences, and Reply.io for outbound.
Run Update Deal (HubSpot) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.