Short answer: Drop the "HubSpot → Update Company" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Company ID company_id | string | Required | HubSpot company record ID — a numeric string. Find via List Companies. Not the company domain. |
Company Name name | string | Optional | Company Name |
Domain domain | string | Optional | Domain. Example: stripe.com |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
City city | string | Optional | City |
Industry industry | string | Optional | Industry |
{"company_id": "e.g. 1234567890","name": "{{trigger.name}}","domain": "e.g. stripe.com","phone": "e.g. +14155551234","city": "{{trigger.city}}"}
{"id": "123","properties": {"name": "Stripe","domain": "stripe.com"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.