Automations

When manually adding a contact into a workflow we should be able to choose any step in that workflow. For example you may want to skip the first few emails and just drop them into the appropriate email for that account. Reduces clutter and enhances user experience by putting them exactly where they need to be in the flow.

Custom Objects in Workflows We do not have custom objects if we need to add them as trigger or an action in the workflow list, kindly add them to triggers as well as actions so we can create automations and actions based on the custom objects in CRM

Can we make it so we can automatically add a pdf version of a form/survey that is submitted to an email/sms workflow?

Hello GHL Team, I’d like to suggest adding a new feature that would significantly expand the flexibility of Workflow automations. Currently, GoHighLevel doesn’t provide a native variable such as {{current_month}} or a direct workflow condition like “Month equals [X]” that allows automations to trigger or branch logic based on the current month. This functionality would be extremely useful for: Scheduling monthly recurring campaigns without relying on external tools or manual date fields. Automating seasonal emails (e.g., “Send this campaign every October”). Running month-based logic within a single workflow instead of creating 12 separate automations. Suggested Implementation: Introduce a dynamic variable like {{current_month}} or {{current_date.month}} accessible in workflows, emails, and conditions. Add workflow filters such as “Current month is equal to [January–December]” or “Wait until current month equals [X]”. This would make workflows far more intelligent and self-sustaining for marketing and client engagement automations. Thank you for considering this enhancement!

Sometimes workflows are used to send messages. When a person is in an active conversation and sends another message, the system tries to enter them into the workflow again. However, since they’re already inside, they can’t re-enter — but ideally, they should be placed in a queue to join the workflow again once their current process finishes. This improvement would save thousands of users a huge headache. Please consider adding this feature!

Would be nice - Sometimes I want to copy like 20 automations, but don't want to copy a whole snapshot

We should have the option to bulk delete workflows vs having to do it 1 x 1. I don't know how but I have over 16 pages of duplicated workflows and having to delete them one at a time is taking forever. Its extremely frustrating we can't just bulk select the workflows we want to delete and do it all at one time.

Give the ability to clone the workflow folders versus having to do each workflow individually.

Setting up Premium Custom Webhook Actions requires manually writing JSON schemas, which is complicated and time-consuming. Most users don't know how to write proper JSON schema syntax, leading to errors, frustration, and abandoned webhook setups. Use Case: We want to connect GHL to external tools (like Zapier, Make.com , custom APIs) using Premium Custom Webhook Actions. To do this, we need to: Define what data fields the webhook should send Write a JSON schema that describes those fields Test and debug the schema until it works Most people aren't developers and don't know JSON schema format. Even technical users spend a lot of time looking up syntax and fixing errors. Current Limitation: Users must manually write the entire JSON schema from scratch. There's no helper, template, or guidance within GHL. This creates a huge barrier to using Premium Custom Webhooks. Requested Feature: Add an AI Schema Builder that asks simple questions and automatically generates the correct JSON schema. How It Should Work: Step 1: User describes what they want AI Prompt Box: "Describe what data you want to send in this webhook. Example: I want to send the contact's name, email, phone number, and the custom field 'membership_level'" User types: "Send contact first name, last name, email, company name, and custom field revenue_milestone" Step 2: AI generates the schema ______ AI generates: { "type": "object", "properties": { "firstName": { "type": "string", "description": "Contact's first name" }, "lastName": { "type": "string", "description": "Contact's last name" }, "email": { "type": "string", "description": "Contact's email address" }, "companyName": { "type": "string", "description": "Company name" }, "revenueMilestone": { "type": "string", "description": "Custom field: revenue_milestone" } } } _____ Step 3: User can edit or regenerate - Add another field - Change email to be required - Make this field a number instead of text - AI updates the schema automatically Additional Features: 1. Smart field suggestions - AI knows GHL's available fields and suggests them 2. Schema templates - Pre-built schemas for common integrations (Zapier, Slack, HubSpot) 3. Error checking - AI validates schema before saving 4. Plain English explanations - Shows what each part of the schema does 5. Test data generator - Creates sample payload to test the webhook Expected Benefits: - Faster setup - Generate schema in 2 minutes instead of 2 hours - Fewer errors - AI writes correct syntax automatically - More adoption - Non-technical users can use Premium Webhooks - Better integrations - Easier to connect GHL with other tools - Less support burden - Fewer support tickets about webhook setup Example User Flow: User: "I need to send event registration data to Zapier" AI: "I'll help you build that schema. What information about the registration do you want to send?" User: "Contact name, email, event name, registration date, and number of tickets" AI: "Got it! Here's your schema: [generates schema] This will send 5 fields to Zapier. Would you like to add anything else or test it?" User: "Looks good, save it" AI: "Schema saved! Here's a test payload you can use to test your webhook: [shows example data]" Business Impact: Democratizes webhooks - Anyone can set up integrations, not just developers Competitive advantage - Makes GHL easier to use than competitors Increases platform value - More integrations = more powerful platform Reduces support costs - Self-service schema creation Speeds up workflows - Faster setup = faster automation deployment Technical Implementation: This could use GHL's existing AI infrastructure (similar to AI content generation features) to: Parse natural language descriptions Map to GHL's data structure Generate valid JSON schema Provide interactive editing Alternative Approach: If full AI is not feasible, even a guided wizard would help: ____ Step 1: Select fields to include (checkboxes for common fields) Step 2: Choose data types (dropdown for each field) Step 3: Mark required fields (checkboxes) Step 4: Preview & generate schema