A
Alfredo Grossi
The new Events feature has a lot of potential, but in its current state there are two major limitations that make it very difficult to use for real-world event management.
  1. There is no “Invite to Event” workflow trigger or event context before registration
Right now, Events only becomes truly useful after someone has already registered.
There is no workflow trigger such as:
* Contact Invited to Event
* Contact Added to Event Invite List
* Send Event Invitation
* Event Invitation Created
Because of this, there is no event context available when sending the initial invitation.
This creates a major problem: we cannot send a mass invitation by WhatsApp or email using Event variables such as:
* Event Name
* Event Date
* Event Start Time
* Event Location
* Event URL
* Event Host
* Event Schedule
For example, we should be able to create one WhatsApp template like:
“Hi {{contact.first_name}}, you are invited to {{event.name}} on {{event.date}} at {{event.start_time}} at {{event.location}}.”
But today, if the workflow is triggered by a tag, contact import, smart list, custom field, etc., HighLevel does not know which Event the contact belongs to, so the Event variables cannot be populated.
This forces users to duplicate Event information into Contact Custom Fields or create separate workflows for every single event, which defeats the purpose of having an Events module.
What is needed:
* A native “Invite Contact to Event” action
* A native “Contact Invited to Event” trigger
* The ability to associate a contact with an Event before registration
* Event merge fields available in WhatsApp, SMS and email invitation messages
* Event-specific workflow context before RSVP
* The ability to send bulk invitations to a selected contact list for a specific Event
The ideal flow should be:
Select Event → Select Contacts → Invite Contacts → Trigger Workflow → Send personalized WhatsApp/Email using Event variables → Contact RSVPs → Continue with Event Registration workflows.
This would make Events dramatically more useful for weddings, conferences, private events, corporate events, webinars and RSVP-based events.
  1. The Event Page is far too limited in customization
The second major issue is the public Event Page.
At the moment, many important system labels cannot be properly customized, including elements such as:
* “About this event”
* “Schedule”
* “Hosted by”
* “Share”
* “Free”
* “RSVP”
For premium or branded events, this makes the page feel like a generic ticketing platform instead of a custom event experience.
There should be full control over:
* All labels and text
* Button text
* Section titles
* Language
* Layout
* Sections shown/hidden
* Fonts
* Colors
* Spacing
* Ticket terminology
* RSVP terminology
* Host terminology
Language customization is especially important.
If I am creating an event in Spanish, Portuguese, French, German, etc., I should not be forced to show English system labels on the public page.
At minimum, Events should support automatic localization based on the sub-account language.
Ideally, every label should also be manually editable.
Why this matters
The Events module currently has excellent functionality for registrations, schedules, workflows and check-in, but the experience before registration is incomplete.
The two missing pieces are:
  1. A proper Event Invitation workflow/context.
  2. A fully customizable and localized Event Page.
Without these, Events works well as a registration engine, but not as a complete event management and communication platform.
Fixing these two areas would make Events significantly more powerful and would allow agencies to build complete vertical solutions for weddings, hospitality, conferences, corporate events and private events directly inside HighLevel.