Automations

Trigger workflows when files change in a Media Storage folder (watch a folder: added, updated, deleted)
What I want: a workflow trigger that watches a specific folder in Media Storage and starts a workflow when a file is created or uploaded, updated or replaced, or deleted in that folder. Each workflow should let me pick which folder it watches (and ideally filter by file type, e.g. videos only), so different folders can drive different automations. How I use this today: Google Drive can watch a folder, and any file created, updated, or deleted there triggers a workflow in n8n. I have used that pattern over and over for content automations — a video lands in a folder and the whole pipeline starts by itself. HighLevel now lets content move through a workflow without a contact, so a Media Storage watch trigger would bring that same pattern inside HighLevel, with no outside tool in the middle. Why this helps far beyond my business: Content and media teams: a video uploaded to a folder can kick off transcription, clipping, captioning, and publishing automatically. Agencies and coaches: a client dropping assets into a folder can trigger a review, an approval request, or a delivery message to the client. Real estate, photo, and video businesses: new shoot files can auto-notify the team, start an edit checklist, or send the client a preview link. Course creators and educators: a new lesson file can start the publish checklist and notify students. Any team that files documents: an updated contract or form can trigger a review task or a message to the contact it belongs to. In every case the automation starts from the file itself, not from someone remembering to run it — and the workflow can then reach out to the contact, which is exactly the communication this platform is built for. Why it is good for HighLevel: today this pattern pushes users to n8n or Zapier for media-driven automations. A native folder-watch trigger keeps those automations inside HighLevel, makes contact-less workflows genuinely useful, and gives every media-heavy business a reason to store and manage files here instead of in Drive. In short: let a workflow watch a Media Storage folder and fire on file created, updated, or deleted — filtered by folder, so each workflow watches only the folder it cares about.
0
·
New Feature
Enable Workflow AI Build mode on Custom Object workflows
Workflow AI's Build mode is how I learn to build workflows — I describe what I want in plain language and it builds the trigger and actions for me. But Build mode does not work on Custom Object workflows, so for those I am back to building everything by hand from the trigger and action catalogs. Custom object workflows are a new way of building for most of us. The triggers, the record-based enrolment, the association actions — it is a steep learning curve when there is no AI builder to help. I am using custom objects as a content tracker (my Content Assets object, tracking transcripts, formats and statuses for repurposing), and every workflow I need there has to be built the slow way, step by step, with no AI to check my work or show me the pattern. Please enable Workflow AI Build mode inside Custom Object workflows, so I can describe the workflow I want — 'when a Content Assets record's Status changes to Completed and its Transcript is not empty, start the repurposing tasks' — and have the builder create it, the same way it does for standard workflows. Why this matters beyond my use case: every agency adopting custom objects hits the same wall. Custom objects are how HighLevel tracks things that are not contacts — content, listings, policies, inventory, courses, events — and the workflows on top of them are what make those records actually do something: notify the right person, create the follow-up task, send the update to the associated contact. If the AI builder cannot help build those workflows, most agencies will either build them wrong, build them slowly, or not build them at all — and the follow-up that should have gone to a contact never goes out. Letting Build mode work on custom object workflows teaches the new pattern while it builds, so more agencies ship working automations faster, more records drive real communication, and more of that work stays inside HighLevel instead of being rebuilt in an outside tool. That is more workflows running, more value from custom objects, and a stickier platform for HighLevel.
0
·
New Feature
Load More
→