Muse Task HubUnofficial guide
Not affiliated with Muse

Work · Community report

Prepare a YouTube upload workflow

@Tharun1 says Muse wrote YouTube API code for uploads and scheduling, clicked through the Google console setup itself and even passed CAPTCHAs, and @itskevingraham says Muse found which videos they had not yet cross-posted. This page sets up a YouTube upload workflow that starts with a private test video.

What you can get

Illustration — suggested task flow, not an execution result
  1. Prepare

    A channel you own and a video you may publish

  2. Ask and review

    Create or choose a Google Cloud project, enable the YouTube Data API v3, set up the OAuth consent screen and create an OAuth client.

  3. Check the result

    A reviewed upload-and-scheduling implementation with a controlled test and explicit publication approval.

The source case

In the same multi-task post, @Tharun1 says Muse wrote a YouTube API workflow for uploads and scheduling and navigated the Google console without manual setup. They also claim it passed CAPTCHAs. The capture supplies no code, OAuth configuration, upload or schedule receipt; it does not justify bypassing verification or publishing without approval. A further X post from @itskevingraham, replying to another user's thread, says Muse scraped which of their videos had not yet been cross-posted to YouTube, saving about two hours. The post does not say how the check was done or whether any upload was actually scheduled.

A public report by someone outside this library. Not independently reproduced here.

From the source

Source excerpt

3) I asked it to write a YouTube API for uploads and scheduling. I didn't have to set up anything in the Google console; it just clicked through the entire flow and even passed CAPTCHAs.

@Tharun1 · Read it at the source · checked

Source excerpt

@flexiblefoodie @Muse Mine scraped which vids I haven’t cross posted to YouTube yet, saved me a good 2 hours today

@itskevingraham · Read it at the source · checked

Quoted from the original posts. Not written by this guide, and not a result produced here.

Suggested prompt

Bring A channel you own and a video you may publish, Title, description, audience setting and intended schedule, An approved OAuth setup and test plan. Source community report, checked 2026-10-09.

Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.

What you need

You supply

  • A channel you own and a video you may publish
  • Title, description, audience setting and intended schedule
  • An approved OAuth setup and test plan

How to try it

Editorial, not from the source

  1. Create or choose a Google Cloud project, enable the YouTube Data API v3, set up the OAuth consent screen and create an OAuth client.
  2. Authorise with the upload scope only, and complete any CAPTCHA or verification prompt yourself.
  3. Upload a test video as private and check title, description, audience setting and thumbnail in YouTube Studio.
  4. Schedule it by keeping it private with a publish time, then confirm Studio shows the time you meant in your timezone.
  5. Approve each real video and publish time, and save the video ID and status the API returns.
  6. Optionally, have the agent list videos in your library that are not yet on the channel before uploading anything.

What the two reports say

In item three of a longer post, @Tharun1 says they asked Muse to write a YouTube API for uploads and scheduling, did not have to set anything up in the Google console, and that Muse clicked through the entire flow and even passed CAPTCHAs. @itskevingraham, replying to another user, says their Muse scraped which of their videos had not yet been cross-posted to YouTube and saved them a good two hours.

Neither post shows the code, the permissions granted, or a video that was actually uploaded or scheduled. The CAPTCHA claim is the author's; this page does not recommend letting an agent handle checks meant for you.

The Google side of the setup

Uploads go through the YouTube Data API's videos.insert call, authorised with OAuth for your Google account. According to Google's documentation, videos uploaded through an unverified API project created after July 2020 are restricted to private viewing until the project passes YouTube's API audit, so a script can work perfectly and still produce videos nobody else can see. While the consent screen is in testing mode, refresh tokens also expire after seven days, which looks like a script that stops working after a week.

Uploads use a large share of the default daily API quota, so a workflow that pushes a backlog will hit the limit quickly. Check the quota page in the Cloud console before planning a batch.

Scheduling, and where you stay in the loop

The API schedules a video by uploading it as private with a publishAt time; YouTube then makes it public at that moment. The time is in UTC, so confirm in YouTube Studio that it shows the hour you intended, and remember the made-for-kids setting must be declared for every upload.

CAPTCHAs, phone codes and 2-step prompts exist to confirm a person is present. Hand those to yourself, and approve each video and publish time before anything becomes public.

Open Muse to try it. That is the product's own site; this guide is not part of it.

Limits and confirmation points

Limits to confirm

  • API code, OAuth scopes, test upload, scheduled-video identifier and verification method are missing.
  • No publicly uploaded or successfully scheduled video is demonstrated.
  • This is an attributed community report, not reproduced by this guide. The suggested workflow and checks are editorial guidance, not a recovered conversation or guaranteed product capability.

If it goes wrong

Editorial, not from the source

Every uploaded video is locked to private
The API project is likely unverified. Apply for YouTube's API audit, or publish manually from Studio in the meantime.
The script stops authorising after about a week
Refresh tokens expire after seven days while the consent screen is in testing mode. Move the app out of testing or reauthorise.
The video went live at the wrong hour
publishAt is in UTC. Convert from your timezone and check the scheduled time in Studio before approving.

Common questions

Can Muse upload and schedule YouTube videos for me?

@Tharun1 says Muse wrote the API workflow and set up the console. No uploaded or scheduled video is shown, and this guide has not reproduced it.

Why are my API uploads stuck on private?

Google restricts videos uploaded through unverified API projects to private until the project passes YouTube's API audit.

How do I schedule an upload through the API?

Upload the video as private and set publishAt to the release time in UTC. Check the scheduled time in YouTube Studio afterwards.

Can it find which videos I have not posted to YouTube yet?

@itskevingraham says Muse did this for them and saved about two hours. The post does not say how the check was done.

Should the agent solve CAPTCHAs during setup?

No. The source claims it did, but those checks are meant for you. Have the agent stop and hand them over.

Next

More in Work

Every work task

Similar tasks

Get recurring task recommendations — ask your own agent to check for relevant updates.