Automations

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.

Hello everyone, I've been going through a lot of forums and blogs that always asks the same question which is "how to send automated dms to new IG followers" I just shared one found in the attachment

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

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

Please add native GitHub actions to HighLevel Workflows so automations can send messages and update repository data without manually building each API request. Core actions: Create or update a GitHub issue and add a comment. Create or update Markdown/JSON files in a selected repository and branch, with a commit message. Optionally open a pull request for review instead of writing directly to the main branch. Map workflow values and AI-generated output into these actions, and return the resulting GitHub URL/status to the workflow. My main use case: a scheduled weekly AI report about changes to our HighLevel workflows. Example prompt: "Every Friday, review all workflows in the selected sub-accounts, explain what changed this week and what stayed unchanged, then publish the report and the supporting data to our GitHub repository." The report should use actual workflow definitions, version history and audit records: created/deleted workflows, changed triggers, actions, conditions, messages and settings, draft vs published state, who changed what and when where available, plus links/IDs back to the source. Summarize execution results and errors separately from configuration changes. Provide a readable Markdown report plus structured JSON snapshots/diffs for traceability and later analysis by our team or an external AI assistant. Clearly distinguish verified changes, verified unchanged workflows and unavailable data; missing access must never be reported as "nothing changed". HighLevel already documents Scheduler, Custom Webhook and Workflow Version History. The request is to connect these capabilities in an easy native GitHub integration and give the reporting AI reliable access to the required workflow history, rather than relying on manually assembled exports. Allow selection of authorized sub-accounts, repository, branch, folder, schedule and timezone. Respect GitHub permissions/branch protection, keep credentials secure, exclude secrets and unnecessary contact data, and prevent duplicate posts/commits when a run is retried. This would give agencies a durable, versioned weekly record of their automations and make it easier to understand changes, investigate problems and keep operational documentation up to date.

Given that Open.AI has given the green light to allow the US government to use what they get from Open.AI to use against US citezens, a lot of people may not want their information processed through Open.AI or Gemini. Since Claude is the only one standing up against the US government at this time, many people are canceling their accounts and moving to Claude. It wont be long before people start asking if businesses that work with AI are using Claude or not. Adding in the action item feature to choose which AI source we want would help us navigate this better.

Add trigger for Youtube comments for individual video and Channel as a whole. Filter by keyword and other options you usually have. Then Action to reply as a comment. Basically the same thing that you already have for Facebook, Instagram and TikTok. https://help.gohighlevel.com/support/solutions/articles/155000002055-guide-to-facebook-instagram-comment-automation-ai

Please add a "Tiktok Lead Form Submitted" Trigger in Workflows

It would be so great if you guys would integrate TikTok Events API as an action in workflows, similar to how Facebook Conversion API is working.