Add GoHighLevel Note: GoHighLevel action

Inputs

The fields this action accepts.

Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.

Field	Type	Required	Description
Contact ID contactId	string	Required	The contact to attach the note to.
Note body	string	Required	Note text. Plain text or basic HTML.
Authoring User ID userId	string	Optional	GHL user to credit as the note author. Defaults to the connected user.

Sample request

{
  "contactId": "ocQHyuzHvysMo5N5VsXc",
  "body": "Spoke with Jane — ready for demo on Friday.",
  "userId": "user_xyz"
}

Returns

{
  "note": {
    "id": "note_abc123",
    "body": "Spoke with Jane — ready for demo on Friday.",
    "userId": "user_xyz",
    "contactId": "ocQHyuzHvysMo5N5VsXc",
    "dateAdded": "2026-04-11T10:00:00.000Z"
  }
}

Use these fields in downstream nodes for routing, logging, or error handling.

FAQ

Questions about Add GoHighLevel Note.

What does the Add GoHighLevel Note action do in GoHighLevel?

Attaches a note to a contact's timeline. Useful for "call summary → log to contact" or "support ticket resolution → add to client history" workflows.

What inputs does Add GoHighLevel Note require?

Required: Contact ID, Note. Every input accepts a static value or a variable from any upstream node in your workflow.

Can I use dynamic inputs from earlier workflow nodes?

Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.

What happens if GoHighLevel returns an error?

The workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Add GoHighLevel Note support batch operations?

Yes. Run Add GoHighLevel Note inside a Loop node to process arrays. Tiny Command handles GoHighLevel's rate limits automatically so you don't have to throttle manually.

More actions