Structured HubSpot Agent
Configure an AI agent to find and update specific HubSpot objects and properties, with deterministic, property-level results you can reference downstream.

What It Does
For each object type you configure, the agent searches HubSpot using your search instructions, then updates each property you list using your extraction instructions. It can optionally use a linked meeting as context, create the object if it isn't found, and pause for human approval before creating a record or writing a specific property.
When To Use It
Use this for defined property writes where you need structured, auditable output, such as syncing several meeting-derived fields to a deal and reporting exactly what changed. This is the preferred agent for structured updates. Use Hubspot Agent instead only for free-form, exploratory requests that don't need structured output.
Configuration
Configure the node with these settings:
Field | What it controls |
|---|---|
Meeting | Optional meeting used as context for extracting property values. |
Object Configurations | One entry per object type to update. Required, at least one. External Object Type.: The HubSpot object type to update, for example deals or contacts. Required. Search Instructions.: Natural language instructions for how to find the right object or objects. Required. Create If Not Found.: Whether to create the object when no match is found. Defaults to |
Outputs
The node passes these values downstream. Check the Outputs tab on the configured node to confirm exact paths.
Variable | Type | Description | Example |
|---|---|---|---|
|
| Results for each object configuration, mirroring input structure |
|
|
| The search instructions that were used |
|
|
| Object IDs found/created by the search phase |
|
|
| Objects that were processed |
|
|
| HubSpot object ID |
|
|
| HubSpot object name/title |
|
|
| Status of each property update |
|
|
| Property internal name |
|
|
| Property human-readable label |
|
|
| The new value written to HubSpot |
|
|
| Integration push event ID for lookup |
|
|
| The AI reasoning used to generate the property update value |
|
|
| Update status |
|
|
| Error message if failed |
|
|
| Error if the configuration failed entirely |
|
|
| Lifecycle of object creation for this configuration (when create-if-not-found is used) |
|
|
| Machine-readable reason when object creation is pending review (e.g. pending_object_creation) |
|
|
| Total number of HubSpot records touched across all configurations |
|
|
| Human-readable summary of operations performed, with optional markdown links |
|
Example Workflow
After a renewal call, a workflow configures this node to find the linked deal and update its close_date and renewal_notes properties from the meeting, requiring confirmation on close_date, then posts the summary output to Slack.
Related Nodes
Hubspot Agent
Update Deal V2
Update Contact V2
Need More Help?
Reach the AskElephant support team by:
clicking the Support tab on the right side of your screen,
emailing [email protected],
or using
@askelephant supportin your dedicated Slack channel.