Create Deal (HubSpot)
HubSpot → Create Deal (HubSpot)
/v1/hubspot-create-deal{ "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", "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" } }
Creates a new deal in HubSpot with amount, stage, close date, and associations to contacts or companies.
Install
Add create 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-create-deal
When to use this.
The "Create Deal (HubSpot)" action facilitates the creation of new deals within the HubSpot CRM, enabling businesses to manage their sales pipeline effectively. Key input parameters include "dealname" for specifying the deal's title, "amount" to define its monetary value, and "closedate" to indicate the anticipated closing date. Optional parameters such as "pipeline," "dealstage," and "hs_priority" allow for further customization of the deal's attributes. The action outputs essential data, including "deal_id," "created_at," and "updated_at," along with detailed information about the deal's status and characteristics. This action is particularly useful for sales teams looking to streamline deal tracking, enhance collaboration, and improve sales forecasting, making it an invaluable tool in the CRM category.
Try it
Run a sample request.
The response is a deterministic, cached example. No live call, no credits used.
Create 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-create-deal. Auth: x-api-key.
/v1/hubspot-create-dealcurl -X POST 'https://v3-api.texau.com/api/v1/hubspot-create-deal' \ -H 'x-api-key: $TEXAU_API_KEY' \ -H 'content-type: application/json' \ -d '{"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","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 → create 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 Create Deal (HubSpot) in 60 seconds.
Pull your API key, paste the cURL, ship to your CRM.