HubSpot

Your HubSpot CRM, in two nodes on one connected credential. The action runs 51 operations — contacts, companies, deals and tickets, links between them (with labels), notes, tasks, calls and meetings, products and quotes, forms, conversations and lists — and can also be an AI toolkit. The trigger fires a flow when a record is created, deleted, merged or restored, any property changes — a deal's stage, a lifecycle stage, your own custom fields — records are linked, a form is submitted, or a conversation gets a message.

Setup

Connect HubSpot under Settings → Credentials, or straight from the node: name the credential, pick your HubSpot account and approve the HostWebhook app. The credential remembers which account it belongs to; reconnecting it to a different account is refused, because every trigger on it would start listening somewhere else.

The app asks for read and write on contacts, companies and deals, read on owners and on their properties — and, optionally, tickets, lists, products, line items, quotes, forms and conversations. An account without one of those products connects anyway, without those operations; the node says so instead of failing with a bare 403.

Operations

Picked from your account

Owner, Pipeline, Stage, List, the association Label, the Product, the Form, the Inbox, the values of properties like Lifecycle stage or Lead status, and the properties you filter by or add are picked from the connected account — your own pipelines and custom properties included. Typing an ID or a template ({{payload.ownerId}}) is in the picker's footer. Changing the pipeline clears the stage, which only exists in its own pipeline, and changing From or To clears the label, which belongs to that pair.

Other properties takes any property by its internal name — one per line (city: {{payload.city}}) or as JSON — and wins over the fields above if it repeats one. Empty fields are not sent: in an update, what you leave empty stays as it is in HubSpot.

IDs are HubSpot's record IDs (numbers), usually from the trigger ({{payload.objectId}}). The output keeps HubSpot's own shape — { id, properties, createdAt, updatedAt } — so its API reference applies as it is. Searches come back as { contacts: [...], count, total, hasMore } (or companies, deals, tickets), newest first, and the next node runs once per record.

Labels, calls, products, quotes, forms and conversations

• Link two records takes an optional Label (“Decision maker”, “Billing contact”) between those two kinds of record. The labels the two records already had stay. List association labels gives the IDs (USER_DEFINED:36).
• Log call and Log meeting put an activity that already happened — or a booked meeting — on the timeline of a contact, company, deal or ticket. A call's duration goes in seconds. A meeting needs an Owner: HubSpot doesn't create meetings without one.
• Add line item to deal puts a product from your library (or a one-off item with a name and a price) on a deal; the deal's amount follows its line items.
• Create quote makes a draft quote for a deal and its buyer with a copy of the deal's line items — HubSpot asks that quotes don't reuse the deal's own — and the account's default template. The deal needs line items first.
• Get form submissions reads a form's latest submissions, newest first, with the values by field name: {{item.values.email}}.
• Reply to conversation answers on the channel the customer used — email, chat — to whoever wrote last. It's sent as the HubSpot user in Send as, or, empty, as whoever the conversation is assigned to.

AI toolkit mode

Once the credential is picked, the node asks for a Mode. AI toolkit turns it into 51 tools that an AI Node — or an MCP client, through one of your MCP servers — calls by name: a sales assistant that finds a contact, moves the deal to the next stage and leaves a note on its timeline.

What you control

• Blocked tools. The seven deletes start blocked — the four CRM records, products, line items and the permanent GDPR delete. Unblock only what the agent really needs, under Block these tool calls.
• Characters per call sent to the model. 20,000 by default, anything from 1,000 to 200,000.

New tools reach your agents

When the HubSpot toolkit gains a tool — the 21 that arrived on October 11, 2026, for one — an AI Node that already used this node gets it without anyone adding it, unless it's blocked on the node. The AI Node's Tools tab lists the ones that arrived that way; remove one there and it won't come back to that agent.

What goes back to the model

The same response as the operation. Searches return 20 unless the model asks for more, up to 100. Pipeline, stage, owner, list, label and form IDs belong to the account, so the model is told to look them up with list_hubspot_pipelines, list_hubspot_owners, list_hubspot_lists, list_hubspot_association_labels and list_hubspot_forms instead of guessing them. Records that don't fit the characters limit are left out whole, with a notes field saying how many. Arguments are used as written: a {{payload.x}} the model writes is not resolved against the flow.

Testing a tool

{ "operation": "search_hubspot_contacts", "query": "sam.rivera@example.com" }

The trigger

Pick HubSpot as the service on a Trigger node and a HubSpot credential. Installing the HostWebhook app already sends the account's CRM changes to HostWebhook, so activating changes nothing in HubSpot and never expires: the trigger simply starts picking the events you chose, for that account.

What fires it

Event Trigger takes one or more; pick at least one. Changing them while the trigger is active counts from the next event, with nothing to apply. The property changes in the list cover the properties that matter most; for any other one — your own custom properties included — open Watch other properties and pick them per object. They fire like the ones in the list, with the whole record and the value before, usually within half a minute (they come through HubSpot's webhooks journal). HubSpot's journal doesn't record changes made by HostWebhook itself, so a flow that changes a watched property doesn't fire this trigger again — changes made in HubSpot, by people or other apps, do.

Form submitted needs the forms it watches: pick them under Forms. HubSpot has no webhook for form submissions, so HostWebhook checks every 5 minutes — and right away when HubSpot says a contact just converted. Submissions made before the trigger was activated — or before you added that form — don't run. New incoming conversation message fires when a customer writes in an inbox conversation (email, chat…); New outgoing conversation message when your team or a bot replies. Internal comments don't fire either.

What the trigger sends downstream

HubSpot's event only carries the record's ID, so HostWebhook reads the record before running the flow and puts it in record, with HubSpot's field names: the usual properties (name, email, stage, owner…), the one that changed, and the ones you add under More … properties in the record. A deleted record comes with its ID and record: null. A property change also brings previousValue, from the property's history (null when it was empty before).

{
  "type": "deal.propertyChange",
  "label": "Deal stage changed",
  "object": "deal",
  "objectId": "9201",
  "propertyName": "dealstage",
  "propertyValue": "closedwon",
  "previousValue": "contractsent",
  "occurredAt": "2026-10-10T17:02:11.000Z",
  "changeSource": "CRM_UI",
  "portalId": "12345678",
  "record": {
    "id": "9201",
    "properties": {
      "dealname": "Acme Corp — Pro plan",
      "amount": "1500",
      "dealstage": "closedwon",
      "pipeline": "default",
      "hubspot_owner_id": "75413921",
      "…": "…"
    },
    "createdAt": "2026-10-01T09:30:00.000Z",
    "updatedAt": "2026-10-10T17:02:11.000Z",
    "archived": false
  }
}

A conversation message and a form submission look like this:

{
  "type": "conversation.newMessage",
  "label": "New incoming conversation message",
  "object": "conversation",
  "direction": "incoming",
  "threadId": "8801",
  "messageId": "a1b2c3d4e5",
  "text": "Hi, I reset my password and still cannot log in.",
  "senderName": "Sam Rivera",
  "senderEmail": "sam.rivera@example.com",
  "contactId": "51",
  "message": { "…": "HubSpot's message" },
  "thread": { "…": "HubSpot's conversation" }
}

{
  "type": "form.submission",
  "label": "Form submitted",
  "object": "form",
  "formId": "5f1b7a2e-3c4d-4e5f-8a9b-0c1d2e3f4a5b",
  "formName": "Contact us",
  "submittedAt": "2026-10-10T17:05:40.000Z",
  "values": { "email": "sam.rivera@example.com", "firstname": "Sam", "message": "I would like a demo." },
  "pageUrl": "https://www.example.com/contact"
}

Trying it out

The trigger's Test push shows what each event you picked will look like — examples with the exact shape this trigger dispatches, so you can write {{payload.record.properties.email}} in the nodes below it from the start. To see a real one, create a contact or move a deal in your HubSpot account.

Gotchas

• Tickets, conversations and forms need their permission. They're optional when connecting; a trigger with those events on an account that didn't grant them refuses to activate and says why.
• Only static lists can be changed by hand. Lists that fill themselves from filters aren't offered. HubSpot now calls lists Segments: create one in More → CRM → Segments, with the type Static.
• A 429 is retried once. HubSpot allows 110 requests every 10 seconds per account; a flow that creates many records at once can touch it.
• Searches find new records after a moment. HubSpot indexes them a few seconds after they're created, so a search right after a create may not see it yet.
• A contact can bring a company along. If the account has HubSpot's setting to create companies from contact email domains turned on, creating a contact with sam@acme.com also creates (or links) the company acme.com — that's HubSpot, not the flow.
• Quotes need Revenue Hub Professional or Enterprise. On other accounts HubSpot refuses Create quote, and the line item copies it made are removed.
• A reply needs someone to send it. If the conversation isn't assigned and Send as is empty, the reply is refused and says so.