Automations

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
Feature Request: Allow Workflows to Create Community Posts
It would be extremely useful to have a “Create Community Post” action inside GHL Workflows. Right now, workflows are incredibly powerful for automating actions based on triggers, webhooks, RSS feeds, AI processing, etc. However, there isn't a native way to take that processed content and automatically publish it as a Community post. The use case: RSS Feed → Webhook → AI → GHL Workflow → Community Post For example: An RSS feed detects a new article. The content is sent into a webhook/workflow. AI processes the article and turns it into an engaging community post. The workflow automatically publishes that content to a selected GHL Community. Optionally, the workflow could also attach an image, link, or CTA. What I'd love to see: → Create Community Post With fields such as: Community Post title Post content Image/media Link Post type/category Author Publish immediately vs. scheduled AI-generated content support Even better would be the ability to use custom values and workflow variables in each field, allowing content to dynamically come from: Webhooks RSS feeds AI actions Custom fields Previous workflow steps External APIs Why this would be powerful: This would turn GHL Communities into a much more powerful automated content distribution platform. For example: RSS → AI summarizes article → AI creates community post → Workflow publishes → Members engage Or: Webhook → AI generates educational content → Create Community Post → Notify members This would also create a lot of opportunities for agencies and SaaS users who are already using GHL's workflows and AI capabilities. In short: please add the ability to create and publish Community posts directly from Workflows. This feels like a natural extension of the existing automation system and would make GHL Communities significantly more useful for automated content delivery.
0
·
New Feature
Load More