Skip to main content
Launcher connects to client-owned Google Drive folders through a read-only service account. PlainRouter verifies ownership before it inventories any media, so knowing a folder link is never enough to claim another workspace’s creative library.
This release inventories Drive media metadata only. It does not download media bytes, upload media to Meta, create ads, or activate spend.

​
Before you begin

You need:
  • Workspace-owner access in PlainRouter.
  • A verified email address on your PlainRouter account.
  • Permission to share the intended Google Drive folder.
  • A Launcher service-account email on the workspace settings page.
If Drive access is not provisioned for this workspace cell yet appears, contact PlainRouter support before continuing.

​
Connect a folder

1

Open workspace settings

In the PlainRouter sidebar, open Account → Workspace. Find Launcher Drive access.
2

Share the folder

Copy the displayed service-account email. In Google Drive, add that address to the intended folder as a Viewer.Share a top-level folder when you want Launcher to include its subfolders.
3

Submit the folder link

Copy the folder’s HTTPS Google Drive link into Google Drive folder link, then click Claim folder. PlainRouter starts ownership verification and reserves the claim for 72 hours.
4

Complete ownership verification

PlainRouter first attempts owner-domain verification. If the page presents a challenge filename, create an empty file with that exact name directly inside the claimed folder. Return to PlainRouter and click Verify ownership.
5

Wait for the verified state

The folder becomes Verified only after ownership proof succeeds. PlainRouter then starts the first read-only inventory sync automatically.

​
How ownership verification works

The challenge file must use the exact generated verify-<token>.txt filename. Put it directly inside the claimed folder, not in a subfolder. Workspace members can view claim state, but only the workspace owner receives the challenge filename or can manage the connection.

​
What Launcher syncs

After verification, Launcher scans the folder and its subfolders every 15 minutes. Shared Drive folders are supported. The current read-only inventory recognizes:
  • GIF, JPEG, and PNG images.
  • MP4 and MOV videos.
Launcher records file identity, name, type, size, checksum, and modified time. Unsupported files are ignored. Unchanged files are skipped idempotently, changed metadata is reconciled, and files missing from a complete scan are marked removed. Each sync attempt and outcome is recorded as durable operational evidence. Folder claims and ownership results also enter the workspace’s v2 audit chain.

​
Connection states

​
Troubleshoot

​
Challenge file not found

Confirm that the file uses the exact displayed name and sits directly inside the claimed folder. Make sure the service-account email still has Viewer access, then click Verify ownership again.

​
Folder inaccessible

Google Drive returned an access denial or could not find the folder. Re-share the folder with the displayed service-account email. For a previously verified folder, click Retry sync. You do not need to repeat ownership verification. Submit an HTTPS link to a Google Drive folder, not a file. Open the folder in Drive and copy its browser URL.

​
The folder is claimed by another workspace

A verified folder cannot be connected to two workspaces. Switch to the workspace that owns the existing connection. If the other claim is unverified, retry after its 72-hour window ends.

​
Verification keeps failing

Use the challenge-file path when the Drive owner uses another email domain, the folder is link-public, or Drive does not expose enough sharing metadata for automatic domain verification.

​
Next step

After inventory sync finishes, import a Launcher draft batch from CSV or XLSX, or pass the synced Drive links directly to launcher.draft_batch through MCP.