The YouTube channel lets a Clone read and reply to comments on your videos — nothing else. YouTube exposes no business DM API, so there's no inbox, no message templates and no 24-hour conversational window like the Meta channels have. What you get is public comment-thread access on videos owned by the connected channel, over the YouTube Data API v3, authenticated through Google OAuth. Setup is quick — a few minutes — but there's one consent-screen checkbox you must not skip, and a couple of operating limits (a daily quota, and YouTube's own comment moderation) worth understanding before you rely on it.
The Google account you sign in with must have at least one YouTube channel, and you must be its Owner or Manager — a personal Google account that has never created a channel can't be connected. If the channel belongs to a Brand Account, sign in with the Google account that manages it. See Before you connect below.
What the YouTube channel is
IcloneU talks to YouTube through the YouTube Data API v3, which surfaces comment threads on the videos your channel owns. A few consequences follow from that, and they're different enough from the other channels to call out up front:
- Comments, not DMs. Every Clone-to-viewer interaction on YouTube is a public comment reply, visible to anyone. YouTube has no business messaging API, so there is no private inbox and no way to DM a viewer. If a conversation needs to go private, reply publicly asking the viewer to reach you on WhatsApp, Telegram or Email.
- Only your channel's videos. A Clone reads and replies to comments on videos owned by the connected channel — not other creators' videos.
- Google OAuth, not Meta. You authorize with the Google account that administers the channel; the connector requests a single YouTube permission (details in What IcloneU can access).
- Pull-based, so there's some latency. The YouTube Data API doesn't push new comments to a webhook — IcloneU polls for them. So a fresh comment takes a little while to appear in Messages rather than showing up instantly.
IcloneU's polling isn't a fixed interval — it's a dynamic cadence that adapts to factors like how recently the video was published and how much comment traffic it's getting (more-recent, busier content is checked more often). So reply latency varies rather than being a constant you can quote.
You add YouTube from the Connections page. Once active, it appears there as a row identified by the YouTube channel name, and incoming comments surface in Messages tagged with the channel — each thread shown against the video it belongs to.
Before you connect
IcloneU's own pre-flight screen sums up the checklist as "Before you start". Three things need to be true:
- A YouTube channel exists on the account. The Google account you sign in with must administer at least one channel. Brand-new channels with no videos still work for the Connect flow — but there's nothing for the Clone to reply to until viewers comment on a video you've uploaded.
- You're an Owner or Manager. For Brand Accounts with several people, only the Owner or a Manager can grant a third-party app access. Editors and lower roles can't. If you're not one of those, either have the Owner add you as Manager, or have them run the Connect flow.
- Sign in with the right Google account. If the channel belongs to a Brand Account, use the Google account that manages that Brand Account — otherwise the channel won't appear in the picker.
Create one free at youtube.com (profile picture → Create a channel). If a Brand-Account channel is missing from the picker, confirm which Google account manages it at myaccount.google.com/brandaccounts, then sign in with that account.
Connecting a YouTube channel
The whole flow takes about 3–5 minutes: start it in IcloneU, authorize in Google, then pick the channel back in IcloneU. The one step that matters most is the Google consent screen — read step 3 carefully.
Start a new YouTube connection
Open Connections in the left sidebar, click New connection, and pick YouTube. A pre-flight screen titled "Connect your YouTube account" appears first — it restates the "Before you start" checklist (channel required, Brand Accounts, and the consent-screen checkbox) and links an in-product YouTube Connection Guide. Read it, then continue to Google to sign in.
Sign in with Google and pick the channel
IcloneU redirects you to Google's sign-in. Use the Google account that administers the channel. If that account manages several channels (a personal one plus one or more Brand Accounts), Google's picker lets you choose which channel this Connection represents.
Tick the YouTube-access checkbox, then continue
On Google's consent screen you'll be asked to grant access to your YouTube data. Grant it and continue.
Heads upThis is the #1 thing people miss. On Google's consent screen the YouTube-access checkbox is not checked by default — you must tick it yourself. Its wording is Google's own: "See, edit, and permanently delete your YouTube videos, ratings, comments and captions." If you skip it, the connection still "succeeds" but the Clone can never read or reply to a comment — you'd have to disconnect and reconnect to fix it. (The "permanently delete" phrasing is Google's standard description for this permission; IcloneU only reads comments and posts replies — it doesn't delete your videos or content. See What IcloneU can access.)
Choose the channel in IcloneU
Back in IcloneU, a screen headed Choose YouTube Channels confirms "Your account was successfully authenticated. Choose the YouTube channels that you want IcloneU to connect to." and lists your channel(s), each with its own Connect button. Click Connect on the one you want.
Set the account options and save
The Account options for <channel> panel opens with your Clone pre-selected. Confirm the Clone, review the Response authorizations and other settings, and tick the AI identifier ✨ confirmation card. On YouTube (a comment channel), an enabled connection's Save button stays disabled until you switch that confirmation on — while it's unchecked the panel shows "Required before enabling this integration." Once it's checked, click Save. The channel then shows in the Connections grid; its status reflects the Enabled toggle.
NoteOn a fresh connect the Clone dropdown may auto-fill your only Clone, but the selection only persists if you click Save — closing with Cancel discards it. See Attaching a Clone for the full panel, including the AI identifier ✨ confirmation.
Google may show "This app isn't verified" if IcloneU's Google app review for its sensitive scopes hasn't cleared yet. As of writing, that review is in progress, so the friction can still appear. If you see it, check with your IcloneU contact to confirm it's expected at this stage before clicking through.
Attaching a Clone
The Account options for <channel> panel is where you attach the Clone and decide how it behaves. You can open it any time from the Connections page by selecting the YouTube row. Because YouTube is a comment channel, its panel includes options the DM-only channels don't:
| Setting | What it does |
|---|---|
| Enabled | When off, incoming comments for this account are ignored. Tokens are kept, so you can re-enable later without reconnecting. |
| Clone | The Clone that will reply on behalf of this integration. Pick it from the dropdown. |
| Response authorizations required for | Per-category control over whether the Clone's reply is sent automatically or held for you to authorize first. A category you don't mark is auto-answered; a category you mark requires your approval before anything posts. |
| Post options | Controls how AI replies handle your public posts and comments. This section is specific to the comment channels (Facebook / Instagram / YouTube). |
| AI identifier ✨ | A mandatory confirmation card on the comment channels (Facebook / Instagram / YouTube): <em>"Confirm the AI identifier is visible on this profile before enabling the Clone."</em> Tick <em>"I have added the ✨ AI identifier and disclosure to this profile."</em> — on an enabled connection Save stays disabled until you do, and the panel shows the <em>"Required before enabling this integration."</em> hint. Once checked and saved it reads <em>"Confirmed on {date}."</em> |
A comment can fail to get an automatic reply for two unrelated reasons. (1) YouTube held it — YouTube's own moderation holds comments with hashtags, links or blocked words for owner review, so the Clone never sees them via the API until you approve them. (2) Your Response authorizations require approval — an IcloneU setting that holds the Clone's reply for you to authorize. They're independent; see Comment moderation.
Without an attached Clone, incoming comments still queue in Messages but nothing is auto-replied. For the full attach-and-enable walkthrough that applies across every channel, see Assigning a Clone to a platform.
The daily quota (and the ~200-reply ceiling)
The single most consequential operating limit on YouTube is the Data API quota. Google rate-limits the API not by requests-per-second but by a daily budget of "units," and every operation costs a set number of them:
| Operation | Cost | Notes |
|---|---|---|
| Read comments (polling) | 1 unit | Cheap. But it runs all day, so it still adds up. |
| Post a reply to a comment | 50 units | The Clone's main outbound action. |
| Approve / reject a held comment | 50 units | Same cost as a reply — moderation isn't free. |
The default budget is 10,000 units/day, which works out to ~200 Clone replies per day (10,000 ÷ 50). In practice the realistic ceiling is a bit lower — roughly 150–180 replies/day — because polling reads and any moderation actions draw from the same pool. The budget resets at midnight Pacific time (a fixed clock boundary, not 24 hours after your last spend). Once it's spent, further calls fail until the reset, and the Clone's replies pause.
YouTube replies run against IcloneU's own API quota, and it's shared — there's a single IcloneU project whose daily budget every customer's YouTube Connection draws from, not a per-customer project. So a busy day elsewhere can, in principle, draw down the shared pool. Quota uplift is requested by IcloneU's parent (via a YouTube API Compliance Audit with Google), not by you — IcloneU is in the process of requesting more. If you run a high-comment-volume channel, raise it with IcloneU support rather than filing your own audit.
Comment moderation and Held for Review
YouTube runs its own AI moderation on incoming comments before they're published. Comments containing hashtags, links, blocked words, or matching other suspicious patterns get held for review — they stay private until you approve them, and the Held tab in YouTube Studio retains them for up to 60 days before auto-discarding.
- The Clone can't reply to a held comment until it's approved — it doesn't reach IcloneU via the API while held. Approve it in YouTube Studio (Comments → Held for review) and the next poll picks it up.
- Approving costs quota too. Each moderation action is 50 units, the same as a reply — so mass-approving a large held backlog can eat a real chunk of the daily budget.
- A reply to a held comment stays invisible until the parent comment is approved, then both appear together.
- Whether IcloneU surfaces held comments in the Messages surface, and whether the Clone can be configured to auto-approve or auto-reject them, is not confirmed — check with IcloneU support if held-comment handling is central to your use case.
What IcloneU can access
IcloneU requests a single YouTube permission — the read-write scope that covers reading comments, posting replies, and moderating (approve/reject) held comments. On Google's screen its wording is "See, edit, and permanently delete your YouTube videos, ratings, comments and captions"; inside IcloneU's own pre-flight screen the same permission is described as "See, edit and manage your YouTube videos, ratings, comments and captions." Both refer to the same underlying scope.
That's Google's standard, unavoidable description for this permission — Google doesn't offer a narrower comments-only wording. IcloneU only reads comments and posts replies on your behalf. It does not upload videos, change your channel branding or thumbnails, touch your Analytics or revenue data, or delete your content.
What this permission does not grant: uploading videos, editing channel branding or descriptions, accessing Analytics revenue data, or managing ads. IcloneU's footprint is bounded to comment management. If you ever want to remove its access entirely, revoke it at myaccount.google.com/permissions — see Disconnecting.
Disconnecting a channel
To remove a YouTube Connection, select its row on the Connections page and click Remove in the toolbar, then confirm. After disconnect, IcloneU stops polling the channel for comments and the attached Clone stops replying. The channel itself — videos, subscribers, settings — is untouched, and new viewer comments keep appearing publicly on YouTube; they just no longer reach IcloneU.
Two things Remove does not do. First, replies the Clone already posted stay on YouTube — there's no bulk retraction; delete individual ones in YouTube Studio if you need to. Second, the Google OAuth grant remains on file until you explicitly revoke it at myaccount.google.com/permissions (find IcloneU → Remove access). Revoking is optional — skip it and a future reconnect reuses the grant; revoke it and the next Connect re-runs the full Google consent screen.
Troubleshooting
Two symptoms cover most cases: a comment isn't reaching IcloneU at all, or the comment arrives but no reply goes out. Diagnose by checking Messages first — if the comment shows there but got no reply, it's a Clone-side or quota issue; if it doesn't show, it's a polling, moderation or OAuth issue.
A comment isn't arriving in IcloneU. Work through these in order:
- It's held for review at YouTube — open YouTube Studio → Comments → Held (and Likely Spam). Held comments don't reach IcloneU until you approve them.
- It's too fresh — polling is adaptive, not instant. Give it a poll cycle and check again, especially for a comment posted in the last few minutes.
- It's on the wrong channel — if you administer several channels, confirm the video actually belongs to the connected one.
- The Connection status is amber/inactive — the OAuth grant may have been revoked, or the daily quota exhausted. Check myaccount.google.com/permissions for IcloneU; if it's gone, reconnect.
- The commenter deleted it before the next poll — deletions are immediate at the API level, so IcloneU never sees it. No recovery.
The comment arrives but the Clone doesn't reply. Usual causes:
- The daily quota is exhausted — if the Clone was busy earlier and then went quiet, you may have hit the ~200-reply ceiling. Wait for the midnight-Pacific reset and see whether replies resume.
- Its Response category requires authorization — the reply is being held for you to approve rather than auto-sent. Check the Response authorizations on the Connection.
- No Clone is attached, or the Clone is configured to answer from library only with no matching content — confirm a Clone is attached and its Knowledge covers the question.
If you've worked through all of this and a fresh test comment from a different account still doesn't get handled, escalate to support with the connected channel name, the video URL, the commenter's @handle plus timestamp, which tab (if any) the comment sits in at YouTube, and screenshots of the Connections page and the Messages surface. For the cross-channel version of these checks, see Social media connection issues.
Frequently asked
No. YouTube exposes no business DM API — there's no inbox and no way to privately message a viewer. Everything happens through public comment replies. If a conversation needs to go private, have the Clone reply publicly asking the viewer to reach you on WhatsApp, Telegram or Email.
Yes — one Connection per channel. Run the Connect flow once for each, and each appears as its own row identified by channel name (subject to your plan's Connection cap). Attach the same Clone to all of them for one persona, or a different Clone per channel. Keep in mind they all draw from the same shared daily quota.
Treat your Clone as scoped to the connected channel's own videos. YouTube's API only lets you moderate comments on channels you own, and whether IcloneU lets a Clone post on videos it doesn't own is a product behavior that hasn't been verified — so don't rely on it. For your own multi-channel setup, give each channel its own Connection.
Shorts are just videos to the API, so their comments flow through the same path as regular video comments and should be handled identically (each reply still costs 50 quota units). Community posts are a separate surface, and whether IcloneU polls their comments is not confirmed — assume they don't by default and ask support if you need them.
Maybe — live chat is a separate API surface (liveChatMessages) from regular comments, with different real-time and quota behavior. Whether IcloneU's YouTube Connection handles live chat, or only regular video comments, isn't confirmed. If live-chat handling is critical, confirm it with IcloneU support rather than assuming it works.
Last updated July 6, 2026 · Platform connections
