Get Contact: 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
Contact ID contact_id	string	Required	HubSpot contact record ID — a numeric string assigned by HubSpot. Find via Search Contacts or List Contacts. Not the email.
Properties properties	string	Optional	Comma-separated property names to include. Leave empty for defaults.

Sample request

{
  "contact_id": "e.g. 501",
  "properties": "e.g. email,firstname,lastname,phone"
}

Returns

{
  "id": "501",
  "properties": {
    "email": "user@example.com",
    "lastname": "Doe",
    "firstname": "John"
  }
}

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

FAQ

Questions about Get Contact.

What does the Get Contact action do in HubSpot?

Retrieves a HubSpot contact by ID with all of its standard and custom properties. The standard read after a trigger fires with a contact ID.

What inputs does Get Contact require?

Required: Contact ID. Every input accepts a static value or a variable from any upstream node in your workflow.

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 Get Contact support batch operations?

Yes. Run Get Contact 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