DocumentationWorkflowsApps and services
HubSpot Companies node
Search, read and edit standard and custom fields. Field definitions provide internal names and option values. Learn how to configure it, map inputs and outputs, run a test and resolve common errors.
9 min readUpdated
What this node does
Search, read and edit standard and custom fields. Field definitions provide internal names and option values.
Use HubSpot Companies as a clearly defined step in an anymize workflow.
- Processes one input.
- Provides one output for following steps.
- Runs as a regular step in the flow.
Set up the node
- 01Open a workflow and add HubSpot Companies from the node catalog.
- 02If your HubSpot account is not connected yet, connect it right in the node panel or under Connectors.
- 03Complete the required fields and map values from previous steps.
- 04Run the node with a small test record and inspect its output.
- 05Connect the successful output and activate the workflow after an end-to-end test.
Operations and modes
Choose the required function in Action. The panel then shows the relevant settings.
- Search and list
- Get
- Create
- Update
- Delete
- List properties
- Get property definition
Settings
| Field | Meaning | Area |
|---|---|---|
| Action | Choices: Search and list, Get, Create, Update, Delete, List properties, Get property definition | Standard |
| Search term | Configure this value in the node panel. | Standard |
| Limit (max. 100) | Configure this value in the node panel. | Standard |
| Record ID | Configure this value in the node panel. | Standard |
| Properties | Standard and custom properties as field and value. An empty value clears the field. | Standard |
| Create associations | HubSpot associations as an array with to.id and types. | Standard |
| Properties to read | Internal property names, separated by commas. Custom HubSpot properties are supported. Leave empty to use the defaults. | Standard |
| Next page | Use paging.next.after from the previous result. | Standard |
| Search filters | HubSpot filter groups with internal property names and operators. | Standard |
| Sort | One internal property name. Prefix it with a minus sign to sort in descending order. | Standard |
| Associated objects | Configure this value in the node panel. | Standard |
| Unique ID property | Optional internal name of a unique property instead of the record ID. | Standard |
| Internal property name | Configure this value in the node panel. | Standard |
| Run once per item | Off (default): the node runs once for the whole input. On: if it receives several items (e.g. from Split Out), it runs once PER item, and {{ $json }} is that one item each time. This is how you work through a file list entry by entry. | Standard |
| If one item fails | "Skip" writes an `error` field for the failed item and keeps processing the rest, instead of losing the whole run to a single unreadable file. | Standard |
| Pause between items (milliseconds) | Wait before every run except the first. 1000 = 1 second per item. Useful when the other side would otherwise throttle you. Maximum 300000 (5 minutes). | Standard |
Inputs and outputs
| Input | Meaning | Type |
|---|---|---|
| Standard | Receives the complete result from the previous step. | JSON |
| Output | Meaning | Type |
|---|---|---|
| Standard | Makes the result available to the next step as JSON. | JSON |
This node can process lists item by item. Error handling and the delay between items are available in advanced settings.
Example and test run
Test-run example: begin with a small, recognizable record. Inspect the output and only map fields that are present there.
Test-run example
{
"input": "value"
}Access and security
The node works with your own connected HubSpot account. It only sees and changes what this account is allowed to. Check the permissions shown when you connect.
"Allowed actions" in the settings of your HubSpot connection under Connectors also applies to this node and is checked on every run. With "Read only" or "Read and draft", only the read actions run: Search and list, Get, List properties, Get property definition. These actions need "Allow changes": Create, Update, Delete.
Keys and credentials belong in Workflow Secrets or your connected accounts. Never paste them as plain text into workflow fields, test data or descriptions.
Troubleshooting
- No output: inspect the latest run and confirm that the previous node returned the expected fields.
- Empty variable: open the previous step output and use a field name from the real test data.
- Connection rejected: reconnect the service and grant the permissions required by this step.
- Action blocked: set "Allowed actions" of the connection under Connectors to "Allow changes", or pick a read action.
- List processed once: enable per-item execution in advanced settings.