Bring your own key is available on plans that include it. Velaro can index YouTube channels and pull video transcripts into your bot's knowledge index. With your own Google service account credentials, YouTube ingestion runs on your own Google Cloud project: your quota, your project, your audit trail. You will be paying your provider directly.

If your plan does not include bring your own key, the YouTube Channel Search panel still works with a daily search allowance. Ask Moshky or submit a ticket from the Support page to add bring your own key to your plan.

Setup (5 minutes)

Step 1 — Create or pick a Google Cloud project

Go to console.cloud.google.com. If you already have a project you use for Google APIs, use that. Otherwise click the project picker at the top and New Project, give it a name like velaro-youtube, and create it. No billing account is required for the YouTube Data API free tier.

Step 2 — Enable the YouTube Data API v3

In the left sidebar go to APIs & Services → Library. Search for YouTube Data API v3, click it, and click Enable. Wait a few seconds for it to activate.

Step 3 — Create a service account

Still in the Cloud Console, go to IAM & Admin → Service Accounts → + Create service account. Give it a name like velaro-youtube-reader. You can skip the optional "Grant this service account access to project" step — the YouTube Data API doesn't require any IAM role. Click Done.

Step 4 — Generate a JSON key

Click the new service account in the list, go to the Keys tab, click Add Key → Create new key → JSON → Create. Your browser will download a JSON file containing the credentials. Open that file in any text editor and copy its full contents.

Step 5 — Paste it into Velaro

In Velaro go to Account → AI Provider → YouTube Data API. Click Add key, paste the entire JSON into the textarea, and click Save. The card status changes from "Not configured" to "Connected".

How quota works on your own key

A fresh Google Cloud project has 10,000 YouTube Data API units per day. That's roughly 100 channel searches per day. If you need more, in the Cloud Console go to APIs & Services → YouTube Data API v3 → Quotas and click Edit quotas or Request more. Google routinely approves higher limits for legitimate SaaS use; approvals typically come back in 24–48 hours.

Removing your key

Click Remove on the YouTube Data API card. Any recurring reindex jobs that were running on your key will pause.

Troubleshooting

"YouTube channel search not configured (missing Google credentials)." The JSON was rejected. Most often this is because the YouTube Data API v3 wasn't enabled on the project (Step 2), or the JSON is incomplete. Re-download the key from the Cloud Console and paste the whole file.

"quotaExceeded" error from Google. Your own project ran out of daily quota. Either wait until midnight Pacific time (when Google resets) or request a quota increase from the Cloud Console.

"keyInvalid" or 403 errors. The service account JSON was revoked or the project was deleted. Generate a new key with Step 4 and re-paste.