Automations

We need a workflow action for workflows that trigger with an inbound webhook so that as the last action, it can return JSON to the calling system along with an HTTP status code.

The client is trying to dynamically populate a Date & Time custom field (First Contact Attempt Date) with the actual call start timestamp using the Update Contact Field workflow action. Currently, the action only displays a fixed date/time picker, with no option to select dynamic values or workflow variables. Expected Functionality: Allow Date & Time custom fields to accept dynamic values, such as call start time, workflow timestamps, or Date/Time Formatter outputs, so these fields can be updated automatically through workflows. Business Impact: The client needs to track the exact time of the first contact attempt automatically. Using a text field as a workaround doesn't provide the same functionality as a proper Date & Time field.

Please add a native TikTok follower-to-conversation journey in HighLevel: someone follows a connected TikTok business account, receives an eligible welcome DM, and can enter a workflow to continue the conversation. Requested capabilities: A "New TikTok follower" trigger when TikTok provides an authorized event for that account, with account/sub-account filters and duplicate protection. Configuration and visibility of TikTok's official new-follower welcome message, including supported quick replies, review/approval status and whether it is enabled. When the person responds, continue through the existing TikTok DM workflow actions: create/update the permitted CRM contact data, tag the source, assign a team member, qualify the request and follow up within the allowed messaging window. Show the actual event used (follow, welcome sent, or follower reply) and delivery/blocked status. If TikTok only exposes the welcome configuration and later replies, make that limitation explicit rather than presenting a reply-triggered workflow as a real-time follow event. Example: "Thanks for following! Would you like our free guide?" The person's reply starts the next workflow step, with the exchange visible in Conversations. Avoid duplicate welcome messages across TikTok's native setup and HighLevel. HighLevel already documents TikTok comments and Customer Replied triggers; this request concerns the earlier follow event and new-follower welcome journey. TikTok's Business API documentation describes FOLLOW_WELCOME for a message sent when someone follows an account: TikTok Business API — automatic messages This is evidence of a provider capability, not proof that TikTok exposes a per-follower webhook or makes it available to all HighLevel accounts. Please use the official APIs, show account/country eligibility and any approval or messaging limits, and enable the feature only where TikTok allows it. HighLevel's integration documentation currently states geographic restrictions, so this should also make availability clear for European agencies. For Instagram/Facebook, there is already a separate planned request: https://ideas.gohighlevel.com/automations/p/automatic-messages-to-new-instagram-followers

EVERYTHING should be able to create, edit, manage, all features etc using claude. If you don't do this fast, nothing else will matter. GHL will become a thing of the past.

I could really use a contact added to smart list trigger. I can make way better filter in the contact section and have it where people are dynamically added to smart list based on those. It would be awesome to have the trigger contact added to smartlist for automations!

Ability to Trigger a workflow based on an image being added to an Opportunity File Upload custom field

Please make content created anywhere in HighLevel usable as a native workflow input, so a finished recording or a community discussion can lead directly to AI analysis and follow-up actions. HighLevel already announced AI Analyze Video (video URL + prompt), and Group Post Created / Group Comment Created triggers. This request is to connect and extend those capabilities, especially for private native media and recordings created outside a workflow. Requested additions: Video / Recording Ready triggers across Media Library, native recording tools, Meeting Rooms, GoKollab live replays, webinar recordings, course videos and AI-generated videos. Fire when upload/recording processing has finished, with a separate event for processing failure. Ending a live must not trigger analysis before its replay is available. Source filters: sub-account, product/tool, community, channel, event, course or media folder. Pass the asset ID, source link, title, author and relevant member/contact IDs to subsequent steps. Content-level workflows should not require an artificial contact or run once per attendee. Use the existing community post/comment triggers to expose the message text, parent-thread context and attached media to AI steps. Support authorized GoKollab chat-message events as well, with explicit scope for which conversations the integration can access. Let AI Analyze Video accept a native media reference, including private recordings, without making the asset publicly accessible. Keep existing access permissions. Provide transcription, summaries, questions, decisions and action items as outputs that later workflow steps can use; distinguish transcript-only analysis from analysis of both picture and sound. Chain those outputs into notes, custom fields/objects, task creation, internal notifications, drafted replies or webhooks. Include an optional human review step before publishing an AI-generated response. Prevent duplicate processing and loops caused by workflow-generated content. Examples: • GoKollab live ends → replay ready → AI summary + unanswered questions → tasks for the team and a draft recap. • Member posts a support question with a video → analyze text and video → classify the issue → notify the right person and prepare a reply. • A video is recorded or generated elsewhere in HighLevel → workflow analyzes it → save the result and continue the configured actions. This builds on the recent releases rather than requesting a second AI video-analysis action. It would make videos, replays and community messages part of the same automation system as CRM activity. Existing releases: https://ideas.gohighlevel.com/changelog/ai-analyze-video-new-workflow-action https://ideas.gohighlevel.com/changelog/new-communities-triggers-in-workflows-automate-more-faster

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.

Please add the possibility of adding contact or custom value fields to the find parameter instead of a hard value in the Text Formatter automation's Find action.

I’d like to suggest a feature for GoHighLevel workflows: the ability to automatically calculate a contact’s age based on their date of birth submitted through a form. This would make it possible to create workflow conditions based on age. A practical use case would be splitting users into different funnels depending on whether they are over or under 18. This would be very useful for segmentation, automation, and age-based funnel logic.