Get Deal by ID (HubSpot)
HubSpot → Get Deal by ID (HubSpot)
/v1/hubspot-get-deal-by-id{ "deal_id": "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" } }
Retrieve a single HubSpot deal record by its deal ID using the CRM v3 objects API
Install
Add get deal by id (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-get-deal-by-id
When to use this.
The "Get Deal by ID (HubSpot)" action allows users to retrieve detailed information about a specific deal in HubSpot's CRM by providing the unique deal ID. This action utilizes the CRM v3 objects API to fetch a comprehensive list of properties associated with the deal, including essential details such as deal name, amount, close date, and deal stage. The primary input parameter is the dealId (text), which identifies the deal to be retrieved. The output includes various fields such as deal_id (id), created_at (date), updated_at (date), archived (boolean), and additional attributes like deal type, priority, and probability. This action is particularly useful for sales teams and CRM administrators looking to access and manage deal information efficiently, making it an essential tool within the CRM category.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Get Deal by ID (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-get-deal-by-id. Auth: x-api-key.
/v1/hubspot-get-deal-by-idcurl -X POST 'https://v3-api.texau.com/api/v1/hubspot-get-deal-by-id' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"deal_id":"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 → get deal by id (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 limit100 / min
- Per-day limit24,000 / day
- 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 Get Deal by ID (HubSpot) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.