Automations

In the Calendars tab, users can open an appointment and manually change its status to Unconfirmed. However, when building Workflows/Automations, every appointment status is available as a trigger or condition except Unconfirmed. This inconsistency doesn't make sense. If the status exists in the calendar UI, it should also be available within automations. Having access to the Unconfirmed status would allow teams to automatically send reminders, follow-up SMS, emails, or internal notifications without requiring agents to manually manage these appointments. This would save time, improve workflow automation, and create consistency between the Calendar module and Workflows. Please add Unconfirmed as an available automation trigger and condition. 🚀

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.

Unfortunately - for whatever reason - there is no workflow trigger “Contact changed” standard fields first name, last name, company - these are missing!!! This is absolutely incomprehensible and is urgently needed.

Using the trigger Respond on a Comment/ Reply in Comments, there is a 150 character limit to the reply text box. This is not indicated at the text box entry. If the character limit is exceeded the response/ reply won't send. The only place an error is indicated is in the execution logs. I have spend days and 3 tech support calls to get this figured out. A simple character limit display would eliminate this problem. There are other text boxes in GHL that have limits without any indication. This has happened to me once before with a different text box. There was no indication of the character limit. No error indicated. Tech support did not catch that error for a few days either. Again, a simple character counter would solve this. I believe this is an industry standard with text boxes containing character limits. Thank you

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

Currently using a conversion event in Google Ads with "external attribution" does not work and causes an error. Google Ads has ruined their marketing attribution by removing "first click" as an option. Savvy Google Ads marketers would love to see GHL be able to send a value of just "1" back with the gclid to show a lead was "1" conversion. Otherwise using Google's mixed attribution models turns these into 0.75, 0.66, etc. I feel like this could be pretty simple to fix on the GHL side.

This is absolutely essential for any long term use of the custom webhook action in GHL workflows. I don't build new workflows in GHL because of this missing feature. If for example i have 10 workflows that use this custom webhook action I will most likely have 30+ different custom webhook actions across all of them. The purpose of saving secret keys to GHL is to be able to reuse them easily, keep them private and secure, and to easily update them all at once if a key/token needs to be rotated or expires. In it's current state, when I rotate API keys i have to go into every single workflow and make sure I manually find every single action that uses the old key and update each one hoping that I don't miss any. Today the only management of these keys is the ability to add a new key or delete an old key. I replaced GHL workflows with a different software that allows me to do this and I build all of my workflows there. If for example the other software (n8n) behaved the same way as GHL does with key management, every time that I rotated a key (expired, key compromised, enforced key rotation policy, etc.) I would have to go in and manually update 73 different workflow actions one by one. This key rotation process would only get worse with every additional workflow that I build. GHL UI workflows are not useable or sustainable for large scale growth and integration with APIs and custom webhooks in their current state

When a "Send SMS" action fails, the event status is still showing as successful - even though we can see in the exact same panel via the "SMS Statistics" that the message failed to send. The event status should be showing as failed if the SMS didn't send.