HubSpot nodes
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.
Why these nodes
Section titled “Why these nodes”A deterministic write after you already know the phone or email. Triggers HubSpot Contact Created / Property Changed are Workflow Triggers plus the same connection.
Which node
Section titled “Which node”Catalog titles:
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”-
On Call End → Manage Contact in HubSpot. Operation Create or update. Phone = caller number.
-
Save & go live, attach, hang up. Open the contact in HubSpot.
What “broken” looks like
Section titled “What “broken” looks like”- 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.
Troubleshooting
Section titled “Troubleshooting”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.”
