YouTube
An active YouTube channel with permission to upload videos
Ownership and availability
You own the YouTube channel. Obelo manages Google OAuth and uploads only approved videos to the selected channel.
Start in Settings → Integrations and check the provider’s current status. This guide describes the configured setup path, not a guarantee of production enablement. Provider approval, plan access and resource permissions still apply.
Before you connect
- A YouTube channel exists under the connecting Google account or Brand Account
- The channel can upload videos and has no blocking restrictions
- An Obelo workspace owner or admin completes Google OAuth
Connect an existing account
- Open the provider in Settings → Integrations for the intended website.
- Sign in to the Google account that owns or manages the channel
- Choose the correct channel identity and grant YouTube upload access
- Return to Obelo and verify the selected channel
If you need a new resource
- Create a YouTube channel or Brand Account channel
- Complete channel verification, branding, and default upload settings
- Confirm manual uploads work before authorizing Obelo
Permissions to check
- YouTube upload permission is required to create video resources
- Scheduled or public publishing may be restricted until Google's app verification and channel checks are satisfied
Verify and troubleshoot
After the channel is active and verified, return and reconnect.
Google returned no usable YouTube channel. Create a channel, switch to the correct Brand Account, or confirm upload eligibility.
Confirm the selected account or resource and inspect the verification or sync result. A saved connection is not proof that an import or publication has completed. Test the intended workflow with an appropriately reviewed item.
Disconnect or change access
Use the provider’s management controls in Obelo to disconnect when supported. Revoke the grant or rotate a dedicated credential at the provider if access must end immediately. Review already-imported data separately; disconnection does not remove content already published elsewhere.
Something unclear or out of date?
Suggest a correction