Vizard AI + Slack: top YouTube clips picked for you
You upload a long YouTube video, then lose half your afternoon scrubbing for “the moment.” You still second-guess which clip will actually pop on Shorts, TikTok, or Reels. And the review loop? Screenshots, timestamps, messy threads.
This Vizard Slack clips automation hits social media managers hardest, but content creators and small marketing teams feel it too. You get a short list of the best clips (already scored) delivered to Slack, so your team can approve faster and publish with more confidence.
Below, you’ll see how the workflow runs, what it replaces, and what you can tweak (like the viral score threshold and number of clips).
How This Automation Works
The full n8n workflow, from trigger to final output:
n8n Workflow Template: Vizard AI + Slack: top YouTube clips picked for you
flowchart LR
subgraph sg0["form_ Flow"]
direction LR
n0["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/form.svg' width='40' height='40' /></div><br/>form_trigger"]
n1["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>submit_video"]
n2@{ icon: "mdi:cog", form: "rounded", label: "wait", pos: "b", h: 48 }
n3@{ icon: "mdi:swap-horizontal", form: "rounded", label: "check_status", pos: "b", h: 48 }
n4["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>send_initial_msg"]
n5@{ icon: "mdi:swap-vertical", form: "rounded", label: "set_videos", pos: "b", h: 48 }
n6["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/httprequest.dark.svg' width='40' height='40' /></div><br/>get_clipping_status"]
n7@{ icon: "mdi:swap-vertical", form: "rounded", label: "split_videos", pos: "b", h: 48 }
n8["<div style='background:#f5f5f5;padding:10px;border-radius:8px;display:inline-block;border:1px solid #e0e0e0'><img src='https://flowpast.com/wp-content/uploads/n8n-workflow-icons/slack.svg' width='40' height='40' /></div><br/>send_video_msg"]
n9@{ icon: "mdi:swap-horizontal", form: "rounded", label: "filter_viral_score", pos: "b", h: 48 }
n2 --> n6
n5 --> n7
n3 --> n4
n3 --> n2
n0 --> n1
n7 --> n9
n1 --> n2
n4 --> n5
n9 --> n8
n6 --> n3
end
%% Styling
classDef trigger fill:#e8f5e9,stroke:#388e3c,stroke-width:2px
classDef ai fill:#e3f2fd,stroke:#1976d2,stroke-width:2px
classDef aiModel fill:#e8eaf6,stroke:#3f51b5,stroke-width:2px
classDef decision fill:#fff8e1,stroke:#f9a825,stroke-width:2px
classDef database fill:#fce4ec,stroke:#c2185b,stroke-width:2px
classDef api fill:#fff3e0,stroke:#e65100,stroke-width:2px
classDef code fill:#f3e5f5,stroke:#7b1fa2,stroke-width:2px
classDef disabled stroke-dasharray: 5 5,opacity: 0.5
class n0 trigger
class n3,n9 decision
class n1,n6 api
classDef customIcon fill:none,stroke:none
class n0,n1,n4,n6,n8 customIcon
The Problem: Finding “the clips” is a time sink
Turning one long-form YouTube video into short clips sounds simple until you do it weekly. You watch the full video (again), mark timestamps, export candidates, then argue internally about which moment is actually worth publishing. Meanwhile the calendar keeps moving. The worst part is the uncertainty: you’re not just cutting clips, you’re trying to predict what will perform, and that guesswork tends to create delays, endless revisions, and “we’ll post it tomorrow” days that turn into… never.
It adds up fast. Here’s where it usually breaks down.
- Reviewing a 20–60 minute video for highlights can easily eat about 2 hours once you include rewinds, notes, and exports.
- Great moments get missed because the team relies on memory and gut feel instead of a consistent scoring method.
- Approvals drag because clips live in random folders, and nobody wants to download five drafts just to pick one.
- When you scale to multiple videos a week, the whole process becomes bottlenecked by one person’s time.
The Solution: Vizard AI scoring + Slack delivery for fast approvals
This workflow takes a YouTube URL, sends it to Vizard AI for automated clipping, waits for the analysis to finish, and then brings back a shortlist your team can actually use. Vizard generates up to 8 candidate clips and attaches a “viral score” to each one. n8n then filters those results so only the best clips (by default, 9/10 or higher) make it through. Finally, the workflow posts the winners into a Slack channel with the clip title, score, and a download link, which means the review happens where your team already works.
The workflow starts when you submit a YouTube URL through a simple intake form. After Vizard finishes processing, n8n splits the returned clips into individual items, filters by score, then posts the finalists to Slack for quick yes/no decisions.
What You Get: Automation vs. Results
| What This Workflow Automates | Results You’ll Get |
|---|---|
|
|
Example: What This Looks Like
Say you publish 3 long YouTube videos per week and you want Shorts from each. Manually, most teams spend about 2 hours per video finding moments, cutting candidates, and sending them around, so that’s roughly 6 hours weekly just on “clip hunting.” With this workflow, submitting each URL takes about a minute, Vizard processes in the background, and your team only reviews the top-scoring results in Slack (maybe 10 minutes per video). That’s about 5 hours back every week, and the decisions happen faster.
What You’ll Need
- n8n instance (try n8n Cloud free)
- Self-hosting option if you prefer (Hostinger works well)
- Vizard AI for automatic clip creation and scoring
- Slack to deliver clips for team review
- Vizard AI API key (get it from your vizard.ai account)
Skill level: Beginner. You’ll connect accounts, paste an API key, and choose a Slack channel.
Don’t want to set this up yourself? Talk to an automation expert (free 15-minute consultation).
How It Works
You submit a YouTube URL through the intake form. That single entry is the trigger, so there’s no messy copying into multiple tools or spreadsheets.
n8n sends the video to Vizard AI and starts checking status. The workflow submits a processing job, waits, then polls Vizard until results are ready. This is the quiet part that normally forces you to keep tabs manually.
Clips are unpacked and scored clips are filtered. n8n takes the returned list, splits it into individual clip items, then keeps only the ones above your quality bar (the default is 9/10 or higher).
Slack gets the finalists. The workflow posts a note when results arrive, then posts each high-scoring clip with title, score, and link so reviewers can act immediately.
You can easily modify the viral score threshold to match your standards based on how picky you want to be. See the full implementation guide below for customization options.
Step-by-Step Implementation Guide
Step 1: Configure the Form Trigger
Set up the intake form that starts the workflow when a YouTube URL is submitted.
- Add the Intake Form Trigger node as the trigger.
- Set Form Title to
YouTube Video Clipper. - Under Form Fields, add a field labeled
YouTube Video Urland mark it as required.
https://www.youtube.com/watch?v=DB9mjd-65gw to validate the input format during testing.Step 2: Connect the Vizard API Job Submission
Submit the video to Vizard for clipping and configure the request authentication.
- Add the Submit Video Job node and connect it after Intake Form Trigger.
- Set URL to
https://elb-api.vizard.ai/hvizard-server-front/open-api/v1/project/createand Method toPOST. - Set Body Content Type to
JSONand JSON Body to={ "lang": "en", "preferLength": [ 0 ], "videoUrl": "{{ $json['YouTube Video Url'] }}", "videoType": 2, "maxClipNumber": 8}. - Credential Required: Connect your httpHeaderAuth credentials in Submit Video Job.
projectId will be available for status checks.Step 3: Set Up Status Polling and Processing Logic
Wait for the clip job to finish, then check status, map results, and filter high-scoring clips.
- Connect Submit Video Job to Pause Interval and set Amount to
10. - Add Fetch Clip Status after Pause Interval and set URL to
=https://elb-api.vizard.ai/hvizard-server-front/open-api/v1/project/query/{{ $json.projectId }}. - Credential Required: Connect your httpHeaderAuth credentials in Fetch Clip Status.
- In Status Condition, set the condition to
={{ $json.code }}equals2000. - Connect the true path of Status Condition to Post Initial Slack Note and the false path back to Pause Interval to keep polling.
- In Map Video List, assign videos to
={{ $('Status Condition').item.json.videos }}. - In Split Video Items, set Field to Split Out to
videos. - In Filter Viral Scores, set the condition to
={{ $json.viralScore }}greater than or equal9and keep Loose Type Validation enabled.
code 2000 (ready state).Step 4: Configure Slack Output Messages
Send an initial header message, then post each qualifying clip as a threaded reply.
- In Post Initial Slack Note, set Text to
=<{{ $('Intake Form Trigger').item.json['YouTube Video Url'] }}|Video Clipper Results>and choose your Channel. - Credential Required: Connect your slackOAuth2Api credentials in Post Initial Slack Note.
- In Post Clip to Slack, set Text to
=*{{ $json.title }} | ({{ $json.viralScore }} / 10)* ``` {{ $json.videoUrl }} ``` ---. - In Post Clip to Slack, set Thread TS to
={{ $('Post Initial Slack Note').item.json.message.ts }}so clips post as replies. - Credential Required: Connect your slackOAuth2Api credentials in Post Clip to Slack.
[YOUR_ID], messages will fail. Replace it with a real channel ID.Step 5: Test and Activate Your Workflow
Run a manual test to validate the full job submission, polling loop, and Slack notifications.
- Click Execute Workflow and submit a valid YouTube URL in the Intake Form Trigger.
- Confirm Submit Video Job returns a
projectIdand that Fetch Clip Status eventually returnscode2000. - Verify Slack receives a header message from Post Initial Slack Note and threaded clip messages from Post Clip to Slack for clips with
viralScore≥9. - When satisfied, toggle the workflow to Active so it runs in production.
Common Gotchas
- Slack credentials can expire or need specific permissions. If things break, check your n8n Slack OAuth connection and the selected channel access first.
- If you’re using Wait nodes or external rendering, processing times vary. Bump up the wait duration if downstream nodes fail on empty responses.
- Default prompts in AI nodes are generic. Add your brand voice early or you’ll be editing outputs forever.
Frequently Asked Questions
About 30 minutes if your Vizard and Slack accounts are ready.
No. You’ll paste an API key, connect Slack, and choose your channel.
Yes. n8n has a free self-hosted option and a free trial on n8n Cloud. Cloud plans start at $20/month for higher volume. You’ll also need to factor in Vizard AI API costs based on your video volume.
Two options: n8n Cloud (managed, easiest setup) or self-hosting on a VPS. For self-hosting, Hostinger VPS is affordable and handles n8n well. Self-hosting gives you unlimited executions but requires basic server management.
Yes, and it’s one of the best tweaks to make. Change the condition in the “Filter Viral Scores” node from 9/10 to something like 8/10 if you want more options in Slack. You can also adjust how many clips Vizard generates by changing the maxClipNumber parameter in the initial “Submit Video Job” request (it defaults to 8). If you want a tighter approval experience, keep the threshold high and post fewer, better candidates.
Usually it’s expired or revoked Slack OAuth credentials inside n8n. Reconnect Slack in your n8n credentials and confirm the workflow has access to the exact channel you selected. If you’re posting to a private channel, make sure the app/bot is actually invited to it. Less common, but it happens: your workspace admin policies can block new apps, so approvals may be required.
A lot, as long as you size it to your usage. On n8n Cloud, capacity is based on monthly executions (each status check and each clip posted counts), so higher volume usually means a higher plan. If you self-host, there’s no execution cap, but your server and Vizard processing limits still matter. In practice, most teams start with a few videos per week, then scale once the Slack review loop is working smoothly.
Often, yes, because this flow needs waiting, polling, item-by-item filtering, and multi-message posting, and n8n handles that without feeling “fighty.” Zapier or Make can work, but you may end up paying more once you add loops and repeated status checks. If your process is simple (one video, one message, no filtering), those tools can be quicker to start. For a real clipping pipeline with scoring and a review channel, n8n is usually the cleaner fit. Talk to an automation expert if you want help deciding.
Once this is running, “find clips” stops being a project and turns into a simple Slack review. The workflow handles the repetitive parts, so you can focus on publishing.
Need Help Setting This Up?
Our automation experts can build and customize this workflow for your specific needs. Free 15-minute consultation—no commitment required.
