Native video/recording-ready triggers and GoKollab content inputs for AI workflows
T
Théo JUSTINE
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:
Log In