Workflow Builder: Pick Email Sender Domain per Workflow

TL;DR

Workflows now allow setting a specific email sender domain for all emails within that workflow. This is relevant if you manage multiple verified sending domains on a sub-account.

Who this affects

This affects Go HighLevel agency owners and SaaS entrepreneurs who manage email sending for clients, particularly those with multiple verified sender domains configured per sub-account. If a sub-account has no dedicated domains set up, this feature's options will not appear. HighLevel has not confirmed who else this might affect.

What changed

Workflow settings now include a "Sender domain" dropdown under "Sender details." This dropdown lists all verified dedicated domains on the sub-account, plus an "All domains" option. Selecting "All domains" will distribute email sends across the configured domains. Choosing a specific domain requires entering an email prefix, for example, marketing@example.com. All email actions within that workflow will then send from the selected domain. Only verified domains from Email Services will appear in this dropdown. If a full sender email is entered on a different domain, it will override the workflow's selected domain and trigger a mismatch warning. Details set within an individual email action take final preference over workflow-level settings. Additionally, email headers configured in dedicated email settings take priority over these new workflow settings. HighLevel has not confirmed any limits, plan gating, or rollout status.

Where to find it

Navigate to Automations > Workflow Builder. Open an existing workflow or create a new one. Click on "Settings" for the workflow. You will find the new "Sender domain" dropdown under "Sender details."

How agencies will use this

An agency might manage a sub-account for a client who uses different branding or departments, each with its own verified sending domain, for various outreach efforts. For example, a client has sales.clientdomain.com for new lead outreach and support.clientdomain.com for customer service. The agency can build a workflow for new lead follow-ups. In the workflow settings, under "Sender details," they would select sales.clientdomain.com from the "Sender domain" dropdown and specify "info" as the prefix (resulting in info@sales.clientdomain.com). Any email actions in this specific workflow—whether it's an initial welcome email or a follow-up nurturing sequence—will now consistently send from info@sales.clientdomain.com. Simultaneously, a separate workflow for support ticket responses could be configured to send from support@support.clientdomain.com. This ensures consistent domain usage per communication type without manual overrides in each email action, as long as the email action itself does not explicitly override the sender details.

Our take

This is a solid quality-of-life update for agencies managing multiple dedicated sending domains within a single sub-account. It adds a layer of organization and consistency to email sending. It's not a major, groundbreaking shift in functionality, but it simplifies domain management for specific workflow types. For agencies with simpler email setups, this won't change much. HighLevel has not confirmed the significance reason for this being a major update, but the directness of the feature makes it a useful, if niche, addition.