Send GoHighLevel SMS: 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 message.
Message message	string	Required	SMS body. Keep under 160 chars to fit one segment.
From Number fromNumber	string	Optional	Specific GHL number to send from. Defaults to the location's primary number.

Sample request

{
  "contactId": "ocQHyuzHvysMo5N5VsXc",
  "message": "Hi Jane — confirming your appointment for tomorrow at 3pm.",
  "fromNumber": "+18005551234"
}

Returns

{
  "status": "queued",
  "messageId": "msg_xyz789",
  "conversationId": "conv_abc123"
}

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

FAQ

Questions about Send GoHighLevel SMS.

What does the Send GoHighLevel SMS action do in GoHighLevel?

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.

What inputs does Send GoHighLevel SMS require?

Required: Contact ID, Message. 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 Send GoHighLevel SMS support batch operations?

Yes. Run Send GoHighLevel SMS 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