Short answer: Drop the "HubSpot → Create Note" 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 |
|---|---|---|---|
Note Content body | string | Required | Message body content. Plain text unless the API specifies HTML/markdown. |
Timestamp (epoch ms) hs_timestamp | string | Required | Timestamp in milliseconds since epoch (e.g. 1712835600000). HubSpot rejects notes without this. Use a workflow expression like Date.now() or pass the trigger event's occurredAt. |
Associated Contact ID contact_id | string | Optional | HubSpot contact record ID — a numeric string assigned by HubSpot. Find via Search Contacts or List Contacts. Not the email. |
Associated Deal ID deal_id | string | Optional | HubSpot deal record ID — a numeric string. Find via List Deals. |
Associated Company ID company_id | string | Optional | HubSpot company record ID — a numeric string. Find via List Companies. Not the company domain. |
{"body": "e.g. Hi there, thanks for reaching out.","hs_timestamp": "1712835600000","contact_id": "e.g. 123456789","deal_id": "e.g. 9876543210","company_id": "e.g. 1234567890"}
{"id": "note123","properties": {"hs_note_body": "Called customer to follow up","hs_timestamp": "1712835600000"}}
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.