Automations

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.

## The Ask Expose workflow execution logs, audit logs, and workflow error events through the public REST API (PIT-authenticated). Currently these are UI-only — no programmatic access exists. ### Specific endpoints requested: GET /workflows/{workflowId}/executions — List execution history with filters (status: active/completed/failed, contactId, dateRange, pagination) GET /audit/search — Query audit log entries by module, action type, date range, and user Webhook event: workflow.action.failed — Real-time webhook trigger when any workflow action fails, including: workflow name/ID, action step name, contact ID, error message, timestamp ## Why This Matters Agency operators managing multiple sub-accounts have no way to programmatically monitor workflow health. We are forced to manually click into each workflow, check the Execution Logs tab, and visually scan for red error highlights. That does not scale. Here is what we would build with API access: Automated error alerting — A script that checks for failed workflow actions across all sub-accounts every hour and sends a Slack/SMS alert: "Workflow Contact Us Form failed on step Send Welcome Email for contact John Smith at 2:15 PM. Error: invalid email address." Cross-workflow health dashboards — Aggregate execution stats (success rate, failure rate, avg completion time) across all workflows in a location. Right now you can only see one workflow at a time in the UI. Audit trail integrations — Pipe audit log data into external compliance/logging systems (Datadog, Supabase, custom dashboards). The 60-day retention limit in the UI means audit data is permanently lost after 2 months — API access would let agencies archive it. Proactive CRM monitoring — Detect when a workflow silently fails (e.g., a welcome email never sent, a tag never applied) before the customer notices. Right now errors go undetected unless someone happens to check. ## Current Workarounds (and why they fall short) Email error notifications — GHL sends error emails, but they are unstructured prose. Parsing emails for monitoring is fragile and slow. Adding webhook steps to every error branch — Works but requires manually editing every workflow step. For an account with 20+ workflows and 100+ action steps, this is days of work and creates maintenance overhead. ## The Opportunity Unlock a new category of monitoring/observability marketplace apps Differentiate HighLevel for agencies managing 10+ sub-accounts at scale Reduce support tickets from "my workflow broke and I did not know for 3 days" Enable the same programmatic access pattern that already exists for contacts, conversations, and pipelines Let agencies archive audit data beyond the 60-day UI retention window ## Related Requests "In Depth Audit Logs" (ideas board — Reporting category) "Audit Logs — Custom Fields" (ideas board — CRM category) This would be a game-changer for any agency running automations at scale.

The Merge Field selection button sits over the top of the text field. This obstructs the view of what you are typing. I often have to copy and past the text from somewhere else, just to be certain it is spelt correctly. Screenshot provided is specifically from the Update Opportunity Action, however occurs elsewhere also.

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

The new way email templates are being handled is taking some time to get used to. However, there appears to be a bug that is absolutely critical to fix: YOU CAN'T UPDATE PREVIEW TEXT IN WORKFLOWS! So, once an email in Workflows gets the "with edits" tag, and you want to update the Preview Text, you're screwed.

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.

I needed a condition that compared a date to the current date. If it was before today, go one path, else go the other. So I put in if that date field is before rightnow.date ... Ran a test with a client who I knew was before today, and it came FALSE. So I had to add a date field and an additional step to set that field to rightnow.date Then change my condition to reference that field instead of { rightnow.date }. And it worked. That's a bug. You can see in the attached execution logs, it's likely a formatting issue. When it sees 03/04/2026, 2026-01-09 registers as FALSE (not before) But when it sees March 4, 2026, 2026-01-09 registers as TRUE (the desired result) The IF/ELSE should recognize the 03/04/2026 format.

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.

Even when a contact is removed from a workflow whilst in a booking bot or conversational ai action, despite saying the contact is no longer in the workflow the ai will still be engaged, this needs to be fixed asap!

Currently we can't update opportunity fields dynamically using multiple choice custom fields with "update opportunity" action. I only saw that option possible with "update contact field" action.