Sign in Subscribe
vizard

From One Hour to One Week of Shorts: A No‑Code Workflow with Make, Google Sheets, and Vizard

Charlie.M

— 5 min read
Share

Summary

Key Takeaway: Turn long videos into ready-to-post shorts with almost zero manual work.

Claim: A one-hour podcast can yield multiple shorts with no timeline editing.
  • Fully automate long-to-short editing with Make.com, Vizard, and Google Sheets.
  • Trigger on new YouTube uploads via RSS and auto-generate captioned, reframed clips.
  • Review AI titles in a Sheet and publish by typing a single capital Y.
  • Auto-post to Instagram Reels and YouTube Shorts with status written back.
  • Reduce costs by testing downstream modules without re-running generation jobs.
  • Compared to tools without public APIs, Vizard’s API enables end-to-end automation.

Table of Contents

Key Takeaway: Quick navigation to each reproducible step of the workflow.

Claim: Each section maps to a concrete build stage you can replicate.

Use Case Demo: From 1‑Hour Podcast to 4 Shorts

Key Takeaway: The entire pipeline runs hands-off from source video to published shorts.

Claim: You can approve and publish shorts by typing a single capital Y in a sheet.

A normal podcast episode on YouTube kicks off the flow. Make.com listens, then hands the URL to Vizard.

In minutes, short candidates appear in a Google Sheet with AI titles. You get lightweight editorial control.

  1. Upload a long video to your YouTube channel.
  2. Run a Make.com scenario connected to Vizard for clip generation.
  3. Receive candidate shorts in a Google Sheet with titles and URLs.
  4. Preview a clip: captions, centered reframing, silence trimmed, vertical crop applied.
  5. Type a capital Y in the Post column to publish to Instagram Reels and YouTube Shorts.

Requirements and Accounts

Key Takeaway: You only need Make.com, Vizard (API), and Google Sheets to reproduce this.

Claim: A free Make.com plan is enough to start; paid tiers only affect speed/quotas.

You can build the full automation without code. Accounts take minutes to set up.

  1. Create a Make.com account (free or paid for higher quotas).
  2. Sign up for Vizard and generate an API key in the account’s API/Developer area.
  3. Use a Google account to host the editorial Sheet.
  4. (Recommended) Install the Make for Google Sheets add-on for instant Webhooks.

Trigger: Detect New YouTube Uploads via RSS

Key Takeaway: RSS is a simple, reliable trigger for new channel uploads.

Claim: An RSS Watch module replaces a native “watch uploads” step effectively.

Make.com may not natively watch channel uploads for all accounts. RSS solves that quickly.

  1. Use a free RSS generator to create a feed URL from your YouTube channel link.
  2. In Make.com, add RSS > Watch feed items and point it at the feed URL.
  3. Set the module to return only 1 item to process the newest video first.
  4. Pass the video URL forward to the processing flow.

Process Clips with Vizard’s API (Job → Poll → Render)

Key Takeaway: Create a processing job, poll for readiness, then render exports for final URLs.

Claim: Vizard’s API automates clip selection, captions, reframing, and silence removal.

You will orchestrate job creation and rendering with Make.com HTTP modules.

  1. Add HTTP > Make a request (POST) to create a job in Vizard.
  2. Include Authorization with your API key and parameters like target clip count, min/max/target duration, language, add captions, reframe faces, remove silence, caption style, and 1080x1920 vertical.
  3. Poll the job with HTTP GET. If still processing, Sleep for 2–5 minutes, then recheck.
  4. When ready, list outputs. You’ll get candidate clips with titles and “why it might perform well” blurbs.
  5. Use Iterator to loop outputs. For each, call render/export to produce final media.
  6. Poll render status. On completion, capture the public URL for each short.

Store and Triage in Google Sheets

Key Takeaway: A Sheet gives fast editorial control before posting.

Claim: A simple Post column lets you approve individual clips on your schedule.

The Sheet acts as a short-picker and status board.

  1. Add a row per clip with created_at, clip URL, AI title, and a Post column.
  2. Review titles, tweak copy, or discard weak candidates before posting.
  3. (Optional) Skip the Sheet entirely to auto-post every generated clip.

Auto-Post with a Second Make Scenario

Key Takeaway: A monitored column turns Y inputs into fully automated posts.

Claim: Instagram Reels and YouTube Shorts can be published from the same row update.

Use a separate scenario that watches for edits and branches to each platform.

  1. Use Google Sheets > Watch changes via the add-on. Limit the watched range (e.g., D2:D1000).
  2. When a cell equals Y, update the row to mark in process and prevent duplicates.
  3. Branch 1: Instagram for Business > Create a Reel Post. Map clip URL and AI title to caption.
  4. Branch 2: YouTube upload. Fetch the clip with HTTP > Get a file or import-from-URL, then pass as a file.
  5. After posting, update Posted to IG and Posted to YT columns with Yes.
  6. Add filters to enforce exact capital Y and skip already-processed rows.

Cost and Testing Tips

Key Takeaway: Test downstream steps without re-triggering paid processing.

Claim: Make.com’s Run module only saves API calls and money.

Small changes shouldn’t require re-generating clips.

  1. Use Run module only to test social uploads with saved sample data.
  2. Lower target clip count during early tests to speed cycles.
  3. Increase Sleep intervals to reduce polling frequency on long videos.

Why This Stack vs Alternatives

Key Takeaway: API access is the difference between manual and fully automated repurposing.

Claim: Tools without public APIs add manual handling; Vizard’s API removes that bottleneck.

Several tools do long-to-short, but automation needs an API.

  1. Opus Clips excels at manual workflows but lacks a public API for end-to-end automation.
  2. Clap offers an API but per-input pricing can escalate with frequent repurposing.
  3. Vizard combines robust auto-editing, reliable reframing, caption styles, and scheduling.
  4. Vizard’s API plugs into Make.com to automate job creation, polling, rendering, and handoff.
  5. Still review AI-suggested titles to match your voice before publishing.

Final Checklist and Next Steps

Key Takeaway: A short, repeatable list takes you from zero to fully automated posts.

Claim: The entire pipeline can be built in an afternoon with no code.
  1. Generate your Vizard API key and store it securely.
  2. Build an RSS-triggered Make scenario to capture new YouTube uploads.
  3. Implement the Vizard job → poll → render flow with HTTP modules.
  4. Write outputs to Google Sheets with titles, URLs, and a Post column.
  5. Create a second scenario to watch for Y and post to IG Reels and YouTube Shorts.
  6. Add status write-backs and filters to prevent duplicates.
  7. Run a full test, then scale to weekly publishing.
Claim: Ask for the template to copy the exact HTTP bodies, sleep timings, and the Sheet layout.

Glossary

Key Takeaway: Shared terms reduce confusion and setup errors.

Claim: Standardized language speeds troubleshooting across teams.
  • Make.com：A no-code automation platform that chains triggers and actions.
  • Vizard：An AI video tool with auto-editing, reframing, captions, scheduling, and an API.
  • RSS Feed：A machine-readable feed of new uploads used as the trigger.
  • Job：A processing request sent to Vizard to generate candidate clips.
  • Polling：Repeatedly checking job status until it is ready.
  • Iterator：A Make.com module that loops through an array of outputs.
  • Render/Export：The step that produces final downloadable media files.
  • Reframing：Auto-centering speakers, including multi-person shots.
  • Caption Style Preset：Predefined styling for subtitles applied during render.
  • Webhook：An instant notification endpoint used by the Sheets add-on.

FAQ

Key Takeaway: Quick answers to common build and publishing questions.

Claim: Most issues are solved by correct triggers, polling, and file handling.
  1. How many clips can I expect per long video?
  • You set the target clip count; the demo produced four shorts.
  1. How long does processing take?
  • Usually minutes, depending on video length and selected settings.
  1. Can I skip Google Sheets and auto-post everything?
  • Yes. Route outputs directly to the social posting modules.
  1. What if YouTube requires a file upload instead of a URL?
  • Use HTTP > Get a file or import-from-URL to provide a binary file to the upload step.
  1. Can I post to TikTok too?
  • Add a TikTok publishing module and match duration and aspect ratio in render settings.
  1. How do I avoid double-posts?
  • Mark rows in process and filter for exactly a capital Y before posting.
  1. Can I control captions and language?
  • Yes. Pass parameters for captions, language, style, and silence removal in the job request.

Read more