Automations

For Fb & IG workflows don't have a filter option for "Story Mentions" On Instagram, when somoeone mensiones someone else in a story, Instagram automatically adds that as a DM message as well as an Instagram notification. this messes up out GHL workflows if anyone is using an "Auto Reply" Workflow. What happens is every time someone on IG mentions the IG account that's connected to GHL, the GHL auto reply workflow triggers and sends a message like: "We'll be with you shortly. Is there anything else you'd like to add to the message? {{ custom_ values.business _short_name }" GHL will send this message on every story mention and there is not way to stop it besides completely turning off the auto reply workflow. If the workflow is running like this the business looks really unprofessional and looks like they don't know how to run their computer systems in front of their IG followers.

Changing the primary color to an invalid color selection, e.g., pasting a HEX value, causes the color picker to disappear, resulting in no longer being able to pick a new color. I pasted FA560FFF into the color picker field. The color picker box is gone now and #FA560FFF is displayed but not editable. Deleting and recreating the calendar appears to be the only way to fix it.

There is enough room in the UI to have a dedicated button for Creating a New Workflow from scratch. Two clicks to do this still seems to slow for what I'm guessing is the primary use case. Can we please have a Quick Create From Scratch Button that is one button click away?

If you have a custom field that is of type checkbox, the intent was to allow the selection of more than one item. When using an automation to select one more item, all existing selected items will be removed. There is not a great way right now to evaluate which existing items are present so that you can re-select them in the automation either. I propose that when selecting a checkbox item with automations, the existing selections should remain. For example: Pick ALL the colors you like: [X] Red [X] Green [ ] Blue If the automation adds Blue, it will remove Red and Green unless you re-select Red and Green at the same time.

Currently, the "Inbound Call - Call Direction - Incoming" workflow trigger activates only after the call is disconnected. While this functionality has its use cases, it limits the ability to take real-time action during the call itself. Adjusting the trigger to activate at the start of the call, rather than at its conclusion, would provide significant benefits. This enhancement would allow agencies to perform critical actions such as populating data, tagging interactions, or sending API requests as soon as the call begins. These actions are essential for improving operational efficiency and customer experience. For example, triggering workflows at the start of the call enables agents to have immediate access to relevant customer information, making interactions more personalized and efficient. Additionally, early tagging and API integration can streamline downstream processes, automate data flows, and reduce manual intervention. By shifting the trigger point to the beginning of the call, agencies can maximize their responsiveness, improve service quality, and unlock greater flexibility in handling inbound calls.

The Workflow AI struggles to use provided email and SMS copy when generating campaigns. For example, if I paste a full multi-email and SMS campaign from the larger Ask AI/GHL function, it follows the structure but rewrites the copy instead of using what I provided, and is physically unable to edit the copy itself despite repeated prompting It would be extremely helpful if Workflow AI could preserve and insert the exact email and SMS copy given to it, allowing true one-click full campaign generation instead of requiring users to manually copy, paste, and build each workflow step.

Improve the AI Workflow Builder So It Can Create Complete Automations I really love the idea of the AI workflow builder, and I hope the GHL team continues developing it. The concept is excellent. Being able to describe the automation you want and have AI build it for you could be one of the most valuable features in the platform. But right now, it does not feel usable enough for real workflow creation. In my experience, the AI builder only partly completes workflows, misses important steps, and still requires us to go through and manually build or fix most of the automation afterward. That makes it hard to rely on. If the feature is going to stay in the platform, I would love to see it developed further so it can actually create complete, functional workflows from start to finish. For example, it should be able to: * understand the full goal of the automation * ask clarifying questions when needed * create the correct trigger * add all required steps * set conditions and if/else logic correctly * connect tags, emails, forms, calendars, opportunities, and pipelines * explain what it built * show a summary before publishing * warn us about missing pieces or possible issues * allow us to test the workflow before turning it on Right now, it feels like the feature has a lot of potential, but it needs more development before it can truly save users time. I would honestly rather see it pulled back temporarily or clearly labeled as experimental than presented as something that can reliably build automations when users still have to manually complete so much of the work. This could be a really powerful feature for GHL. It just needs to be able to build complete workflows that users can trust, review, and activate with confidence.

Please update the call reporting to accurately mark answered/missed IVR calls in the call reporting and conversations tab. We can't tell our clients that they will have call reporting and then have it show that every call was answered. The system already knows that the IVR call was answered or missed in the automation, but every single call is included as "completed" in the reporting AND the conversation. This needs to be addressed ASAP.

The Date/Time Formatter action does not provide an exact timestamp. The X (Unix in seconds) time formatting end up rounding to the nearest minute, making timestamps generated this way useless, as they are not unique. The result is even worse on the x (Unix in Milliseconds), where it not only does not include any millisecond data(just 3 more 0's/decimal places), it will even round to the minute. My current workaround is to use a Custom Code action: "const timestamp = Date.now (); output = { now: timestamp};" This provides an accurate Unix timestamp, but we should not have to use a premium action due to a bug in a standard action. It appears as if the Date/Time Formatter action is batching or rounding it's timestamp lookups. Here is a Loom of the situation: https://www.loom.com/share/680fc97d875842c3aa8c3382b64a0cbb

Expectation: when an appointment is booked, {{appointment.start_time}} (and other similar time-related fields) for use in workflows includes the time zone so it is clear to the client when their appointment is when they receive confirmation emails and reminder/emails and texts generated through workflows, regardless of where they happen to be physically (in the time zone where they booked the appointment, in a different time zone than where they booked the appointment (i.e., the time zone of the business), etc.). Problem: Because GHL autodetects time zone of the client when they are booking an appointment, it is causing confusion. This autodetection is using the assumption that the client will attend the appointment in the time zone in which they booked the appointment. It is not taking into account appointments that are for the physical location of the business that were booked in a different time zone. This issue has already caused problems/confusion with appointments several times. Example: Client booked an appointment with the business (which is on Central time) while they were in the Mountain time zone. They then returned to the Central time zone when the appointment was to occur, but all of the reminders that were being sent from the workflow were for Mountain time without specifying the time zone. The client appointment was supposed to be at 2:45 pm Central, but everything they were being sent said that it was 1:45 pm Central, which thus lead to confusion. If this is not fixed: this problem causes loss of revenue, confusion, and business reputation problems. This is unacceptable. Also, I realize that there are a couple of other tickets that touch on this, but the acceptance criteria is less direct.