See the top GoHighLevel agencies in the USA for 2026: 14 ranked
HighLevel automation notification setup: internal notifications
HighLevel automation notification setup comes down to one workflow action, Send Internal Notification. It alerts your own team by email, in-app bell notification, SMS or WhatsApp when the workflow's trigger fires. Recipients are always users in the account, never contacts. You can send to everyone, chosen users, the assigned user, a role or team, the opportunity owner or the record's followers.
Updated
Internal notification facts
| Fact | Detail | Source |
|---|---|---|
| Action name | Send Internal Notification (workflow action) | help.gohighlevel.com |
| Channels | Email, In-App Notification (bell icon), SMS, WhatsApp | help.gohighlevel.com |
| Who receives it | Team members only: all users, particular users, the assigned user, roles or teams, the opportunity owner | help.gohighlevel.com |
| Followers | Optional extra recipients: contact followers, opportunity followers or both | ideas.gohighlevel.com |
| Rate limit | Up to 500 notifications per user every 5 minutes by default; extra ones queue | help.gohighlevel.com |
| Duplicates | A user picked in several recipient fields gets one notification | help.gohighlevel.com |
| No assigned user | Email and SMS to "Assigned User" are skipped and the workflow carries on | help.gohighlevel.com |
| Billing note | Each CC or BCC address adds to email usage and billing | help.gohighlevel.com |
| Help article updated | March 31, 2026 | help.gohighlevel.com |
How to set up an internal notification
- Open Automation in the left menu and click + Create Workflow, or open an existing workflow.
- Add a trigger, for example a form submission, a new appointment or a stage change.
- Click + under the trigger and choose Send Internal Notification.
- Name the action (for example "New lead: email the sales team").
- Pick the Type of Notification: Email, In-App Notification, SMS or WhatsApp.
- Set To User Type and, if needed, switch on contact followers or opportunity followers.
- Write the message. The tag icon inserts custom values such as the contact's name and phone.
- Save, then publish the workflow.
What each channel offers
| Type | Fields | Good for |
|---|---|---|
| From name and email, recipients, CC/BCC, subject, templates, message with Write with AI, attachments | Full lead details someone can forward | |
| In-App Notification | Title, message, Redirect Page, recipients | Alerts that open the contact or opportunity in one click |
| SMS | Recipients, templates, message, attachments or file URLs, test number | Alerts someone sees within seconds |
| Recipients, an approved WhatsApp template, message | Teams that already work in WhatsApp |
Each channel needs its setup in place first: a phone number for SMS, a sending email for email, the WhatsApp integration for WhatsApp. When a channel isn't ready for a recipient, that send fails and the rest of the workflow still runs.
Recent changes
HighLevel has extended the action several times. The changelog entries are undated, so they are listed without dates:
- Several users in one action for email and SMS.
- CC and BCC on internal emails, which had been available only in the regular email action.
- WhatsApp as a notification type.
- Followers and Opportunity Owner as recipients on all four channels, with duplicates removed. Existing actions were left unchanged.
Newer workflow changes, such as the Router and Loop actions released in October 2026, are in the GoHighLevel updates for October 2026.
User notification settings
Separate from workflows, each user chooses which system alerts they get under My Profile > Notifications, with in-app, email and SMS switches per category. HighLevel's calendar article shows email and in-app on by default and SMS off. Client portal notifications are another system again, set by the contact in their portal profile.
Internal alerts often follow a form on a funnel, including the GoHighLevel video gate form, or a lead from an integration such as Google Sheets. Teams that want alerts as iMessages rather than SMS can look at iMessage providers for HighLevel. Teams that work from their phones can read about the GoHighLevel mobile app. To have notification workflows set up for you, compare GoHighLevel CRM and automation agencies.
Frequently asked questions
Can a GoHighLevel internal notification go to a client or lead?
No. HighLevel says internal notifications are for team members inside the account only. Messages to contacts use the regular Send Email or Send SMS actions.
Why didn't the assigned user get the notification?
If the contact has no assigned user, or the user has no valid phone for SMS, HighLevel skips the step. HighLevel's help article also suggests checking whether the user's profile is marked DND (toggle it off and on, then test), and the limit is 500 notifications per user every 5 minutes.
Can one notification go to several people?
Yes. One action can go to all users, several particular users, a role or team, the opportunity owner and the contact or opportunity followers. Email notifications also take CC and BCC addresses.
Can the alert open the lead's record?
In-app notifications have a Redirect Page setting, so clicking the bell alert can open the contact or the opportunity.
Do internal notifications reach the mobile app?
HighLevel's help article for the action does not mention mobile push, and users on HighLevel's ideas board report mixed results. Email and SMS reach a phone without relying on app push.
Sources
All checked November 6, 2026.
- HighLevel help: Workflow Action – Internal Notification (last modified March 31, 2026)
- HighLevel changelog: followers and opportunity owners, WhatsApp support, CC/BCC, multiple users
- HighLevel help: calendar integration disconnection notifications (My Profile notification settings, April 22, 2025)
- HighLevel help: notifications inside the client portal