> For the complete documentation index, see [llms.txt](https://docs.ebbot.ai/ebbot-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ebbot.ai/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions/get-contact.md).

# Get Contact

Fetches the details of a specific contact in HubSpot, such as name, email and phone number. The contact can be looked up either by ID or by email address.

**Action identifier:** `get_contact`. **Reference checked:** 29 September 2026.

## Inputs

| Field        | Type   | Required/default | Meaning                                                                      |
| ------------ | ------ | ---------------- | ---------------------------------------------------------------------------- |
| `contact_id` | string | `""`             | The ID of the contact to fetch                                               |
| `email`      | string | `""`             | The email address of the contact to fetch (used when no contact ID is given) |

## 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                                                                      |
| ------------------------------ | -------------- | ---------------------------------------------------------------------------- |
| `contact`                      | object         | Returned contact data; may be a default object when no data is returned.     |
| `contact.id`                   | string         | HubSpot record ID.                                                           |
| `contact.properties`           | object         | Property values returned for this record; some declared fields may be empty. |
| `contact.properties.firstname` | string \| null | First name of the contact                                                    |
| `contact.properties.lastname`  | string \| null | Last name of the contact                                                     |
| `contact.properties.email`     | string \| null | Email address of the contact                                                 |
| `contact.properties.phone`     | string \| null | Phone number of the contact                                                  |
| `contact.properties.company`   | string \| null | Company name                                                                 |
| `contact.properties.website`   | string \| null | Website URL                                                                  |
| `contact.createdAt`            | string         | Creation timestamp returned by HubSpot; empty when unavailable.              |
| `contact.updatedAt`            | string         | Last-update timestamp returned by HubSpot; empty when unavailable.           |
| `contact.archived`             | boolean        | Archive flag returned by HubSpot; defaults to false when omitted.            |
| `exists`                       | boolean        | True when the contact is returned; false when no contact 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

Supply `contact_id` or `email`; if both are set, the ID takes precedence. Neither supplied causes an error. A missing contact returns a default contact and `exists: false`.

The action requests the fixed property list below. A field being present in the output model does not guarantee HubSpot returned a value. Use an explicit property read/search when additional fields are needed.

### Requested properties

This action explicitly requests `email`, `firstname`, `lastname`, `phone`, `hs_object_id`, `createdate`, `lastmodifieddate`. Other fields declared in its output model are not automatically fetched.

See [Troubleshooting](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/troubleshooting.md) for request errors and retry behavior, or return to the [action catalog](/ebbot-docs/integrations/automations-integrations/integration-setup-guides/hubspot-integration-in-automations/actions.md).