Automations

User (Team Member) Replied Trigger Needed
Right now in GHL there is a trigger called "Customer Replied." It fires when a customer sends us a message. That part works great. But there is no trigger for when a user (a team member, a staff member, an agent) replies back to the customer. This is a huge problem. Here is the problem in simple words: A customer messages us. We are supposed to message them back. Sometimes our team does. Sometimes our AI does. Sometimes nobody does — and we don't find out until the customer gets angry and leaves. We have no way to know if a user replied or not. GHL does not tell us. What we want to build (but can't): Customer sends us a message Wait 5 minutes Check: did a user reply? If YES → great, do nothing If NO → send an alert to the owner: "Hey, nobody replied to this customer!" Step 3 is impossible right now. There is no "User Replied" trigger. What we need GHL to build: A simple new trigger called "User Replied" that fires when any team member sends a message to a contact. With filters for: Which user replied Which channel (SMS, email, WhatsApp, Instagram, Facebook, Live Chat) Which assigned user it was meant for Also please add "User Reply" as an option on the Wait action, the same way we already have "Contact Reply." Why this matters: AI agents are everywhere now. When the AI misses a message, we have no way to catch it. Sales teams need SLA tracking — "did my rep reply in 5 minutes?" is impossible to answer today. Drip sequences keep firing even after a human has already replied, which makes customers angry. Shared inboxes need this to know who is handling what. This idea has had hundreds of votes for two years. Please build it. It is the single biggest missing piece for anyone running AI or team-based customer conversations on HighLevel. Thank you.
93
·
New Feature
Workflow Dashboard, Workflow Export, and MCP Visibility
I would love to see a better way to view, audit, and manage workflows inside GHL without having to open each automation one by one. Right now, if you have a lot of workflows, it is very hard to quickly understand what is happening across the account. It would be incredibly helpful to have a dashboard view where we can see: * all workflows in one place * which workflows are live vs. inactive * the trigger for each workflow * the actions/steps inside each workflow * which workflows contain certain steps, tags, emails, conditions, or actions * when each workflow was last updated * whether a workflow is connected to a form, funnel, calendar, campaign, or product Ideally, we could filter workflows by status, trigger type, action type, tag, email, form, funnel, or other workflow components. This would make it so much easier to audit accounts, clean up old automations, troubleshoot issues, and understand the customer journey without clicking into every single workflow manually. I would also love for the Claude/Codex MCP connection to be able to see all workflow automations and the steps inside them. If MCP could view workflow structure, AI could help us: * optimize our systems * troubleshoot broken automations * identify duplicate or outdated workflows * find missing steps * document what each workflow does * spot risky automations before they cause problems * simplify complicated customer journeys Right now, we are manually updating a Google Sheet with each workflow, the trigger, and every step inside the automation. On a platform as powerful and high-tech as GHL, this feels like something we should not have to do manually. If a full workflow dashboard or MCP workflow visibility is not possible yet, could we at least get a workflow export feature? A simple CSV export showing all workflows, whether each one is live or inactive, the trigger, and the actions inside each automation would be incredibly valuable. This would save users so much time, make accounts easier to manage, and help teams use GHL more strategically. Please consider adding this. It would be a huge quality-of-life improvement for anyone managing complex GHL accounts.
0
·
New Feature
New Automation Action: Add “Internal Comment” to Conversations
[The Problem] When a contact calls in or messages us, the fastest way for our team to get context is to quickly scan that contact’s Conversation thread. However, a lot of important information currently lives outside the conversation (forms, custom fields, notes, appointment outcomes, etc.). Right now there is no way to automatically add an Internal Comment via automations/workflows. That means: • Team members must manually add internal comments after calls or appointments • Critical notes sometimes end up buried in other sections (custom fields, notes, opportunities, etc.) instead of right where the team is already looking: the Conversation • Speed and consistency suffer, especially in busy inbound call/message environments ⸻ [Requested Feature] Add a new Automation / Workflow action: “Add Internal Comment to Conversation” Basic behavior: • Select the contact’s Conversation • Post an Internal Comment (not visible to the contact) • Allow use of Custom Values / Form Fields / Appointment data / Custom Fields to merge into the comment text • Optionally allow choosing a “From” user (or default to the system/assigned user) ⸻ [My Main Use Case] (example): We run virtual consultations and use an Appointment Outcome Form to record key notes: concerns, goals, objections, recommendations, next steps, etc. Ideal flow: 1. Contact completes a virtual consultation 2. Staff fills out the Appointment Outcome Form 3. Automation triggers on form submission or appointment status change 4. Automation action creates an Internal Comment in that contact’s Conversation, pulling in the form data (e.g. “Consult Summary: [form answers…]”) Now, if that person calls or texts back later, our team can simply open the Conversation and instantly see the latest internal notes without hunting through other tabs or records. ⸻ [Other Powerful Use Cases for the Community]: • Logging important workflow decisions directly into the Conversation (e.g. “Lead moved from Nurture → Hot; requested pricing details.”) • Summarizing long form submissions or surveys into a short internal comment • Capturing key events from other systems via webhooks → workflows → internal comments • Creating quick “handoff” notes between team members when ownership changes ⸻ [Why This Matters] • Speed: Frontline staff can get up to speed in seconds by scanning the Conversation. • Consistency: Automations ensure that important notes are always added, not forgotten. • Clarity: Conversations become the single source of truth for all recent context, instead of scattered across multiple sections. • Team collaboration: Internal-only comments are perfect for coordination without cluttering external communication. ⸻ If you also rely on Internal Comments and want automations to be able to create them, please UP-VOTE this idea so GoHighLevel can prioritize it. Having “Add Internal Comment to Conversation” as a standard workflow action would be a simple but high-impact upgrade for anyone doing consultations, sales calls, or any workflow where fast context matters.
3
·
New Feature
Add “Create from cURL” for Custom Webhook Premium Actions
Please add the ability to create a Custom Webhook Premium Action in HighLevel Automations by pasting in a cURL command. The goal is simple: let users paste a full cURL request, and have HighLevel automatically parse and structure the webhook action for them. This should automatically map: URL HTTP method Headers Authorization Query parameters Request body / payload Why this matters: Many of us now use AI to generate cURL requests for API calls. Instead of manually rebuilding those requests field by field inside HighLevel, we should be able to paste the cURL directly into the Custom Webhook action and let HighLevel structure it automatically. Desired workflow: Add a button inside Custom Webhook Premium Action called “Import from cURL” User pastes a cURL command HighLevel parses the request The webhook action is automatically populated with the correct fields User reviews, edits if needed, and saves Benefits: Faster setup for webhook-based automations Fewer manual configuration errors Better support for AI-assisted workflow building Easier API integrations for both technical and non-technical users More value from the existing Custom Webhook Premium Action Use case: We want to be able to ask AI to write the cURL, paste it into HighLevel, and have HighLevel automatically build the custom webhook action correctly inside the automation. This would make HighLevel much more powerful for advanced integrations and significantly reduce setup friction.
0
·
New Feature
Load More