Updated login email template — does automation use the new version?
Quick answer
After editing a template, verify that the active automation uses the updated email. Template edits may not automatically update every workflow step depending on how the campaign was cloned or attached.
Platform
Web
Area
Internal Operations
Related system
GHL
Symptoms
If any of these match, this article is for you.
- Login email template was updated with the exp:// / server-error warning.
- Team asks whether new users will get the updated email.
- Automations menu is hard to find.
- Existing buyers will not receive the updated email automatically.
Step-by-step solution
Internal workflow
- Open the active onboarding automation / workflow.
- Locate email 2/2 or the current login instruction email.
- Confirm the content includes the exp:// warning.
- Send a test email to an internal account.
- For existing buyers, send a separate update email with the new instructions.
If it still does not work
- Keep a recommended instruction line ready: “If you see ‘server error,’ check the search bar — exp:// may be missing. If so, add it to the beginning and press enter.”
- Track template versions in the support log.
Was this article helpful?
Still need help?
Send us a quick form. We'll prefill what we already know about this article.
Related articles
New user did not receive follow-up / login / verification email
Determine whether the user is a buyer, pre-register / contact, or questionnaire lead, then resend the appropriate instructions.
GHL campaign says there are no contacts or buyer list is missing
Internal email / audience setup issue, not a customer-facing app bug. Verify the campaign audience, smart list, and contact filters before sending.
Are new buyers added to the smart list automatically?
The intended workflow is that new buyers are added to the smart list automatically after the onboarding email workflow / contact automation completes.
Notion says “no users” while tracking support cases
Treat Notion “no users” as an internal tracking / tool issue. Do not let it block recording the case. Add the user email manually until the relation field works.