Short answer: Drop the "HubSpot → Update Contact" 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 |
|---|---|---|---|
Contact ID contact_id | string | Required | HubSpot contact record ID — a numeric string assigned by HubSpot. Find via Search Contacts or List Contacts. Not the email. |
Email email | string | Optional | Email. e.g. "user@example.com" |
First Name firstname | string | Optional | Contact's first (given) name. |
Last Name lastname | string | Optional | Contact's last (family) name. |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
Company company | string | Optional | Company |
Lifecycle Stage lifecyclestage | options | Optional | Lifecycle Stage. Options: Subscriber, Lead, Marketing Qualified Lead, Sales Qualified Lead, Opportunity, Customer |
{"contact_id": "e.g. 501","email": "user@example.com","firstname": "e.g. Jane","lastname": "e.g. Doe","phone": "e.g. +14155551234"}
{"id": "501","properties": {"email": "user@example.com","firstname": "John"}}
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.