Workflow Sender Domain Selection
TL;DR
GoHighLevel workflows now allow selecting a specific sender domain for all emails within that workflow.

TL;DR
Workflows can now use specific, verified sender domains for all emails. This is a minor update, not requiring immediate action for most.
Who this affects
HighLevel has not confirmed who this affects. It is relevant for anyone managing email sender reputation or branding across multiple client workflows.
What changed
- Workflow settings now include a sender domain dropdown under sender details.
- Users can select any verified domain on the sub account for a workflow.
- Every email action in a workflow sends from the selected domain by default.
- Different workflows can use completely different sender domains.
- Entering a full sender email on a different domain overrides the selected domain.
HighLevel has not confirmed any limits or plan gating for this feature. HighLevel has not confirmed the rollout status for this feature.
Where to find it
This feature is located within Workflow settings, under sender details.
How agencies will use this
An agency managing multiple brands or services within a single HighLevel sub-account can now assign specific email sender domains to individual workflows. For example, a sub-account might handle both 'Client A's Lead Generation' and 'Client B's Customer Support'. Previously, all workflow emails would typically originate from a single default domain. Now, the agency can set 'client-a-leads.com' as the sender domain for a lead nurture workflow for Client A, and 'client-b-support.com' for a support ticket automation workflow for Client B. This ensures consistent branding and proper sender reputation management specific to each client or function without requiring separate sub-accounts or manual overrides on every email action.
Our take
This is a standard product enhancement. It provides more granular control over email sending within workflows. It is a minor update. It addresses a common need for agencies managing diverse client needs or multiple internal brands under one sub-account. You do not need to drop everything to implement this, but it offers a clean solution for specific branding requirements.
Source: Official HighLevel announcement


