Claude YouTube Automation: Schedule Shorts with Claude Cowork

Claude YouTube automation is useful when your Shorts already exist and the repetitive work is choosing the next video, writing the metadata, and keeping the publishing queue moving.

This YouTube Shorts automation is about distributing finished videos. It does not create a faceless channel, write scripts, or generate every Short from scratch.

The workflow in this guide uses two YouTube content folders for Pantry AI. Claude Cowork alternates between recipe Shorts and product-demo Shorts, then prepares each video for the Pantry AI YouTube channel.

Claude handles the instructions and file-selection logic. Genviral's MCP server gives Claude permissioned access to the media library, connected YouTube account, and scheduling tools.

This is not a claim that the recorded setup was fully autonomous. The scheduled YouTube task was still failing during the walkthrough, which makes the testing and confirmation steps below part of the setup.

What this Claude YouTube automation does

You give Cowork the Genviral workspace, two media folders, exact filename patterns, destination channel, metadata examples, and posting sequence.

For the Pantry AI workflow, one post comes from the recipe folder and the next comes from the product-demo folder. The files are numbered, so Cowork can move through both YouTube queues in order.

The same media is reused from Genviral instead of uploaded again for every post. That keeps the library clean and avoids creating a new duplicate each time the task runs.

Cowork then writes a YouTube-specific title, description, and hashtags for the selected Short. The post can be scheduled ahead so you have time to review it in the Genviral queue.

Why YouTube needs its own content rules

YouTube viewers see the title before they decide whether to watch. That makes the title part of the content system, not a caption added after the video is finished.

A YouTube Short needs a clear title that describes the video before the description adds context. The hashtags, call to action, and wording should follow examples from the same channel.

This setup starts with finished YouTube videos, so its harder problems are inventory and metadata. Cowork needs to know which Short comes next and how that channel writes about it.

Keep those YouTube rules in their own Cowork project. A separate project stops unrelated content instructions from changing the title format, folder sequence, or destination channel.

What you need

Prepare these six things before you build the task:

1. A Claude account with custom connector access
2. A paid Claude plan for Cowork projects and scheduled tasks
3. A Genviral account
4. A YouTube channel connected in Genviral
5. One or more named folders containing finished vertical videos
6. About 10 real YouTube titles, descriptions, and hashtag sets

Post manually for one or two weeks if you do not know what your YouTube metadata should look like yet. Automation cannot recover a format you have not decided.

Step 1: Add Genviral as a Claude connector

Open Claude, go to Customize, and choose Connectors. Add a custom connector with this remote MCP endpoint:

https://mcp.genviral.io/mcp

Name it Genviral, continue through the setup, and approve the OAuth connection.

Anthropic's connector documentation explains how custom remote MCP connectors work.

Only connect servers you trust. A connector that can create posts can take real actions on your social accounts through the permissions you approve.

Step 2: Approve the permissions this task needs

Open Manage Connectors, select Genviral, and review the tools available to Claude.

This workflow needs access to the relevant workspaces, folders, media files, connected accounts, and post-scheduling action. Enable upload access only when Cowork must bring in a file that is not already in Genviral.

The video enables every available tool because the wider project also creates content. You do not need to copy that permission set for a task that only schedules finished Shorts.

Give the project the smallest useful set of permissions, then expand it when a specific step requires more access.

Step 3: Connect and confirm the YouTube channel

Open Social Posts, choose Manage Accounts, and connect the YouTube channel you want to use.

If you have more than one Genviral workspace, switch to the correct workspace first. The walkthrough targets the Pantry AI workspace and its Pantry AI YouTube channel.

Ask Claude to list the YouTube destinations it can see. Confirm the workspace and channel name before you let it create the first post.

Do this before you debug folders or metadata. If Claude cannot see the destination, the rest of the task cannot work.

Step 4: Create a dedicated Cowork project

Create one Cowork project for the YouTube workflow. Keep the connector instructions, destination channel, folder names, filename patterns, metadata examples, and scheduling rules inside it.

If you already scheduled one correct YouTube Short in Claude, ask it to summarize that setup as a handoff. Paste the handoff into the Cowork project before describing the recurring sequence.

The handoff preserves the workspace, channel, folder, and connector details that you have already debugged. Cowork can use those facts without searching for the same setup again.

Reuse the setup facts, but rewrite the output rules for YouTube.

Step 5: Organize the YouTube content folders

Put finished YouTube videos into folders with names that explain the content inside them. The example below separates recipe Shorts from product-demo Shorts.

Number the files so Cowork can follow a stable order:

Pantry AI YouTube Recipes/
├── YT-R-01-hair-growth-recipe.mp4
├── YT-R-02-kimbap-recipe.mp4
└── YT-R-03-pesto-pasta.mp4
 
Pantry AI YouTube Product Demos/
├── YT-D-01-scan-ingredients.mp4
├── YT-D-02-build-a-meal.mp4
└── YT-D-03-save-a-recipe.mp4

The recorded library had about 35 numbered files. Cowork initially found the folders but missed the videos because the instruction did not include enough detail about their names.

Give it one or two exact filenames and the prefixes it should search for. Clear filenames are part of the automation contract.

Step 6: Confirm the inventory before posting

Ask Cowork to return the files it found before it creates a post. The response should include the folder, filename, sequence number, and media reference it plans to reuse.

Do not accept a general message saying the folder was found. In the walkthrough, the folder existed while the first file search still returned the wrong result.

Use a prompt like this:

Use the Genviral connector in the Pantry AI workspace.
 
Find the folders named Pantry AI YouTube Recipes and Pantry AI YouTube Product
Demos. Search for files beginning with YT-R- and YT-D-. Show me five filenames
from each folder in sequence. Do not create or schedule a post yet.

The preview gives you a cheap place to correct a folder name or search pattern before it affects the channel.

Step 7: Reuse existing media without creating duplicates

Tell Cowork to use the existing Genviral media reference for each Short. It should not upload another copy when the selected video is already in the library.

This is safer than giving the task a raw storage URL and assuming it will remain valid forever. Let the connector return and use the media reference supported by the posting tool.

After the first run, open the media library and confirm that one scheduled post did not create another copy of the original video.

Step 8: Teach Cowork your YouTube metadata

Paste about 10 titles, descriptions, and hashtag sets from Shorts you posted manually. Pick examples you would publish again, not every post you have ever made.

Tell Cowork which parts are fixed and which parts may change. Your instructions should cover:

• title length and capitalization
• whether the title names the recipe, result, or problem
• description structure and call to action
• hashtags to include or avoid
• claims the task must not invent
• whether reused videos need a new YouTube angle

The walkthrough calls out robotic AI writing as a problem. Real examples give Cowork a pattern it can reproduce instead of asking it to guess what human or engaging means.

Step 9: Define the alternating sequence

Write the folder rule as an explicit sequence. For example, select the next unused YT-R- file, then the next unused YT-D- file, and repeat.

Tell Cowork to rescan both folders before each run so newly added videos enter the inventory. It should preserve the current position rather than starting again when a new file appears.

Also define what happens when one folder ends before the other. The task can continue with the remaining folder, pause for review, or restart only after both pools are exhausted.

Do not leave that decision implicit. An unclear end-of-inventory rule is how the same Short gets selected again by mistake.

Step 10: Schedule one reviewed Short

Before creating a recurring task, schedule one Short far enough ahead to inspect it. Include the workspace, folder, filename, YouTube channel, title rules, publish time, and IANA time zone.

You can adapt this prompt:

Use the Genviral connector and the Pantry AI workspace.
 
Select YT-R-01 from the Pantry AI YouTube Recipes folder and schedule it for
the Pantry AI YouTube channel tomorrow at 10:00 AM America/New_York.
 
Write a YouTube-specific title and description using the examples in this
project. Reuse the existing media reference. Do not upload a duplicate.
 
Before finishing, show me the channel, filename, title, description, hashtags,
scheduled time, and status returned by Genviral.

Open the post in Genviral and review the selected video, title, description, hashtags, channel, date, and displayed time.

If you only need this reviewable calendar workflow, the YouTube Scheduler is the simpler starting point. Add Cowork when you need the file-selection and metadata decisions too.

Step 11: Create the recurring Cowork task

Once the reviewed Short is correct, create the recurring task in Cowork. Anthropic explains the current controls in its scheduled tasks guide.

The walkthrough uses two posts per day, one in the morning and one in the evening. That is the Pantry AI cadence shown in the video, not a universal recommendation for YouTube Shorts.

Start with a cadence you have already handled manually. Schedule each Short ahead of its publish time during the first week so a bad title or wrong file can still be corrected.

Ask for a confirmation after every run. It should include the selected filename, YouTube folder, channel, scheduled time, title, status returned by Genviral, and the next file in the sequence.

What was not working in the recorded setup

The scheduled YouTube task did not appear to work reliably at the time of recording. The walkthrough shows the intended recurring setup, but it does not show a completed unattended YouTube run followed by verified publication.

The workflow is still useful, but you need to validate each stage instead of calling the whole system successful when Cowork finishes a task.

Track these states separately:

1. Cowork ran the scheduled task
2. Genviral accepted or scheduled the Short
3. YouTube published the Short
4. Claude independently confirmed the published result

A Cowork confirmation proves the first state only unless it includes evidence from the later stages. Check the Genviral calendar and the YouTube channel while you validate the recurring setup.

If a run fails, preserve the filename and sequence position. Retry the failed Short instead of advancing the inventory or starting the whole sequence again.

Reusing Shorts responsibly

The Pantry AI workflow reuses videos that Fekri and Viktor own and have approved for the YouTube channel. It cycles through that library rather than creating a new asset for every upload.

That does not mean every channel should repost the same inventory forever. Watch for audience fatigue, update weak metadata, and add new videos before the account becomes a loop people can predict.

YouTube also reviews repetitive and reused content when it evaluates monetization. Read YouTube's channel monetization policies before scaling a recycled-content workflow.

Keep the rights to every video, avoid low-value mass duplication, and make sure the channel gives viewers a reason to watch the content on YouTube.

Can Claude post directly to YouTube?

Claude needs a connected tool that can perform the publishing action. In this workflow, Genviral provides the tool through MCP and manages the YouTube account connection.

You do not give Claude your YouTube password. You authorize the channel in Genviral and approve the connector permissions Claude may use.

Can Claude understand every video in the folder?

In this workflow, Cowork relied on folder names, filenames, metadata, and the instructions in the project. Do not assume it watched every video because it can list the files.

Use descriptive filenames and add a one-sentence note when the correct title depends on a detail the filename does not contain.

Can Cowork run while my computer is off?

Connector-based tasks and files saved to your Claude account can run while your computer is asleep.

If the task needs local files or desktop apps, the Claude Desktop connection and computer need to remain available. Test the exact task before leaving it unattended.

Can I generate the Shorts instead?

Yes. Claude can ask a connected service such as Genviral to generate an image or video with an external model, then schedule the result.

The recorded workflow uses finished Pantry AI videos because the goal is distribution. Start there if you already have a useful inventory, then add generation as a separate process.

Getting started

Use this order for your first Claude YouTube automation:

1. Add the Genviral MCP connector to Claude
2. Approve the workspace, media, account, and scheduling permissions you need
3. Connect and confirm the YouTube channel
4. Create a dedicated Cowork project
5. Add named folders and ordered filenames
6. Ask Cowork to preview the inventory without posting
7. Tell it to reuse existing media references
8. Paste about 10 real YouTube metadata examples
9. Define the alternating and end-of-inventory rules
10. Schedule one Short ahead for review
11. Verify the post in Genviral and on YouTube
12. Create the recurring task and keep confirmations enabled

The OpenClaw YouTube guide is a better fit when you want an API-key-based agent with its own posting and analytics loop.

The Hermes Agent YouTube guide covers the same folder, logging, and confirmation problems for an agent that runs in a messaging channel.

Related guides

• How to Connect Claude to Instagram and Automate Posting
• Claude Facebook Automation with Claude Cowork
• How to Automate YouTube Posting with OpenClaw
• How to Automate YouTube Shorts Posting with Hermes Agent
• YouTube Scheduler
• Best Social Media APIs for Posting and Automation