Short answer: Drop the "GoHighLevel → Send GoHighLevel Email" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
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.
Triggered by anything in the catalog. Free tier available. No credit card.