Hubspot logo

Search Deals (HubSpot)

HubSpot → Search Deals (HubSpot)

POST/v1/hubspot-search-deals
texau__hubspot-search-dealscrm
Run in Studio →Open in MCP
cURL · api.texau.app
84ms
POST/v1/hubspot-search-deals
{
  "propertyname": "Jane Doe",
  "operator": "sample-value",
  "value": "sample-value",
  "query_string": "sample-value",
  "sort_by": "sample-value",
  "sort_direction": "sample-value",
  "limit": 1,
  "after": "sample-value"
}
200 Accepted
{
  "ok": true,
  "data": {
    "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",
    "total": 1,
    "next_after": "sample"
  }
}

Search for deals using a text query or specific filters

Install

Add search deals (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.

claude_desktop_config.json
{
  "mcpServers": {
    "texau": {
      "command": "npx",
      "args": ["-y", "@texau/mcp-server"],
      "env": { "TEXAU_API_KEY": "..." }
    }
  }
}

Tool name: texau__hubspot-search-deals

When to use this.

The "Search Deals (HubSpot)" action enables users to efficiently search for deals within the HubSpot CRM by utilizing a text query or specific filters. Key input parameters include 'propertyname' for filtering by attributes like 'dealname' or 'amount', 'operator' to define the filter logic, and 'value' to specify the filter criteria. Users can also employ 'querystring' for broader text searches, while 'sortpropertyname' and 'sortdirection' allow for organized results. The action returns a comprehensive set of output fields, including deal ID, creation and update dates, deal stage, amount, close date, and more, providing valuable insights into each deal's status and details. This action is ideal for sales teams looking to streamline deal management, analyze performance, and prioritize follow-ups, making it a vital tool in CRM operations.

Try it

Run a sample request.

The response is a deterministic, cached example. No live call, no credits used.

Search Deals (HubSpot)

Try it

The name of the property to filter by (e.g., 'dealname', 'amount').

The operator for the filter (e.g., EQ, CONTAINS_TOKEN). Required if Filter Property Name is used.

The value to filter for. Required if Filter Property Name is used.

Query string for text search across multiple fields.

The property to sort the results by.

The direction to sort (ASCENDING or DESCENDING).

Response is cached — no live API call.

Response

Output schema.

Every field returned in `data`. Click rows to expand nested objects.

FieldType
  • id
    Id
    text
  • created_at
    Created At
    nullabletext
  • updated_at
    Updated At
    nullabletext
  • archived
    Archived
    nullableboolean
  • deal_name
    Deal Name
    text
  • pipeline
    Pipeline
    text
  • deal_stage
    Deal Stage
    text
  • amount
    Amount
    number
  • close_date
    Close Date
    text
  • deal_type
    Deal Type
    nullabletext
  • description
    Description
    nullabletext
  • priority
    Priority
    nullabletext
  • analytics_source
    Analytics Source
    nullabletext
  • closed_lost_reason
    Closed Lost Reason
    nullabletext
  • closed_won_reason
    Closed Won Reason
    nullabletext
  • next_step
    Next Step
    nullabletext
  • deal_stage_probability
    Deal Stage Probability
    nullablenumber
  • deal_collaborator_owner_id
    Deal Collaborator Owner Id
    nullabletext
  • creator_date
    Creator Date
    nullabletext
  • last_modified_date
    Last Modified Date
    nullabletext
  • hubspot_owner_id
    Hubspot Owner Id
    nullabletext
  • total
    Total
    nullablenumber
  • next_after
    Next After
    nullabletext

Integrate

Copy-pasteable snippets.

Real endpoint: https://v3-api.texau.com/api/v1/hubspot-search-deals. Auth: x-api-key.

cURL · api.texau.app
84ms
POST/v1/hubspot-search-deals
curl -X POST 'https://v3-api.texau.com/api/v1/hubspot-search-deals' \
  -H 'x-api-key: $TEXAU_API_KEY' \
  -H 'content-type: application/json' \
  -d '{"propertyname":"Jane Doe","operator":"sample-value","value":"sample-value","query_string":"sample-value","sort_by":"sample-value","sort_direction":"sample-value","limit":1,"after":"sample-value"}'
200 Accepted
{
  "ok": true,
  "data": {
    "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",
    "total": 1,
    "next_after": "sample"
  }
}

Compose

How this fits a workflow.

The next 2 actions most operators chain after this one.

Search Deals (HubSpot)→List Contacts (HubSpot)→Get Contact (HubSpot)

Output

Results land in a TexAu table.

Sample rows below.

Real result preview coming soon.

InputStatusScore
[email protected]valid96
[email protected]risky54
[email protected]invalid12

Workflow

A real example.

Trigger → search deals (hubspot) → enrich → push to your CRM. ~80 ms operator effort, the rest runs in the background.

Step 1TriggerNew row, webhook, or schedule.
Step 2Search Deals (HubSpot)HubSpot action runs.
Step 3EnrichWaterfall fills missing fields.
Step 4Push to CRMHubSpot / Salesforce / Pipedrive.

Built for

Who runs this.

GTM EngineerRevOpsAgency

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.

CodeCauseFix
200 OKAction ran. Data in `data`.Read response.
400 Bad RequestMissing or malformed input.Validate against the input schema.
401 UnauthorizedMissing or invalid `x-api-key`.Re-issue from /api-platform.
403 ForbiddenWorkspace lacks plan tier.Upgrade or contact sales.
404 Not FoundAction key not recognized.Verify the slug.
429 Rate LimitedPer-minute or per-day cap hit.Backoff; reduce concurrency.
500 Server ErrorUnexpected TexAu issue.Retry with backoff.
502 Bad GatewayUpstream provider 5xx.Retry; we surface root cause.
504 TimeoutUpstream slower than maxLatency.Switch to `isAsync` polling.

Pricing

What it costs to run.

Light tier

Pricing tier on /pricing. Per-action credit cost is private.

Related

More HubSpot actions.

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 Search Deals (HubSpot) in 60 seconds.

Pull your API key, paste the cURL, ship to your CRM.

Start free →Read the API docs