GActionGoHighLevelUpdated September 2026
How do I add a GoHighLevel contact note?
Short answer: You can add gohighlevel note in GoHighLevel by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GoHighLevel Add GoHighLevel Note action to a workflow, map its 3 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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.
Triggered by
Apps that pair well as the trigger for Add GoHighLevel Note.
Any of these apps can fire this action as part of a workflow.
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 run history shows the failed step with its input and the error message GoHighLevel returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Add GoHighLevel Note support batch operations?
Run Add GoHighLevel Note inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within GoHighLevel's rate limits.
More actions
Other GoHighLevel actions.
Action
Create GoHighLevel Contact
Inserts a contact with email, name, phone, custom fields, and starting tags. The base hook for "form submission → push to GHL" sync workflows in agency-managed sub-accounts.
ActionCreate GoHighLevel Opportunity
Creates an opportunity with value, stage, owner, contact link. For "qualified lead → auto-create opportunity in the right pipeline" workflows.
ActionGet GoHighLevel Contact
Returns a contact by ID with all standard and custom fields plus tags, opportunities, and recent activities. The standard lookup before update or for context-enrichment workflows.
ActionSearch GoHighLevel Contacts
Lookup by email, phone, name, or tag. The standard "find before update" dedupe pattern for upsert workflows.
ActionSend GoHighLevel Email
Sends a one-shot email to a contact via the GHL email system. Useful for transactional sends triggered by external events that should appear in the GHL contact timeline.
ActionSend GoHighLevel SMS
Sends SMS via the GHL number tied to the contact's sub-account. For "reminder SMS for appointments" or "promo SMS for the campaign" workflows where the message appears in the GHL conversation thread.