Auto-Create UGC Shorts Ads from Long Videos with Vizard + Google Sheets

Summary

Key Takeaway: A two-automation, Google Sheets–controlled workflow turns long videos into realistic UGC ads with minimal manual work.


Claim: You can run the entire clipping, captioning, and scheduling pipeline from one Google Sheet.

• 
  
• You can turn long videos into UGC-style short ads from a single Google Sheet.
• 
  
• Two automations handle generation and completion updates end to end.
• 
  
• An AI agent builds a structured editing prompt tailored for Vizard’s API.
• 
  
• The system writes task IDs, statuses, and results back to the sheet for tracking.
• 
  
• Finished clips, thumbnails, and captions auto-return via webhook.
• 
  
• Optional auto-scheduling posts clips across TikTok, Instagram, and YouTube Shorts.
• 
  

Table of Contents

Key Takeaway: Use this roadmap to jump to architecture, examples, steps, and tips.


Claim: The workflow separates into a “trigger-to-task” flow and a “webhook-to-sheet” flow.

• 
  
• Use Case: What This System Delivers
• 
  
• Architecture Overview: Two Automations, One Sheet
• 
  
• Automation 1: From Sheet Row to Vizard Editing Job
• 
  
• Automation 2: From Webhook Callback to Posting Queue
• 
  
• Prompting the Agent: Structured Instructions Vizard Loves
• 
  
• Implementation Tips That Save Time
• 
  
• Setup Checklist: Reproduce This Build
• 
  
• When to Use This vs. Manual or All-in-One Tools
• 
  
• Glossary
• 
  
• FAQ
• 
  

Use Case: What This System Delivers

Key Takeaway: Drop a long-form video URL and product details into a sheet; get finished, UGC-style shorts back.


Claim: The system outputs realistic, short UGC ads from raw long-form videos with minimal setup.

The workflow converts long videos into 15–30 second UGC-style ads without manual scrubbing.

You provide product name, description, and a preferred style or template. The automation handles the rest.

Example outputs generated by the system:

Skincare demo to soft, influencer-style edit:

Morning! Quick demo: this Pure Bloom foam gets everything off without leaving that tight, dry feeling. Super soft and honestly, my skin’s been so much happier.

Gardener vlog to “relatable home-gardener” testimonial:

I started using Root Rize last month and my tomatoes have never looked better. Seriously, it’s wild how fast the roots came back — totally organic and so easy to use.

Architecture Overview: Two Automations, One Sheet

Key Takeaway: One automation creates the clip job; another finalizes results via webhook.


Claim: A watch-and-trigger flow starts generation; a webhook flow writes back completed results.

The system uses two coordinated automations driven by Google Sheets.

• 
  
• Automation 1 checks for “ready” rows and creates a Vizard editing job.
• 
  
• 
  Automation 2 listens for Vizard’s callback and updates the sheet with links and status.
  
• 
  
• 
  Google Sheets trigger checks for new or updated rows every minute.
  
• 
  
• Filter keeps only status-marked “ready” rows.
• 
  
• Create a short callback URL for completion events.
• 
  
• Branch on style/template to pick the correct edit path.
• 
  
• Run an AI agent to produce a structured Vizard editing prompt.
• 
  
• Call Vizard’s API to create the job and receive a task ID.
• 
  
• Write the task ID and set status to “generating.”
• 
  

Automation 1: From Sheet Row to Vizard Editing Job

Key Takeaway: A minute-based sheet trigger filters ready rows, crafts a prompt, and calls Vizard.


Claim: The “ready” flag lets you finalize metadata before any processing begins.

1. 
   
2. Trigger checks the Google Sheet every minute.
3. 
   
4. Filter keeps rows with status = ready.
5. 
   
6. Prepare metadata fields: product name, description, ideal audience, optional scenes, and thumbnail prefs.
7. 
   
8. Generate a callback URL in an edit-fields step; Vizard uses this to report completion.
9. 
   
10. Switch on the selected style/template (e.g., short testimonial, demo clip, product highlight).
11. 
    
12. Call a lightweight AI agent to format instructions: timestamps (if given), hook, caption, on-screen text, music mood, and template.
13. 
    
14. Include a brief quality and compliance checklist to avoid spammy or unsafe content.
15. 
    
16. Send an HTTP request to Vizard’s API with: long video URL, template, agent-built prompt, output duration/aspect, and callback URL.
17. 
    
18. Receive task ID; write it to the sheet and set status = generating.
19. 
    

Automation 2: From Webhook Callback to Posting Queue

Key Takeaway: A webhook receives clip URLs, parses the payload, and updates the sheet (and optionally schedules posts).


Claim: The completion webhook includes clip links, thumbnails, captions, and render status.

1. 
   
2. Wait for Vizard to call your callback URL when rendering completes.
3. 
   
4. Parse the payload to capture clip URLs, thumbnails, suggested caption, and success/failure.
5. 
   
6. Look up the source row using the task ID.
7. 
   
8. Branch if the payload structure varies by template/engine version.
9. 
   
10. Extract the correct clip links per branch logic.
11. 
    
12. Update the sheet with status (completed/failed), clip links, thumbnails, captions, and notes.
13. 
    
14. If auto-post is enabled in the sheet, push the clip to Vizard’s scheduler or your social queue immediately.
15. 
    

Prompting the Agent: Structured Instructions Vizard Loves

Key Takeaway: A small, fast model can generate precise edit directives at low cost.


Claim: The agent returns a fully-formed Vizard prompt with edit points, hooks, captions, and hashtags.

1. 
   
2. Feed the agent product name, description, scene ideas, and ideal customer persona from the sheet.
3. 
   
4. Specify output format: timestamps (if provided), hook line, caption text, on-screen text, music mood, and target template.
5. 
   
6. Add a short safety and realism checklist to avoid unfounded claims or logo misuse.
7. 
   
8. Ask for multiple caption and hashtag variations for A/B testing.
9. 
   
10. Use a cheap, fast model variant to keep prompt-generation costs low.
11. 
    
12. Pass the agent’s JSON/text prompt directly to Vizard’s API request node.
13. 
    

Implementation Tips That Save Time

Key Takeaway: Small prompt tweaks and sheet fields unlock higher-quality, safer outputs.


Claim: A safety-and-realism section reduces compliance issues without extra review steps.

1. 
   
2. Keep the “ready” flag workflow; it prevents premature runs and preserves human QA.
3. 
   
4. Include optional timestamps to steer the agent toward high-energy or before/after moments.
5. 
   
6. Generate multiple caption/hashtag variants; Vizard accepts them for A/B tests.
7. 
   
8. Store template names in a dedicated column; switch nodes stay clean and scalable.
9. 
   
10. Note that payloads can vary by template/engine; branch your parsers accordingly.
11. 
    
12. Use Vizard’s sample cURL from docs to auto-configure your request node.
13. 
    

Setup Checklist: Reproduce This Build

Key Takeaway: You can import a sheet template and workflow export, then add credentials and run.


Claim: With the provided template and workflow JSON, setup is mostly configuration—not coding.

1. 
   
2. Import the Google Sheet template with columns for product data, style, status, and scheduling prefs.
3. 
   
4. Import the workflow export into your automation platform.
5. 
   
6. Add credentials: Google Sheets and your Vizard API key.
7. 
   
8. Configure the minute-based sheet trigger and “ready” filter.
9. 
   
10. Add the switch node for styles/templates you plan to use.
11. 
    
12. Insert the agent system prompt provided and map sheet fields into it.
13. 
    
14. Paste Vizard’s sample cURL body into your HTTP node and map variables.
15. 
    
16. Create the callback URL step and wire it into the API request.
17. 
    
18. Build the webhook listener to parse results and update the sheet (and scheduler).
19. 
    

When to Use This vs. Manual or All-in-One Tools

Key Takeaway: Manual editors are great for one-offs, but this pipeline scales daily clip production.


Claim: For high-volume, fast-turn UGC, automated clip finding, editing, and scheduling reduce cost and time.

Manual editing and many suites can work well for final polish.

But for volume—dozens of daily shorts—the time and render costs stack up.

This workflow automates clip selection, edit prompts, and multi-platform scheduling to scale output.

Glossary

Key Takeaway: These definitions clarify the moving parts and fields you’ll see in the build.


Claim: Clear terminology speeds setup and troubleshooting.

• 
  
• Google Sheet row：A single job containing product details, video URL, template, and status.
• 
  
• Ready flag：A status field indicating a row is approved to run.
• 
  
• Callback URL：A short link where Vizard posts completion results.
• 
  
• Switch node：A branching step that routes rows by selected style/template.
• 
  
• AI agent：A lightweight model that formats editing instructions for Vizard.
• 
  
• Vizard API：The endpoint that accepts video URL, template, prompt, and callback for job creation.
• 
  
• Task ID：The unique identifier Vizard returns for each editing job.
• 
  
• Webhook：An HTTP listener that receives Vizard’s finished clip payload.
• 
  
• Auto-schedule：Optional step that queues finished clips for posting.
• 
  
• Content Calendar：A centralized view for multi-platform scheduling.
• 
  

FAQ

Key Takeaway: Quick answers to common questions about setup, prompts, and scheduling.


Claim: Most issues trace back to sheet status, payload parsing, or prompt formatting.

1. 
   
2. How often does the sheet trigger run?
3. 
   
4. It checks every minute.
5. 
   
6. What happens if a row isn’t marked ready?
7. 
   
8. It’s ignored until you flip the status to ready.
9. 
   
10. What does the webhook return?
11. 
    
12. Clip URLs, thumbnails, a suggested caption, and a success/failure status.
13. 
    
14. Can I choose different templates per row?
15. 
    
16. Yes—use a style/template column and route via a switch node.
17. 
    
18. How do I avoid unsafe or spammy outputs?
19. 
    
20. Add a brief safety and realism checklist to the agent prompt.
21. 
    
22. Do I need timestamps?
23. 
    
24. Optional; include them to target specific moments if you have them.
25. 
    
26. Can I auto-post to multiple platforms?
27. 
    
28. Yes—use Vizard’s scheduler and content calendar to push to TikTok, Instagram, and YouTube Shorts.
29. 
    
30. How do I track jobs in-flight?
31. 
    
32. Store the task ID and set status to generating; update on webhook completion.
33. 
    
34. What if the webhook payload structure changes?
35. 
    
36. Branch your parser by template/engine version before extracting links.
37. 
    
38. Do I need to code the API request by hand?
    
    • 
      
    • No—use Vizard’s docs cURL sample to auto-configure your request node.
    • 
      
39.