GitDoctorruntime, not static

Integrations / Google Cloud Scheduler

Google Cloud Scheduler

Not yet — service-account access, same careful pass as AWS.

Why connect it

Cloud Scheduler jobs and Cloud Functions/Run invocations are readable with a service account; the grant flow deserves its own design.

What you'll see

  • Planned: every scheduler job with schedule, last attempt status, and target

What the credential can and cannot do

Where to get it: —

It grants: Nothing is connected.

It cannot: —

Whatever you connect lives in an encrypted cookie in your browser and nowhere else. Sign out and it's gone; revoke it at the provider and it stops working immediately.

Connect

Open the engine