Why this is a one-time chore — Google Drive setup — VidVertex Docs
Docs/Google Drive setup/Why this is a one-time chore

Why this is a one-time chore

Google only lets desktop apps talk to Drive through an OAuth client that the account owner creates — there is no shared VidVertex key you could paste. So you create a tiny "app" in your own Google Cloud account (free, no billing), download its credentials.json, and VidVertex uses it to ask for your permission in a browser window. After that, a token is cached and refreshed automatically — as long as you publish the client in step 1.4 below, which is the one step people skip.

Google Drive as the transfer vehicle: Metricool re-hosts the file and the Drive copy is deletedVidVertexDriveMetricoolre-hostspostshare linkthe Drive copy is deleted —Metricool has its own
FIG 1Drive link in, Metricool-hosted copy out — and the Drive copy is deleted afterwards.

You need this for both Metricool modes: Metricool (Drive + CSV) hands the planner your Drive links in the import CSV, and Metricool API re-hosts each file from a Drive link before it schedules the post. The Zernio modes never touch Drive.