Automations

Guys, I know I'm not the only one struggling with slow loading times on a lot of GHL. We replaced the 9 dots of death with the ring of stress.. We all absolutely LOVE all the new features coming out, but can we pause for a sec and just update the servers or whatever needs to be done in order to make the GHL experience even better for our clients? I'm an affiliate for GHL as well, so when I make videos promoting GHL and my load times are 30-60 seconds, it can be difficult to be confident in this for new users. So please, let's just take a second to improve overall speed and performance of GHL! Me love you long time!

Not sure why delete Task or mark complete action is not available but it would be useful specially if you already did the task in GHL and It will auto complete. No redundancy. :)

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

I realize this might be an idea from a few other posts however I would like to suggest how this might work to generalize functionality for some of these Ideas. ## Related Posts: https://ideas.gohighlevel.com/contacts/p/custom-field-array https://ideas.gohighlevel.com/contacts/p/ability-for-custom-field-objectsarrays https://ideas.gohighlevel.com/automations/p/custom-values-nested-fallback-ability-to-blank-field-types-validation "Forgive me for not posting all of these" ## Functionality Description: Array Field/Value Description and UI : Take the Checkbox Custom Field (minus the "Object" Assignment for Custom Values) and require a DEFAULT Option as well as the ability to Add More Options. Option Name and Option Value MUST be allowed to be different. For Custom Fields we can Replace the Option Value with an Option Validation field (i.e. A Dropdown with typical validation types such as STRING, BOOL, URL, EMAIL, REGEX???? maybe an idea for the future.) Should Custom Fields be Mutable? : The issue GHL has with doing this for Custom Fields is that Mutability of the Array Keys is not possible. I prompted Grok 3 for a brief explanation : "Mutability of standard array keys for a database field can cause issues because it risks breaking consistency and integrity in data retrieval and storage. If keys are altered dynamically, queries or application logic relying on specific key names may fail, leading to errors or unpredictable behavior. It also complicates data validation, schema mapping, and debugging, as the expected structure becomes unreliable across different parts of the system." Forgive me if I am using the wrong terminology to describe the software (mutability vs immutability). In theory, for Custom Fields, Options MUST BE IMMUTABLE AFTER SUBMISSION. The only exception that could be allowed for a deletion of an option. This SHOULD come with a warning and delete this field from every contact in the database. How to call this in workflows/email templates/etc : EXAMPLES: We will be using a typical merge tag and array syntax. Since we have a default field, any value can be set for the key: {{ contact.custom_array[1] }} {{ custom_value.message_option[1] }} {{ custom_value.colors["Primary"] }} Allow for a SECOND field/value to become the array key {{ contact.custom_array[inboundWebhookRequest.foobar]}} Updating through Workflows : Options MUST be Updated via each specific KEY. When you click to update an option that is an array , you will then be given the options to select the specific KEY you would like to Update, Add, Clear, etc.

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,

A while ago HighLevel added a MUCH needed feature to Email Campaigns: the option to "Set a custom reply-to address for this campaign." But the same option was NOT added to email actions within Workflows. This is a shame, because... One of the most beneficial uses of this new feature is to bypass the dedicated subdomain address as the reply-to (e.g. @ email.yourdomain.com ) which HL uses for tracking, and bypassing this is great if the emails you send from HL look like they are "from staff in your company" but those same staff don't USE HighLevel for email communications and would never see a reply within HL, so instead you just want recipient replies to go to the actual "Sent From" email address (e.g. @ yourdomain.com ) so the staff member receives the reply. BUT often times for this use case we're using Workflows to send emails that look like they come from staff, and if we use Workflows instead of Campaigns we don't have this option.

Right now this only works for the email workflow but not for internal email notifications.

Currently in HighLevel, we can associate related contacts through Related Objects or use the “Association” feature to link records—such as a spouse, co-borrower, lender, or partner—to the primary contact. However, workflows are limited to only pulling data directly from the current contact, with no access to fields from any associated contact records. This is a significant limitation, especially in industries like real estate, lending, or healthcare where transactions often involve multiple stakeholders. For example: A real estate agent might want to CC a spouse or co-borrower on automated email or text sequences. A mortgage lender might be linked as an associated contact and should receive status update emails or tasks. A healthcare portal might want to notify both patient and caretaker (linked as related contact) during onboarding or appointment follow-ups. Proposed Enhancement: Allow workflows to access fields (email, phone, custom fields, etc.) from any associated contact or custom object relationship tied to the current contact. This would allow us to: Use merge fields from associated contacts (e.g., {{associated_contact.email}}) Add associated contacts to communication steps (email, SMS, tasks) Trigger conditional logic based on associated contact tag or fields Create smart automations involving multiple parties without duplicating workflows Why It Matters: This enhancement would dramatically increase the flexibility and relational power of the CRM. It would enable more dynamic automations, reduce workflow duplication, and better reflect real-world relationships between people and roles in complex industries.

With DND, when a contact gets the email status of DND, I can make a workflow to tag that person as DND Email. I need the same ability to do this for Hardbounced people so we can filter them out with the tag Hardbounced in email campaign or broadcast sends. Right now we have to export and then re-import contacts to add the tag. That means before I send ANY emails, I have to do this step for the last email. That's really a huge flaw in your database - the fact I can't drilldown and tag people inside of the stats - I have to do an entire export/import/tag dance.

Almost every automation platform offers this feature; it's really straightforward. Import/Export workflow JSON files. This makes backing up and transferring workflows super simple.