Google Cloud Scheduler
Create, run, pause and delete cron jobs in Google Cloud Scheduler (Google OAuth2).
OCNORA ships 16 typed Google Cloud Scheduler operations. Each node has a schema-driven form, input and output tables beside its settings, and is pre-flighted by Workflow Health before your first real run.
Before you connect Google Cloud Scheduler
- Authentication
- OAuth 2.0
- Credential
- {"client_id", "client_secret", "refresh_token"}
- Connection test
- Available: the stored credential can be checked against the provider when you add it. This is not a record that a test was run or passed.
What you can do with Google Cloud Scheduler
Operations, grouped by what they do to your data.
Create and send 2
Read and search 7
Delete and cancel 3
A sample Google Cloud Scheduler workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Scheduler trigger is needed.
- 2Get Cmek Config Locationcloud_scheduler.get_cmek_config_locationGets the Scheduler config in the project/region.
- 3Cancel Operationcloud_scheduler.cancel_operationStarts asynchronous cancellation on a long-running operation.
An outline built from this provider’s node contracts, not a recorded run. Each step’s output fields are available to the next in the field picker.
Every node below has a reference page: what it does, the connection it needs, its config fields with types, constraints and examples, and the shapes it emits.
Operations 16
- Cancel OperationStarts asynchronous cancellation on a long-running operation.cloud_scheduler.cancel_operation
- Create HTTP JobCreate a Cloud Scheduler cron job that calls an HTTP endpoint.cloud_scheduler.create_http_job
- Delete JobDelete a Cloud Scheduler job.cloud_scheduler.delete_job
- Delete OperationDeletes a long-running operation.cloud_scheduler.delete_operation
- Get Cmek Config LocationGets the Scheduler config in the project/region.cloud_scheduler.get_cmek_config_location
- Get JobGets a job.cloud_scheduler.get_job
- Get LocationGets information about a location.cloud_scheduler.get_location
- Get OperationGets the latest state of a long-running operation.cloud_scheduler.get_operation
- List JobsList Cloud Scheduler jobs in a project location.cloud_scheduler.list_jobs
- List LocationsLists information about the supported locations for this service.cloud_scheduler.list_locations
- List OperationsLists operations that match the specified filter in the request.cloud_scheduler.list_operations
- Pause JobPause a Cloud Scheduler job.cloud_scheduler.pause_job
- Resume JobResume a paused Cloud Scheduler job.cloud_scheduler.resume_job
- Run JobForce-run a Cloud Scheduler job now.cloud_scheduler.run_job
- Update Cmek Config LocationInitializes or Updates the a scheduler config.cloud_scheduler.update_cmek_config_location
- Update JobUpdates a job.cloud_scheduler.update_job
Google Cloud Scheduler questions
- How does OCNORA authenticate with Google Cloud Scheduler?
- With a stored OAuth 2.0 credential, shaped {"client_id", "client_secret", "refresh_token"}. A connection test can check it when you add it.
- What can I automate with Google Cloud Scheduler?
- 16 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Scheduler operation I need is not listed?
- Where Google Cloud Scheduler has an HTTP API, call it from the HTTP node with the same credential, or describe the step to the AI builder, which asks our team for a typed node when one is missing.
- Are there templates that use Google Cloud Scheduler?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Scheduler calls controlled?
- Every call and every run step is audited, runs count against the execution budget, and Workflow Health pre-flights the workflow when you save it.
See your first Google Cloud Scheduler workflow run.
Book a technical demo. We add the connection, pick a template or describe the workflow to Build with AI, and Workflow Health checks it before it runs.