Search Deals: HubSpot action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Search Query query	string	Optional	Search by deal name
Limit limit	number	Optional	Maximum results (max 50)

Sample request

{
  "query": "{{trigger.query}}",
  "limit": "{{trigger.limit}}"
}

Returns

{
  "total": 3,
  "results": [
    {
      "id": "456",
      "properties": {
        "amount": "50000",
        "dealname": "Enterprise Deal",
        "dealstage": "closedwon"
      }
    }
  ]
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Search Deals.

What does the Search Deals action do in HubSpot?

Searches deals in HubSpot CRM by name, stage, amount, owner, or custom property. Powers pipeline reports and complex upsert lookups.

What inputs does Search Deals require?

Search Deals has no required inputs. Sensible defaults are applied if you leave fields blank.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if HubSpot returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Search Deals support batch operations?

Yes. Run Search Deals inside a Loop node to process arrays. Tiny Command handles HubSpot's rate limits automatically so you don't have to throttle manually.

More actions