Short answer: You can send gohighlevel email in GoHighLevel by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GoHighLevel Send GoHighLevel Email action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
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 email. |
Subject subject | string | Required | Email subject line. |
HTML Body html | string | Optional | HTML email body. Use this for formatted/branded emails. |
Plain Text Body text | string | Optional | Plain-text fallback. Provide html OR text — at least one is required. |
From Email fromEmail | string | Optional | Sender address. Defaults to the location's configured sender. |
From Name fromName | string | Optional | Sender display name. |
{"contactId": "ocQHyuzHvysMo5N5VsXc","subject": "Welcome to Acme","html": "<p>Hi {{contact.firstName}}, welcome aboard!</p>","text": "Hi Jane, welcome aboard!","fromEmail": "support@acme.com"}
{"status": "sent","messageId": "msg_xyz789","conversationId": "conv_abc123","emailMessageId": "email_xyz"}
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.