- Published
- Byline
- GoHighLevel Partners Editorial
- Filed under
- GoHighLevel Automation
As of August 28, 2026, GoHighLevel workflows can pick their own verified sending domain instead of quietly inheriting whatever the sub-account defaults to. If you run more than one dedicated domain — which most agencies juggling several client brands or a mix of transactional and promotional email eventually do — this is the setting that decides which domain’s reputation absorbs the blast radius when one campaign gets flagged as spam.
Here is what shipped, where to find it, and the three places a workflow’s actual sending domain can quietly get overridden without anyone noticing until deliverability drops.
What Shipped on August 28, 2026
HighLevel added a Sender domain dropdown to Workflow Settings, under Sender details. Pick a verified dedicated domain there and every Send Email action inside that workflow sends from it by default. Previously, domain selection lived only inside Email Campaigns and on a per-action basis inside individual workflow steps — there was no single place to lock an entire workflow to one domain.
This is not the same feature as dedicated sending domains themselves, which have existed for a while and are a separate setup step (covered below). The new dropdown is a selector that sits on top of domains you have already verified — it does nothing on a sub-account with no dedicated domain configured.
Where to Find It
- Open the workflow in Workflow Builder.
- Click Settings (the tab next to the canvas, not the action editor).
- Scroll to Sender details.
- If the sub-account has at least one verified dedicated domain, a Sender domain dropdown appears.
If that dropdown does not appear, the sub-account has zero dedicated domains verified — see the setup section below. There is no error message explaining the absence; it simply does not render.
All Domains vs a Specific Domain
The dropdown offers a choice between one named domain and an “All domains” option, and the two behave differently:
| Option | What you enter | How sending works |
|---|---|---|
| A specific domain | Sender name plus an email prefix (e.g. “marketing”) | Every email sends as prefix@thatdomain.com, no rotation |
| All domains | Sender name and email prefix only, no domain picker | HighLevel rotates across every verified, warmed domain on the sub-account using its internal weighted-distribution rules |
“All domains” is the closer behavior to how Email Campaigns already worked before this update. Picking one specific domain is the new capability: it lets you deliberately pin a workflow — say, a payment-failure dunning sequence — to one domain and keep it off the domain your promotional campaigns use.
The Override Hierarchy — Where Agencies Get Surprised
The workflow-level domain is a default, not a lock. Three layers decide the final sending domain for any individual email, and each layer beats the one below it:
| Priority | Setting | Behavior |
|---|---|---|
| 1 (highest) | Dedicated email header settings | Custom headers configured under Settings > Email Services override everything below, including the workflow’s chosen domain |
| 2 | An individual Send Email action’s own Sender details | If someone filled in a From Email on the action itself, that wins over the workflow-level dropdown |
| 3 (lowest) | The workflow-level Sender domain dropdown | Applies only when no action-level override and no header override exist |
The practical trap: a workflow built months ago, before this feature existed, may already have hardcoded sender details on individual actions. Setting the new workflow-level domain today does not touch those actions — they keep using whatever was typed into them originally, and the workflow-level setting silently applies only to the actions that were left blank. Audit each Send Email action’s own sender fields before assuming the workflow-level dropdown is now controlling all outbound mail from that workflow.
The Sender Domain Mismatch Warning
If the From Email entered anywhere in the chain uses a different domain than the one selected — for example the workflow is set to send from updates.agency.com but an action’s From Email is typed as hello@clientbrand.com — HighLevel shows a sender domain mismatch warning. It is a warning, not a hard block: the email still sends. Treat it as a signal to check, not as validation that the address is correct. A mismatched domain can still pass DKIM/SPF checks for whichever domain actually authenticated the message while damaging the reputation of the domain the sender name implies, which is exactly the ambiguity the warning exists to flag.
Why This Matters More for Agencies Than Single Brands
A single-brand sub-account sending everything from one domain gets little practical benefit from this feature beyond tidiness. An agency is different in one specific way: multiple dedicated domains on one sub-account, each doing a different job, is a common setup precisely to isolate reputation. Before this update, that isolation was enforced per email action or per campaign, which meant a workflow with a dozen Send Email actions needed the correct domain re-entered a dozen times, and a single missed field silently fell back to a shared default.
Now the workflow itself carries the default, and the audit surface shrinks to one dropdown per workflow instead of one field per action — as long as you remember that any action with its own sender details already set is exempt from that default, per the override table above.
Setting Up a Dedicated Domain First
The workflow-level dropdown does nothing until at least one dedicated domain exists on the sub-account. If yours is not set up yet:
- Go to Settings > Email Services > Dedicated Domain and IP.
- Click Add Domain and enter a subdomain, such as emails.yourbrand.com — a subdomain, not the root domain, is the standard pattern so it does not share reputation with your website or main inbox.
- Add the DNS records HighLevel generates, either through an automatic connection or manually at your DNS host. Propagation can take up to 24 hours.
- HighLevel does not support multiple DKIM records for the same domain — if a DKIM record already exists there from another provider, remove or replace it rather than adding a second one.
- Warm up a brand-new domain before pointing large lists or high-volume workflows at it. A domain with no sending history and a sudden spike in volume is the fastest way to land in spam folders regardless of how correctly the workflow setting is configured.
A sub-account can hold multiple dedicated domains and assign them across different sending contexts — one-to-one conversations, workflows, campaigns, invoices — independently. The new dropdown is what finally lets the workflow context be set once at the workflow level instead of the previous per-action-only control.
What HighLevel’s Own Documentation Does Not Confirm
HighLevel’s changelog entry and its Send Email workflow action article do not state whether this dropdown applies to SMTP-connected email sending (where a sub-account routes through an external mail provider instead of HighLevel’s native LC Email infrastructure) or only to LC Email. If your sub-account uses SMTP for workflow emails, verify in your own account whether the Sender domain dropdown appears at all before assuming it governs your sending.
Frequently Asked Questions
Do I need a dedicated domain for this dropdown to show up?
Yes. With zero verified dedicated domains on the sub-account, the Sender domain field does not appear in Workflow Settings at all — there is nothing to select.
Does setting the workflow-level domain override every email action inside it?
No. An individual Send Email action’s own Sender details, if already filled in, take priority over the workflow-level dropdown. Dedicated email header settings override both. Check each action, not just the workflow settings, if you are auditing which domain actually sent a given email.
What happens if I choose “All domains” instead of one specific domain?
HighLevel rotates sending across every verified, warmed dedicated domain on the sub-account using its internal weighted-distribution rules, the same rotation behavior Email Campaigns already used before this update.
Is the sender domain mismatch warning a hard block?
No. It is a warning, and the email still sends. Use it as a prompt to double-check the From Email against the selected domain, not as confirmation that the setup is already correct.
Can I set a different domain for transactional versus promotional workflows on the same sub-account?
Yes, that is the core use case this update enables — pick a specific domain per workflow rather than relying on one shared default, which lets you keep a payment or booking confirmation workflow off the domain your marketing campaigns use.
We build your GoHighLevel account for you
CRM, pipelines, funnels, SMS and automation — configured for your business, not left for you to figure out.
- Setup (one-time)$850
- Ongoing (per month)$38.80
No obligation quote · reply within 1 business day
This site is independently operated and is not officially affiliated with, endorsed by, or sponsored by HighLevel LLC. We do not receive referral commissions — this is our own flat-fee implementation service.