Input node
HubSpot
Read HubSpot CRM objects: contacts, companies, deals and tickets.
HubSpotWhat it does
Reads HubSpot CRM objects (contacts, companies, deals, tickets, or a custom object) through a saved Connection, following HubSpot's cursor paging to the end. You choose the object and, importantly, which properties to bring back. The object's fields arrive under dotted properties.* columns.
Inputs and outputs
| Inputs | None. This node starts a pipeline. |
| Outputs | One. |
When to use it
- Load CRM records into a warehouse
- Join marketing data with sales or finance data
- Snapshot a CRM object on a schedule so you can see how it changed
Examples
Contacts
Object: contacts · Properties: email, firstname, lastname
Naming properties is much faster than taking HubSpot's default set.
Deals
Object: deals
Leave Properties blank and HubSpot decides what to return.
A custom object
Object: p1234567_projects
Custom objects are read by their id, exactly like a standard one.
Include archived
Extra parameter: archived = true
HubSpot's own parameters are passed straight through.
Tips
- Ask for only the properties you need. HubSpot returns a default set otherwise, which is both slower and wider than you want.
- The credential is a Service Key, created under Settings → Integrations in HubSpot. Give it a read scope for each object you want: a key with no scope for the object still passes Test but returns nothing. A legacy private-app token also works.
- Fields land under dotted properties.* columns. Rename them with Manage Columns before writing to a database that dislikes dots.
- Max records is a real cap: it stops mid-page rather than delivering the rest of the page you were on.
- Use “Fetch sample” to fill in the columns so downstream nodes see them without a run.