For the complete documentation index, see llms.txt. This page is also available as Markdown.

Create Note

Creates a standalone note in HubSpot that is not attached to any ticket or contact. Use "Add Internal Ticket Note" instead when the note belongs to a ticket.

Action identifier: create_note. Reference checked: 29 September 2026.

Inputs

Field
Type
Required/default
Meaning

content

string

Required

The body text of the standalone note. This field supports HTML formatting. Use HTML tags (e.g., <br>, <b>, <ul>) instead of Markdown.

Output shape

Paths are relative to this action's output. Select them from the builder's variable picker; do not add a ticket wrapper to actions that return top-level fields. Nullable property fields and empty defaults are not proof that a value was retrieved.

Path
Type
Meaning

note

object

Returned CRM Note data; may be a default object when no data is returned.

note.id

string

HubSpot record ID.

note.properties

object

Property values returned for this record; some declared fields may be empty.

note.properties.hs_note_body

string | null

The body of the note

note.createdAt

string

Creation timestamp returned by HubSpot; empty when unavailable.

note.updatedAt

string

Last-update timestamp returned by HubSpot; empty when unavailable.

note.archived

boolean

Archive flag returned by HubSpot; defaults to false when omitted.

success

boolean

True when HubSpot returns created Note data. This does not mean the Note is attached to a record.

exists

boolean

True when created Note data is returned; false when no Note data is returned.

Property objects can contain additional fields returned by HubSpot. The declared fields above are not a promise that every property is populated.

Behavior and limits

Creates a standalone CRM Note with the current UTC timestamp. It does not attach the Note to a record. Use Associate Objects with the correct supported type, or use Add Internal Ticket Note when the desired destination is a ticket.

No created Note data produces false flags. Successful creation is not proof of an association. Verify the destination timeline after a separate association step.

See Troubleshooting for request errors and retry behavior, or return to the action catalog.

Was this helpful?