Goals
- Automatically detect new YouTube uploads on a specific channel
- Upload and index each new video in VideoDB and tag it with a target label (e.g.,
YT summary) - Generate a Markdown-formatted summary of the indexed video using VideoDB
- Create a new Notion page containing the summary and relevant metadata for easy storage and reference
Prerequisites
- A Zapier account to create and manage the two workflows (zaps)
- Access to VideoDB with an active API key
- A Notion account and a parent Notion page (e.g., YouTube video summaries) where new pages will be created
- The YouTube channel ID (Note: YouTube typically displays channel usernames/handles like
@channelnameinstead of the actual channel ID. Use a converter tool such as StreamWeasels YouTube Channel ID Converter to convert the username to a channel ID) - Basic familiarity with Zapier actions (triggers, async jobs, delay/flow control) and dynamic field mapping
Workflow 1: YouTube Upload to VideoDB Upload and Index
Step 1: Trigger Setup (YouTube)
- Create a new Zap with the trigger New Video in Channel (YouTube)
- Provide the correct YouTube channel ID. Note that YouTube displays channel usernames/handles (like
@channelname) instead of the actual channel ID. Use a converter tool such as StreamWeasels YouTube Channel ID Converter to get the channel ID from the username. - Test the trigger to ensure Zapier can fetch a recent video from the channel
Step 2: Upload and Index with VideoDB
- Add a Zapier action: VideoDB - Upload an Index job
- Authenticate using your VideoDB API key (retrieve from the VideoDB console / Access Control)
- Map fields: video title, video URL (YouTube link), and a descriptive prompt (e.g., “informative video - summarize accordingly”)
- Set a target label (e.g.,
YT summary) so VideoDB knows which downstream workflow(s) to trigger when indexing completes - Test the step and confirm VideoDB returns a Job ID (indexing is asynchronous)
Step 3: Publish Workflow 1
Activate (publish) the zap so that every new upload on the specified channel triggers this upload/index job automatically.Workflow 2: VideoDB Done to Summarize to Notion Page
Step 1: Trigger Setup (VideoDB)
- Create a second Zap with trigger New video uploaded & indexed from VideoDB
- Filter by the same target label (
YT summary) to ensure only relevant indexing jobs trigger this workflow - Test to obtain a sample payload (includes
video_id, stream/download URLs, length, etc.)
Step 2: Request Video Summarization
- Add an action: VideoDB - Summarize Video
- Use the dynamic
video_idfrom the VideoDB trigger (do not use a static video id) - Provide a summarization prompt tailored for Notion, for example: “Summarize the technical content of this video. Provide the final notes in Markdown format suitable for Notion.”
- Run the step - VideoDB returns a summary job id because summarization is asynchronous
Step 3: Wait / Poll for Completion
- Insert a Zapier Delay (Flow Control) - e.g., Delay for 3 minutes - to allow time for the async summarization job
- After the delay, add VideoDB - Check Job Status and pass the summary job id (dynamic)
- Test the check step; once complete it will return the summarized text (already formatted per the prompt)
Step 4: Create Notion Page
- Add an action: Notion - Create Page under the parent page YouTube video summaries
- Authenticate and grant Zapier access to that Notion page
- Configure the page:
- Title: map dynamically from the original YouTube upload (video name from the first trigger)
- Body/content: use the Markdown summary returned by the VideoDB Check Job Status step (Notion supports Markdown import)
- Optionally map metadata (video URL, video length, VideoDB job id) into properties or content for traceability
- Test creating the page to confirm formatting and placement are correct