Automations

It would be an awesome addition if we could leave custom notes on action steps and triggers in our own wording to explain how they work in case we forget in the future or for new user!

Would be great to be able to see which automations use a specific tag when clicking on the tag. that way we click and it would appear "Used in: (specific workflows)"

We can set campaigns to run only on certain days of the week, but it would be helpful to cause all campaigns to pause on specific dates, especially important holidays -- such as Thanksgiving, Christmas, New Year's, etc.) that are off-limits for contacting prospects. Right now we must put every campaign in draft status manually. HIGHLVL-I-841

Currently, you can select the name and email for the emails within the workflow, I think it would be ideal if you can select what number you want to have the automations go out as well. This way if you are working with clients that have locations with different area codes, we can provide the automation to fit that specific local area. Or even an additional option with the SMS action within the workflow. Some clients prefer to have one subaccount with multiple pipelines instead of being in and out of multiple subaccounts.

We are loving high level but we NEED a trigger when payments for subscription or products fails or when subscriptions are cancelled. There is no way of updating an opportunity or a contact based on this.

Ability to copy workflows to other locations.

This is very important. I thougt we can update both custom value and and custom fields using math operations but you can only use custom field with math operation in workfow. This is going to solve a lot of problem and minimize using 3rd party integration. In this screenshot you can only update standar field and custom field. Custom value is not available. https://www.loom.com/i/5d4e3dafa2ac4d19ae28066ff698aef3

The workflow's voicemail trigger mislabels ALL missed calls as voicemails, causing incorrect notifications for clients. So if a client wants to be notified of Voicemails only, the workflow trigger doesn't work because it catches all missed calls and treats them as voicemails. Easy fix: Is there an mp3 Voicemail recording- mark as VM. No recording file? - Missed Call

There is a conflict between the way that the new Inbound Webhook Triggers identify contacts and the Allow Duplicate Contacts setting. I'm trying to allow a contact to receive multiple "Estimates" on a "Ticket" before assigning the opportunity to the user whose estimate was accepted. A contact can have multiple tickets and can receive multiple estimates on each ticket before the opportunity is assigned. Because there's no way to put one contact into the same workflow, I have to use the Allow Duplicate Contacts setting to allow multiple tickets. Then, updating an Opportunity becomes impossible because I can't select the Opportunity associated with the correct Contact. There are two (real) (maybe three) ways to fix this: Allow the Inbound Webhook Trigger to identify the contact by their ID. Create an Array type of Custom Field (or "Custom Objects") https://highlevel.canny.io/crm/p/custom-objects Create Custom Fields on Opportunities (not recommended)* I think that allowing a contactId parameter on the Inbound Webhook Trigger itself would be the easiest and most intuitive way to do it. https://www.loom.com/share/404789dffc754ee587990aba2e387a30 * by allowing Multiple Opportunities, you can create one Opportunity per "Estimate" and then sort the ticket out manually, but this eliminates the potential for automation, since Workflows operate on Contacts, not Opportunities. It will also select an arbitrary contact each time, which creates further confusion, eliminating the potential for a Contact to have multiple Tickets with Estimates.

Looking at the execution log doesn't really help to tell what path an account went down. Actions show the action type but not the action name we give it so don't know which path that action happened in. Would be great if we can select a past contact while in the builder and see the highlighted path that contact went through then be able to restest that contact without the actions firing.