Cloud Scheduler API

Name: Cloud Scheduler API API
Brand: Cloud Scheduler API
Availability: InStock

✓ Official Vendor SpecDeveloper ToolsCi Cdoauth210 EndpointsREST

For Agents

Schedule recurring HTTP, App Engine, or Pub/Sub jobs using cron expressions and pause, resume, or trigger them on demand. Lets agents own time-based automation across GCP without standing up a cron host.

Quickstart

Get started with Cloud Scheduler API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"schedule a recurring job"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Cloud Scheduler API API.

Create scheduled jobs that target HTTP endpoints, App Engine handlers, or Pub/Sub topics

Pause and resume jobs around release windows or incident response

Trigger a queued job to run immediately for testing or backfill

Configure retry policy with exponential backoff and max attempts per job

GET STARTED

Start building with Cloud Scheduler API API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Cloud Scheduler API API for, with concrete tasks.

★ Cron-Driven HTTP Webhooks

Replace self-managed cron boxes with managed schedules that POST to any reachable HTTPS endpoint. Cloud Scheduler signs the request with an OIDC or OAuth token from a service account and retries on failure with configurable backoff, making it suitable for nightly billing rollups, cache warmers, and reconciliation jobs that need to run on time without operators.

Create a Cloud Scheduler job that sends a POST to https://api.example.com/reconcile every day at 03:00 UTC with retries enabled

Pub/Sub Fan-Out On a Schedule

Trigger downstream pipelines by publishing a message to a Pub/Sub topic on a fixed cadence. Cloud Scheduler jobs with a Pub/Sub target are ideal for orchestrating Cloud Functions, Cloud Run services, or Dataflow pipelines without coupling them to one another, and the schedule runs in the same region as the consumer to keep latency predictable.

Create a job that publishes {"action": "refresh"} to projects/acme/topics/data-refresh every 15 minutes

Maintenance Window Pausing

Pause and later resume scheduled jobs around release windows or incident response so noisy cron firings do not pile up while a service is down. Cloud Scheduler stores the schedule state separately from the running schedule, letting an agent or runbook flip jobs off and back on with a single API call each.

Pause job projects/acme/locations/us-central1/jobs/billing-rollup, run the deployment, then call resume on the same job

Agent-Triggered Scheduled Workflows

An AI agent can stand up a one-off recurring job to drive its own multi-step workflow — for example, polling a slow-moving data source every 30 minutes and stopping once a condition is met. Through Jentic, the agent searches for 'schedule a recurring job', receives the jobs.create schema, and provisions the job without learning the full Cloud Scheduler resource model.

Use Jentic to create a Cloud Scheduler job that triggers the agent's webhook every 30 minutes and call delete on the job once the workflow completes

Key Endpoints

10 endpoints — cloud scheduler is a fully managed enterprise-grade cron service for google cloud.

METHOD

PATH

DESCRIPTION

GET

/v1/{+name}/locations

List Cloud Scheduler locations available to the project

POST

/v1/{+name}:run

Trigger a job to run immediately

POST

/v1/{+name}:pause

Pause an active scheduled job

POST

/v1/{+name}:resume

Resume a paused job

POST

/v1/{+name}:cancel

Cancel an in-flight job execution

GET

/v1/{+name}/locations

List Cloud Scheduler locations available to the project

POST

/v1/{+name}:run

Trigger a job to run immediately

POST

/v1/{+name}:pause

Pause an active scheduled job

POST

/v1/{+name}:resume

Resume a paused job

POST

/v1/{+name}:cancel

Cancel an in-flight job execution

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Google OAuth 2.0 client credentials and refresh tokens for Cloud Scheduler are stored encrypted in the Jentic vault. Agents only see scoped short-lived access tokens at execution time.

Intent-based discovery

Agents search Jentic with intents like 'schedule a recurring job' and Jentic returns the jobs.create operation with its request schema, so the agent does not need to read Google's discovery document to assemble the call.

Time to first call

Direct integration with Cloud Scheduler: 1-2 days for OAuth setup, region selection, and target configuration. Through Jentic: under 30 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Cloud Tasks API

Queue-based asynchronous task dispatch instead of cron-based scheduling

Use Cloud Tasks for ad-hoc work items with rate limiting and retries; use Cloud Scheduler for recurring time-based fires

Complementary

Cloud Pub/Sub API

Pub/Sub topics are a common Cloud Scheduler target for fan-out

Pair Pub/Sub with Cloud Scheduler when you want one schedule to trigger many downstream consumers

Complementary

Cloud Workflows API

Multi-step orchestration that Cloud Scheduler can kick off on a cadence

Use Workflows when the scheduled job needs to chain several services with conditional logic; Cloud Scheduler alone only fires a single target

FAQs

Specific to using Cloud Scheduler API API through Jentic.

What authentication does the Cloud Scheduler API use?

It uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic the OAuth client and refresh token live in the Jentic vault and only short-lived access tokens are passed to the agent runtime.

Can I trigger a scheduled job on demand with the Cloud Scheduler API?

Yes. Call the run method on /v1/{name}:run to fire a job immediately outside its normal schedule. This is the standard way to validate a job after creating or editing it.

What are the rate limits for the Cloud Scheduler API?

Google enforces per-project quotas on jobs created and on administrative API calls per minute. Job execution itself is governed by the per-job retry configuration, not by the API quota — most projects can run thousands of jobs concurrently within the default limits.

How do I create a recurring job through Jentic?

Search Jentic for 'schedule a recurring job', load the projects.locations.jobs.create schema, and execute a call against /v1/{parent}/jobs with the cron schedule, target, and timezone. Jentic returns the input schema so the agent fills only the fields it needs.

Is the Cloud Scheduler API free?

Cloud Scheduler offers three free jobs per billing account per month and charges a small monthly fee per additional job. The API itself has no per-call charge beyond the job pricing.

What target types does Cloud Scheduler support?

Each job can target an HTTP or HTTPS endpoint, an App Engine HTTP handler, or a Pub/Sub topic. Use HTTP targets with OIDC tokens to reach private Cloud Run or Cloud Functions services without exposing them publicly.