HubSpot Connector Tools

Overview

Before using this tool group, save a HubSpot connection in Config -> Connections. See HubSpot for Service Key setup, required scopes, and merge opt-in settings.Merges are permanent — HubSpot redirects both input record ids to the resulting record. REQUEST_MERGE_APPROVAL returns review_required; follow the shared CRM merge workflow before execution.

Tool Name

hubspot_connector_tools

Purpose

The hubspot_connector_tools group integrates Genesis with HubSpot CRM. Search and read contacts, companies, deals, and tickets; inspect properties and associations; create, update, and batch-upsert records; and merge duplicate contacts and companies.

Functions Available

hubspot_connector: Bounded HubSpot reads, record mutations, and merge preview / request / execute actions.

Input Parameters

`hubspot_connector`

Parameters

Name	Definition	Format	Default
action	Operation to perform. Supported: `TEST_CONNECTION`, `SEARCH_OBJECTS`, `GET_OBJECT`, `LIST_PROPERTIES`, `LIST_ASSOCIATIONS`, `CREATE_OBJECT`, `UPDATE_OBJECT`, `BATCH_UPSERT`, `PREVIEW_MERGE`, `REQUEST_MERGE_APPROVAL`, `EXECUTE_APPROVED_MERGE`, `GET_MERGE_APPROVAL`.	String (required)	none
connection	HubSpot connection name such as `hubspot.production`. Merge actions require an explicit connection; other actions may use the effective default.	String	none
object_type	HubSpot CRM object type, such as `contacts` or `companies`. Merge actions support only `contacts` and `companies`.	String	none
record_id	HubSpot CRM object id for `GET_OBJECT`, `UPDATE_OBJECT`, or `LIST_ASSOCIATIONS`.	String	none
filter_groups	HubSpot `filterGroups` for `SEARCH_OBJECTS`.	Array of objects	none
properties	Properties to return or include in a merge preview projection.	Array of strings	none
associations	HubSpot association payload for `CREATE_OBJECT`.	Array of objects	none
to_object_type	Destination HubSpot object type for `LIST_ASSOCIATIONS`.	String	none
data	Properties object for `CREATE_OBJECT` or `UPDATE_OBJECT`.	Object	none
inputs	HubSpot batch upsert input objects for `BATCH_UPSERT` (maximum `100` per request).	Array of objects	none
limit	Maximum results for `SEARCH_OBJECTS` or `LIST_ASSOCIATIONS`.	Integer	none
after	HubSpot paging cursor for `SEARCH_OBJECTS` or `LIST_ASSOCIATIONS`.	String	none
survivor_id	First numeric HubSpot input id, sent as `primaryObjectId`. HubSpot determines the resulting record id and redirects both input ids to it.	String	none
loser_ids	Exactly one second numeric HubSpot input id to merge with `survivor_id`.	Array of strings	none
expected_digest	Optional preview digest that `REQUEST_MERGE_APPROVAL` must reproduce.	String	none
ttl_seconds	Lifetime of a pending HubSpot merge approval in seconds.	Integer	`3600`
approval_id	Action Review proposal ID returned by `REQUEST_MERGE_APPROVAL`, required by `EXECUTE_APPROVED_MERGE` or `GET_MERGE_APPROVAL`.	String	none

Read-only connections: When the connection locator sets read_only to a truthy value, or access_intent to read or read_only, write and merge actions are refused.Merge opt-in: PREVIEW_MERGE, REQUEST_MERGE_APPROVAL, and EXECUTE_APPROVED_MERGE require merge_enabled on the connection locator and a valid merge_survivorship_policy JSON object with version and preview_fields. See HubSpot.HubSpot executions follow the shared CRM merge API outcome contract.Object allowlists: Genesis can read contacts, companies, deals, and tickets by default, and can create, update, or merge contacts and companies. An administrator can extend allowed object types through the hubspot.extra_objects App Config setting.Deletes unavailable: Archive and delete actions are not exposed through this tool group.

Merge workflow: Follow the shared CRM merge workflow.

HubSpot merges cannot be undone and accept exactly one loser. If a request times out or transport fails, reconcile HubSpot state before retrying. Example — search contacts

hubspot_connector(
    action="SEARCH_OBJECTS",
    connection="hubspot.production",
    object_type="contacts",
    filter_groups=[
        {
            "filters": [
                {"propertyName": "email", "operator": "EQ", "value": "[email protected]"},
            ],
        },
    ],
    properties=["email", "firstname", "lastname"],
    limit=10,
)

Example — merge preview

hubspot_connector(
    action="PREVIEW_MERGE",
    connection="hubspot.production",
    object_type="contacts",
    survivor_id="101",
    loser_ids=["202"],
)

Use Cases

Inspect CRM data — SEARCH_OBJECTS, GET_OBJECT, or LIST_PROPERTIES when a user asks about HubSpot contacts, companies, deals, or tickets.
Update a record — UPDATE_OBJECT or BATCH_UPSERT when a workflow should write back to HubSpot.
Duplicate review — PREVIEW_MERGE to show what a contact or company merge would do before any write.
Governed merge — Follow the shared CRM merge workflow.

Getting Started

Getting to Know Genesis

Creating A Mission

User Guide

Blueprint

Genesis Data Agents

Genesis Prover

Genesis Apps

Genesis REST API

Genesis Agent Security Controls

Genesis Data Agent's Toolkit

Setup

Slack and Teams

Data Connections

Deployment Options

Overview

Tool Name

Purpose

Functions Available

Input Parameters

`hubspot_connector`

Use Cases

​Overview

​Tool Name

​Purpose

​Functions Available

​Input Parameters

​hubspot_connector

​Use Cases

​Related pages

Overview

Tool Name

Purpose

Functions Available

Input Parameters

`hubspot_connector`

Use Cases

Related pages