For the complete documentation index, see llms.txt. This page is also available as Markdown.

Get Deal

Fetches the details of a specific deal in HubSpot, such as the deal name, stage, amount and close date.

Action identifier: get_deal. Reference checked: 29 September 2026.

Inputs

Field
Type
Required/default
Meaning

deal_id

string

Required

The ID of the deal to fetch

Output shape

Paths are relative to this action's output. Select them from the builder's variable picker; do not add a ticket wrapper to actions that return top-level fields. Nullable property fields and empty defaults are not proof that a value was retrieved.

Path
Type
Meaning

deal

object

Returned deal data; may be a default object when no data is returned.

deal.id

string

HubSpot record ID.

deal.properties

object

Property values returned for this record; some declared fields may be empty.

deal.properties.dealname

string | null

The name of the deal

deal.properties.amount

string | null

The monetary amount of the deal

deal.properties.dealstage

string | null

The current stage of the deal

deal.properties.pipeline

string | null

The pipeline ID

deal.properties.closedate

string | null

The close date of the deal

deal.createdAt

string

Creation timestamp returned by HubSpot; empty when unavailable.

deal.updatedAt

string

Last-update timestamp returned by HubSpot; empty when unavailable.

deal.archived

boolean

Archive flag returned by HubSpot; defaults to false when omitted.

exists

boolean

True when the deal is returned; false when no deal data is returned.

Property objects can contain additional fields returned by HubSpot. The declared fields above are not a promise that every property is populated.

Behavior and limits

Reads a deal by ID with HubSpot's default returned properties. Declared property fields do not guarantee every value was fetched. For custom fields use Get Object Associations or an explicit properties list in Search CRM Objects.

A missing deal returns a default object and exists: false.

See Troubleshooting for request errors and retry behavior, or return to the action catalog.

Was this helpful?