Not connectable yet
You cannot connect YouTube to FounderReply today — the Google app is still pending review, so the connect flow is disabled and the authorisation endpoint refuses. When it opens it is a comment tool and nothing else: no video upload, no Community posts, no direct messages, and a daily API quota that search burns quickly.
You cannot connect YouTube to FounderReply today. The single scope this connector needs is one Google classifies as sensitive, so the consent screen requires Google app verification and a YouTube API Services compliance audit before it can serve users outside a test list. The connect button is disabled in the dashboard and the authorisation endpoint refuses the request, so nothing on this page is available to switch on yet — on any plan.
On YouTube
Comment replies only. No publishing, no DMs, and a hard daily API quota.
The agent finds videos on a topic and drafts a comment or a reply. There is no publishing step, because YouTube gives third-party apps nowhere to publish.
Publishing is switched off in the connector: video upload is out of scope and Community posts have no public API at all, so a publish action fails rather than pretending.
YouTube prices API calls in units and search is the expensive one, so discovery on YouTube has a budget in a way no other platform here does.
The daily unit budget is per Google Cloud project and shared across every user of the app — a search costs roughly a hundred times a plain read.
Every public action on YouTube waits for a human, including replying to a comment on your own video.
YouTube’s spam policy holds promotional comments aggressively, so the ceiling table caps all four actions at approval rather than allowing own-content automation.
The room
A YouTube comment on a tutorial or review keeps getting read for as long as the video does, which is often years. The audience is people mid-problem, watching someone else solve it. That is a genuinely good place to be useful and a spectacularly bad place to be promotional — YouTube’s spam filters exist mostly because of this surface.
YouTube removes promotional comments aggressively and does it silently — a filtered comment often looks published to its author and is invisible to everyone else. Volume does not just risk removal; it risks removal you cannot see.
The ceiling
Two layers decide whether an action happens by itself: your autonomy dial, and a hard ceiling we impose per platform. The safer of the two always wins, so the dial can make things stricter and never looser. This table is generated from that ceiling.
| Action | Ships as | Most permissive allowed |
|---|---|---|
| Publish your own postOriginal content from your connected account | No API on YouTube | No API on YouTube |
| Reply on your own postsAnswering comments left on your content | Waits for your approval | Waits for your approval |
| Direct messagePrivate messages to a person | No API on YouTube | No API on YouTube |
| Comment on someone else’s postThe highest-risk action on every platform | Not permitted | Waits for your approval |
YouTube’s spam policy holds promotional comments aggressively, so every public interaction is human-gated — there is no action on YouTube that may run unattended. Publishing is not supported at all: there is no text-post or Community API for third-party apps. These ceilings are already in the controller and apply the moment the platform opens.
A single Google scope covers channel reads, comment writes and moderation. Google classifies it as sensitive, which is what puts the app in verification.
Nothing here is a marketing paraphrase — it is the string the connect flow sends, copied from lib/connectors/youtube.ts.
https://www.googleapis.com/auth/youtube.force-sslFAQ
No. YouTube is marked coming-soon in the platform registry, so the dashboard offers no connect button and the authorisation endpoint refuses the request. The connector is written and tested, but the Google app is not cleared to serve real users.
No. Video upload is deliberately out of scope and YouTube exposes no public API for Community posts, so publishing is switched off entirely in the connector and a publish action reports a failure rather than doing something unexpected.
Google budgets the YouTube Data API in units per Cloud project, shared across every user of an application, and a search call costs roughly a hundred times a simple read. That makes discovery on YouTube a genuinely scarce resource rather than a rate limit you can wait out.
No. Every YouTube action is capped at human approval, including replies to comments on your own videos. YouTube filters promotional comments aggressively and often invisibly, so an unattended reply loop would fail in a way you could not observe.
YouTube is not connectable yet. Reddit, X, Bluesky, Lemmy and Discourse are — and the approval queue works the same way on all of them.