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.
Use these steps in your selected Pixie CRM company workspace. The module, dependent tools and actions available to you follow its configuration and your permissions.
Social accounts → YouTube; Configuration where applicable
PermissionManage connections; administrator for app credentials; Create posts + Publish posts for a live test
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
- 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.
- 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.
- In Social accounts, choose Verify connection and compare the account or destination identity with the intended test account.
- 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.
- 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.
Fields and options
- 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.
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.
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.
Common questions
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.