Automations

same concept you have for Instagram and Facebook, it would be great to have TikTok Triggers in the automation workflows for when people comment on posts and or send DMs to a tiktok account.

Hi everyone, TikTok has quickly become a key platform for driving traffic to businesses, but managing user interactions can be challenging. Unlike Facebook and Instagram, where we already have tools to automate comments and DMs, TikTok still lacks a robust solution. The Proposal I suggest implementing an automation system for TikTok similar to what we use on other platforms, which would include: Automated comment replies: Keep interactions active effortlessly. Automated DMs: Send information or promotions to users who comment with specific keywords. Benefits -Time-saving: Reduce the need to manually respond to every comment. -Increased conversion: Leverage immediacy to guide users toward specific actions. -Better user experience: Quick responses enhance brand perception. TikTok is booming, and automating these functions can help us maximize its potential. What are your thoughts on integrating this strategy? Best regards,

It would be very useful to be able to copy not only a step or two from one workflow to another but also entire sections. This would save a lot of time if there is a section in one workflow you need in another. Right now you essentially have to manually recreate every single step from one workflow in a new one.

This submission addresses a critical system limitation within the Opportunities object type that prevents the dynamic mapping of values for checkbox, radio, and dropdown fields, within the workflow action "Create Opportunity". The Problem Currently, when attempting to pass information between two opportunities (e.g., from an existing Opportunity A to a newly created Opportunity B), it is impossible to dynamically map values for checkbox, radio, and dropdown fields, even when the fields are identical across both opportunities. As illustrated in the attached screenshot, the "Dynamic" option is unavailable when configuring these field types for mapping. Instead, users are forced to select a static, pre-defined option from the field's choices, rendering the mapping functionality ineffective for these field types. Why This is a Limitation This limitation forces users to employ cumbersome workarounds, such as using "single line" text fields. This requires manual data entry by the client, where they must type in information that is typically standardized and pre-defined within checkbox, radio, or dropdown selections. This introduces several problems: Data Inconsistency: Manual entry of coded information drastically increases the risk of typos and inconsistencies. Increased Manual Effort: Clients and users are burdened with unnecessary manual tasks. Reduced Automation Efficiency: The platform's ability to automate workflows and maintain data integrity is significantly hampered. Expected Behavior & Benefits The expected and highly beneficial behavior would be the ability to dynamically map values for checkbox, radio, and dropdown fields. If Opportunity A has a checkbox field called "Desired Service," and a newly created Opportunity B has an identical "Desired Service" checkbox field, the value selected in Opportunity A should be directly mappable to Opportunity B. Implementing this functionality would provide immense value by: Ensuring Data Accuracy: Guarantees that consistent and coded information is passed accurately between opportunities. Improving Workflow Efficiency: Automates data transfer, saving significant time and reducing manual errors for all users. Enhancing User Experience: Simplifies the process for clients and internal teams by eliminating redundant manual data entry. Strengthening Platform Robustness: Aligns the behavior of these field types with other mappable fields, making the Opportunities object more powerful and versatile. This enhancement is crucial for maintaining data integrity and maximizing the automation potential within the HighLevel platform.

In Make and Zapier, you can copy steps from one workflow to another and this would be amazing to have HighLevel as well. Zapier is good to grey out the missing stuff that needs to be reconfigured etc. That would also be good to think through.

I have a membership and I made a custom field that's a date field for Membership Billing End Date. We have a monthly recurring billing and a yearly recurring billing. Currently for a custom field for dates, there's only Right Now (today) as an option. I am requesting options for both past and future such as 30 days ago, 30 days from now, 60 days ago, 60 days from now, 90 days ago, 90 days from now, and 1 year ago, 1 year from now.

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

Need to wait until a task is completed before the next step in the workflow. Very important with salespeople doing multi-email sequences. Need time to do calls and research.

I hope GHL will allow us to use custom values (like "Additional Information" or internal notes) when manually booking appointments in the GHL calendar tab. Right now, those Custom values only show when booking through a form or widget, but not during manual booking — which limits automation and email confirmation content. This feature would help match manual bookings with the same flexibility as widget-based ones. Adding this feature would make manual bookings just as flexible as widget-based ones. Looking forward to seeing this improvement soon! So that every notes we have added in the internal notes clients/assigned user can see it in the email confirmation and reminder

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