Connecting your YouTube channel

You will create a Google Cloud project of your own and connect it here. It is the longest part of setting up, and you only ever do it once.

About 10 minutes · you need the Google account that owns the channel

Why you and not us. YouTube gives each app 10,000 quota units a day, and one upload costs 1,600 — six uploads a day for everyone combined. If we shared a single connection, one busy customer would use up the day for all the others. Your own project means your allowance is yours: about six uploads a day, for you alone, which is well beyond what any plan here uses.

1 Create a project

Go to console.cloud.google.com/projectcreate, sign in with the Google account that owns your YouTube channel, and give the project a name — My Channel Publishing is fine. Leave the organisation as it is and click Create.

It costs nothing. This part of Google Cloud has no charge and no card is asked for.

2 Turn on the YouTube Data API

With that project selected, open the YouTube Data API v3 page and click Enable. This is what lets the project upload on your behalf.

3 Fill in the consent screen

Go to APIs & Services → OAuth consent screen. Choose External and continue. You only need three things:

App name — anything; you are the only person who will see it
User support email — your own address
Developer contact — the same address

Save and continue past the Scopes page without adding any. On Test users, click Add users and add your own Google address.

The step people miss. If you do not add yourself as a test user, Google refuses the connection later with "app has not completed verification". Adding yourself is what makes it work, and it is easy to skip past.

4 Create the credentials

Go to APIs & Services → Credentials → Create Credentials → OAuth client ID.

Application type: Web application
Name: anything
Authorised redirect URIs → Add URI, and paste this exactly:

https://videocadence.com/api/connections/youtube/callback

Click Create. Google shows a Client ID and a Client secret — keep that dialog open for the next step.

The redirect URI must match character for character, including https and with no trailing slash. A single character out and Google returns "redirect_uri_mismatch", which is the most common thing that goes wrong here.

5 Paste them into Videocadence

In Videocadence open Settings → Connections, choose Connect YouTube, and paste the Client ID and Client secret. Then click connect and pick your channel in Google's window.

Google will warn that the app is not verified. That is expected — the app is yours, made minutes ago, and Google only verifies apps that ask for other people's data. Choose Advanced → Go to (your app name) and continue.

6 Check it worked

The Connections page should show your channel name and a green status. Make one video and schedule it a few minutes out; when it appears on your channel as private and then goes public at the scheduled minute, everything is wired correctly.

Your credentials stay yours. The client secret and the access token are encrypted before they are stored, with a key kept apart from the database. Disconnect at any time from the Connections page and we stop publishing immediately.

7 When something goes wrong

redirect_uri_mismatch — the URI in step 4 does not match exactly. Re-copy it.
App has not completed verification — you are not on the test users list in step 3.
Access blocked / app is being tested — same cause; add your address as a test user.
quotaExceeded — more than about six uploads that day on that project. It resets at midnight Pacific time.
Channel not listed — you signed in with a Google account that does not own the channel. Sign out and use the owning account.

If none of that fits, email support@videocadence.com with the step number and what you saw. Do not send the client secret.