Skip to main content

Social Media Automation

Connect a YouTube channel and upload a video with explicit audience settings

Authorise the correct channel, choose privacy and made-for-kids designation, and verify the uploaded video in YouTube Studio.

Reviewed 13 November 20262 minute read5 steps

Where to start
Social accounts → YouTube; Configuration where applicable

Fields and options

Access needed
Manage connections; administrator for app credentials; Create posts + Publish posts for a live test
Requested OAuth permissions
https://www.googleapis.com/auth/youtube.upload and https://www.googleapis.com/auth/youtube.readonly. These are the scopes requested by the current adapter; provider products/review must permit them.
Destination and scope
Google testing-mode authorisations can have limited refresh-token lifetimes. Verification, quotas and YouTube API project/audit restrictions remain provider controls; a saved OAuth client is not approval.
Publishing format
Attach a supported video, provide the required title up to 100 characters, choose Private/Unlisted/Public and explicitly choose whether it is made for kids. Start an authorised sandbox test as Private.

Before you begin

An organisation-owned Google Cloud project with YouTube Data API enabled, OAuth branding/audience configured, a Web application OAuth client and an eligible test Google account/channel.

Follow these steps

  1. In Configuration, copy the YouTube application callback into the matching provider app. Save its matching ID and secret with Save encrypted credentials. Leave direct publishing locked during connection setup.
  2. Choose YouTube Connect, complete Google consent for the correct account/channel and verify the discovered channel. Include the test user when the OAuth app is in Testing.
  3. In Social accounts, choose Verify connection and compare the account or destination identity with the intended test account.
  4. Attach a supported video, provide the required title up to 100 characters, choose Private/Unlisted/Public and explicitly choose whether it is made for kids. Start an authorised sandbox test as Private.
  5. When a controlled test is authorised and the direct gate is enabled, select only this destination, choose Post Now once and inspect its existing receipt.

Check the result

Open YouTube Studio and verify the channel, video processing, selected privacy and audience designation. Upload acceptance alone does not prove playable final processing. Match the actual provider outcome to the destination receipt, remote reference and intended visibility.

If something does not look right

If authorisation expires, check testing status and reconnect through Google consent. If upload is restricted, inspect the API project’s current quota, verification/audit state and provider error. Do not repeat Post Now after an ambiguous result until the original provider outcome has been checked.

Fields, rules and limits

  • Saving credentials or passing connection verification does not prove that a live publication succeeded.
  • Use a dedicated test destination and the most restrictive appropriate visibility. Provider consent, app review and organisational approvals remain separate requirements.

Questions and answers

Does a connected account mean publishing is approved?

No. Connection identity, app publishing entitlement, content eligibility and the separate direct-publishing gate are independent checks.

What is a complete first test?

Official consent, correct destination discovery, successful verification, one deliberate test publication, a destination receipt and direct verification in the actual provider account.

Related technical reference: Britixo's detailed product guide (opens in a new tab). The screens available to you depend on your configured modules, company and permissions.

Contact the Proplix team if you need help with your setup. Include the page or record reference and a description of the issue; leave passwords and private access tokens out of the message.