Automations

Just like when someone comments on a post, it would be nice to be able to send an automatic message to new followers on instagram and facebook

Description: Currently, the “One day before appointment” wait step triggers exactly 24 hours before the scheduled appointment time. This makes it difficult to send reminder messages at a consistent hour. What we need: A workflow action that allows us to wait until a specific time (e.g., 9:00 AM) on the day before the appointment, regardless of the appointment’s actual hour. Example use case: If an appointment is at 14:00 or at 18:00, we should still be able to send a reminder at 9:00 AM the day before. Why this matters: Ensures consistent communication timing across all appointments. Prevents contacts from being stuck in a wait step if the appointment time changes. Avoids incorrect reminder timing when appointments are rescheduled. Helps maintain clean workflows without complicated workaround logic. Requested features: A new Wait condition: “Wait until [specific time] on the day before the appointment.” Automatic recalculation of the wait step if the appointment is rescheduled, so the contact doesn’t remain in an outdated wait. Optional fallback logic if the wait time has already passed (e.g., skip the reminder). This improvement would make appointment reminder workflows far more reliable and easier to manage.

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

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

Currently, contacts can only progress through workflows step by step or via conditional logic (If/Else, Goals, or re-enrollment). However, there is no way to manually move a contact to a specific step inside an active workflow. This creates limitations in real-life scenarios where a contact needs to be “fast-tracked” or redirected within the same workflow. Proposed solution: Add an option to “Move Contact to Step” within the workflow view or directly from the contact’s profile. This would allow admins or agents to place a contact exactly at the right point in the workflow without workarounds like tags, custom fields, or duplicating automations. Benefits: Simplifies workflow management. Saves time and avoids messy workarounds. Gives users more flexibility to handle exceptions or manual adjustments.

🔍 Summary Introduce the ability to build nested conditional logic (if/else blocks inside other if/else branches), enabling more advanced and organized automation logic without duplicating workflows or creating long, flat sequences. 🧩 Problem The current If/Else structure is single-layered, forcing users to: Chain flat logic with lots of redundant conditions Create additional workflows or custom workarounds to simulate nesting Duplicate logic just to change small branch outcomes This creates inefficiency, increases the chance of configuration error, and limits logical flexibility—especially in use cases like sales funnels, custom follow-up routines, or multi-segment journeys. 💡 Proposed Solution Allow users to drag and drop new If/Else nodes inside existing If/Else branches, supporting: Visual indentation or collapse/expand nesting view Unlimited (or reasonably capped) levels of nested logic Copy/paste logic blocks between nested nodes Seamless evaluation: child branches only process if the parent is true UI Suggestions: Use collapsible tree-style branches (like nested folders) Visual guides (e.g., connector lines or “inside branch of…” indicators) Ability to nest under “Yes” or “No” conditions ✅ Use Cases Multi-Tier Follow-Up Systems If Contact Type = Lead → If Follow-Up Type = 2 Weeks → If Follow-Up Date is today → Send reminders → Assign task → Else: Skip → Else: Tag for manual review Else If Contact Type = Client → Archive old tags → Remove from nurture workflows Advanced Qualification Flows If Form A is submitted → If score > 80 → If location = California → Send to high-priority sales queue → Else: Assign regional SDR → Else: Send to nurture Redundant Workflow Elimination Instead of creating separate workflows for minor logic changes, use nested paths for improved maintainability. 🛠 Technical Considerations (Optional for Devs) Execution engine must support condition trees Logging/Execution history should display nested paths clearly Backward compatibility: no change required for existing flat workflows 🚦Priority Justification Reduces workflow bloat Minimizes logic duplication Makes workflows easier to build, test, and maintain Empowers advanced users to consolidate decision trees into single flows Brings GHL in line with major automation platforms like Integromat, Zapier, and ActiveCampaign

We need a way to trigger automations based on comments on Instagram stories. Use case: Comment the word LUCKY on this story to get my lead magnet.

I would like to have the ability to add an internal comment to a contact via automation.

Add the ability to trigger a workflow from a client or salesperson reschedule.