Automations

Hello everyone, I've been going through a lot of forums and blogs that always asks the same question which is "how to send automated dms to new IG followers" I just shared one found in the attachment

Currently, the notifications feature is not very convenient. While we do have a notification icon in the top-right corner, it does not fully solve the issue because reps may not realize when a new notification comes through. We'd like to request a pop-up notification that can be used in workflows as needed. It should allow a message to pop up on the user's current page when the workflow is triggered.

Just like when someone comments on a post, it would be nice to be able to send an automatic message to new followers on instagram and facebook

An automation that allows you to block out more time (say a whole day) on calendar b if a p[articular appointment is booked on calendar a

When building automations we have the option to test-send the emails and we can enter an email address to have the email sent to us to see what it looks like in our inbox. However every time we need to do this, it's a blank field by default so we have to re-enter our email address. 99% of the time it would be the email address of the person that is currently logged in to GoHighLevel. I think it'd be a great feature to just default this field to have the logged-in user's email address pre-populated in this field

When building automations we have the option to test-send the emails and we can enter an email address to have the email sent to us to see what it looks like in our inbox. However every time we need to do this, it's a blank field by default so we have to re-enter our email address. 99% of the time it would be the email address of the person that is currently logged in to GoHighLevel. I think it'd be a great feature to just default this field to have the logged-in user's email address pre-populated in this field

Please add optional HMAC signature validation directly inside the Inbound Webhook workflow trigger. The Problem: Many third-party platforms (payment processors, custom SaaS tools,etc) issue an HMAC key and send a signature header (e.g., X-Signature) to verify payload authenticity. Currently, HighLevel cannot validate header signatures on incoming webhooks. This forces users to route webhooks through middleware (Make, Zapier, or a custom server) just to verify the request before forwarding it to HighLevel. Proposed Solution: Add an optional HMAC Verification configuration block inside the Inbound Webhook trigger settings: Secret Key Field: Input for the shared secret/HMAC key. Header Name Field: Input to specify the signature header (e.g., X-Signature, X-Hub-Signature-256). Algorithm Selection: Dropdown to select the hashing algorithm (e.g., SHA-256, SHA-1). Behavior: Automatically reject or drop incoming requests if the computed signature does not match the header. Why This Matters: This would allow users to build secure, direct integrations with external tools without needing expensive third-party middleware or custom code servers.

The advanced filters in the list of workflows fall short for you have dozens of automations. We're asking for three improvements: 1) Filter by folder. Today you can only filter by state and by name, but not because of the folder in which each flow lives. Folders are the only real organization that we have and yet they are not good for searching. Que “Folder” is a filter field, allowing the full path (folder and subfolder) and multiple selection. So we could work by business area —Webinar, Recruitment, Sale, Onboarding— and save smart lists by folder. 2) Create a filter from a manual selection. When you check multiple boxes the action bar (Move, Manage Permissions, Delete) already appears in the list; it would be enough to add there an “Add to filter” that converts that selection into a savable smart list. It's the natural way to group flows that don't they share a folder or name, without having to reorganize the folders just for be able to filter them. 3) Make “Workflow Name” a selector with search and selection multiple, not a free text field with “Contains”. Today we have to write the memory name and get the exact string right; worse, to filter three specific flows, three conditions must be linked together. A drop-down that lists existing flows, are filtered as you type and allow you to mark several solves the most common case in one step. Real case: in an account with flows grouped by customer and by phase, for To review a single phase you have to remember the names from memory or open the folders one by one.

Currently, if one Ai agent transfers to another, you cannot activate flows, or use that transfer as a trigger in an automation.

Please add the ability to use a Custom Code action's Reference Output as a Dynamic Value in the Update Contact Field workflow action. My use case is very simple: I have a contact's Date of Birth stored in HighLevel. A Custom Code action calculates the person's current age and successfully returns an output such as age: 61. I then need the next Update Contact Field action to write that calculated value into my custom contact field called “Age.” Currently, the Update Contact Field value picker does not expose the Custom Code Reference Output, so there is no supported way to map the calculated age output into the Age contact field. Ideally, the workflow should allow: Date of Birth → Custom Code calculates current age → Reference Output “age” → Update Contact Field “Age” This would also be useful for many other workflows where Custom Code performs a calculation and the resulting value needs to be stored permanently on the contact record. HighLevel Support confirmed this limitation under Ticket #6010524.