Skip to content
EN
Open app

HubSpot nodes

2 min read
Copy as Markdown
View as MarkdownOpen the raw .md file.md

HubSpot in the palette is one node per object. Each card stays Setup required until HubSpot is connected on Integrations. The agent HubSpot tool (caller ID, live property updates) is that page — this page is the graph.

A deterministic write after you already know the phone or email. Triggers HubSpot Contact Created / Property Changed are Workflow Triggers plus the same connection.

Catalog titles:

Find or upsert the person
TURN ONManage Contact in HubSpotNEEDSGet / Get or create / Create or update / List / Search / Delete. Phone from Call Parameters.
The company
TURN ONManage Company in HubSpotNEEDSName + domain on create.
A deal or a ticket
TURN ONManage Deal / Manage TicketNEEDSPipeline + stage on create.
A follow-up for a human
TURN ONManage Task in HubSpotNEEDSTitle required. Owner + due date.
A note on the record
TURN ONCreate Note in HubSpotNEEDSBody required. Associations link it.
Log the activity
TURN ONLog Call / Log Email / Schedule MeetingNEEDSOn a phone trigger, call metadata (direction, duration) is filled from the call — do not set it by hand.

Operation is required on every card. Lookup fields use Get by / Value ({{call.phone_number}}). Create fields flip with the operation.

Ports follow the object (Contact: Contact saved / HubSpot error / No wait).

Galaxy, Shopify, Soft1, WooCommerce, Salesforce, Guesty are the same rule: connect on Integrations, then add that provider’s node. They do not get their own pages here.

First setup — upsert the caller after hang-up

Section titled “First setup — upsert the caller after hang-up”
  1. Connect HubSpot.

  2. On Call End → Manage Contact in HubSpot. Operation Create or update. Phone = caller number.

  3. Save & go live, attach, hang up. Open the contact in HubSpot.

  • Setup required — Integrations → HubSpot is not connected.
  • Empty contact — Value did not match (missing +, wrong Get by).
  • Call log fields you typed are ignored — a phone trigger already owns them.
Tool vs workflow node?

The tool is what the model may do while talking. The node is what the graph always does on that trigger. Use the node for “always file this contact.” Use the tool for “update a property they just confirmed.”