> For the complete documentation index, see [llms.txt](https://agpt.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://agpt.co/docs/integrations/block-integrations/contact.md).

# HubSpot Contact

Blocks for managing HubSpot contact records in the CRM.

## Hub Spot Contact

### What it is

Manages HubSpot contacts - create, update, and retrieve contact information

### How it works

This block interacts with the HubSpot CRM API to manage contact records. It supports creating new contacts, updating existing contacts, and retrieving contacts by email address.

Contact data includes standard properties like email, first name, last name, phone, and any custom properties defined in your HubSpot account.

### Inputs

| Input         | Description                                | Type            | Required |
| ------------- | ------------------------------------------ | --------------- | -------- |
| operation     | Operation to perform (create, update, get) | str             | No       |
| contact\_data | Contact data for create/update operations  | Dict\[str, Any] | No       |
| email         | Email address for get/update operations    | str             | No       |

### Outputs

| Output  | Description                           | Type            |
| ------- | ------------------------------------- | --------------- |
| error   | Error message if the operation failed | str             |
| contact | Contact information                   | Dict\[str, Any] |
| status  | Operation status                      | str             |

### Possible use case

**Lead Capture**: Create contacts automatically from form submissions or integrations.

**Contact Updates**: Update contact information when customers change their details.

**CRM Lookup**: Retrieve contact details for personalization or workflow decisions.

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://agpt.co/docs/integrations/block-integrations/contact.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.