Google Cloud Tasks API

Name: Cloud Tasks API
Brand: Cloud Tasks API
Availability: InStock

✓ Official Vendor SpecCloud InfrastructureServerlessoauth216 EndpointsREST

Install Jentic One Beta

Connect the Cloud Tasks API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Cloud Tasks API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Cloud Tasks API.

Create queues with configurable max dispatch rate, concurrency, and retry policy

Enqueue tasks that POST to HTTP endpoints with optional OIDC token authentication

Pause and resume queues during incidents to prevent thundering herds

GET STARTED

Start building with Cloud Tasks API

Explore with Jentic

View OpenAPI Document

For Agents

Create rate-limited task queues, enqueue HTTP or App Engine work items, and pause, resume, or purge queues on demand. Lets agents reliably hand off work to background workers without managing a queue cluster.

Use for: I need to create a Cloud Tasks queue with a max dispatch rate, Enqueue a task that POSTs to my worker endpoint, Pause a Cloud Tasks queue during an incident, Resume a paused Cloud Tasks queue

Not supported: Does not stream events, run cron schedules, or execute the task code itself - use for asynchronous, rate-limited dispatch of HTTP and App Engine targets only.

Use Cases

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

★ Offload Long Work From Request Handlers

Hand off slow operations like PDF generation, third-party API calls, and bulk emails to a Cloud Tasks queue so the user-facing request returns in milliseconds. The API enqueues an HTTP target with a payload, retry policy, and optional delay, and Cloud Tasks invokes the worker with reliable at-least-once delivery and exponential backoff.

Enqueue a task that POSTs {"order_id": 1234} to https://workers.example.com/generate-invoice with a 5 minute delay and 5 retry attempts

Rate-Limited Outbound Calls

Use a Cloud Tasks queue to throttle calls to a third-party API that imposes strict QPS limits. Configure a max dispatch rate and concurrency on the queue, enqueue every outbound call as a task, and Cloud Tasks paces the workers so the upstream service is never overwhelmed even during spikes.

Create a queue with maxDispatchesPerSecond=10 and enqueue 5,000 tasks that each POST to the partner's webhook endpoint

Incident-Time Queue Pausing

Pause a queue during an outage so tasks accumulate without firing against a broken downstream service, then resume once the service is healthy. Cloud Tasks retains queued items while paused and continues to apply the queue's retry policy on resume, which keeps work in flight without losing items or hammering a recovering system.

Pause queue projects/acme/locations/us-central1/queues/email-out, wait for the downstream alert to clear, then resume the queue

Agent-Controlled Background Work

An AI agent can enqueue follow-up work for itself instead of holding a long synchronous loop. Through Jentic the agent searches for 'enqueue cloud task', loads the tasks.create schema, and submits a task that calls back into the agent's webhook with the next step's input.

Use Jentic to enqueue a task on queue email-out that POSTs the next chunk of work to the agent's resume webhook in 60 seconds

Key Endpoints

16 endpoints — cloud tasks is a fully managed service for the asynchronous execution of distributed work items.

METHOD

PATH

DESCRIPTION

GET

/v2/{+name}/locations

List Cloud Tasks regions for the project

POST

/v2/{+name}:pause

Pause dispatching from a queue

POST

/v2/{+name}:resume

Resume a paused queue

POST

/v2/{+name}:purge

Purge all tasks from a queue

POST

/v2/{+name}:run

Force-run a queued task immediately

GET

/v2/{+name}/locations

List Cloud Tasks regions for the project

POST

/v2/{+name}:pause

Pause dispatching from a queue

POST

/v2/{+name}:resume

Resume a paused queue

POST

/v2/{+name}:purge

Purge all tasks from a queue

POST

/v2/{+name}:run

Force-run a queued task immediately

Why Jentic?

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

Credential isolation

Your Cloud Tasks OAuth credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'enqueue a task' or 'pause a Cloud Tasks queue', and Jentic returns the matching Cloud Tasks operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Cloud Tasks API through Jentic.

What authentication does the Cloud Tasks API use?

It uses Google OAuth 2.0 with the https://www.googleapis.com/auth/cloud-platform scope. Through Jentic the OAuth credentials live encrypted in your Jentic One instance and the agent only sees a short-lived access token at execution time.

Can Cloud Tasks call private Cloud Run services?

Yes. Configure the task's HTTP target with an OIDC token from a service account that has run.invoker on the target service. Cloud Tasks adds the bearer token to the dispatched request so the worker can be locked down to authenticated callers.

What are the rate limits for the Cloud Tasks API?

Each queue has a configurable maxDispatchesPerSecond and maxConcurrentDispatches that govern how fast tasks are dispatched. The control-plane API for creating queues and enqueuing tasks has its own per-project quota that defaults to several thousand operations per minute.

How do I enqueue a background task through Jentic?

Search Jentic for 'enqueue cloud task', load the tasks.create schema, and execute the call against /v2/{parent}/tasks with the HTTP target URL, body, and headers. Jentic returns the schema so the agent does not need to parse Cloud Tasks' resource model by hand.

Is the Cloud Tasks API free?

Cloud Tasks includes a free tier of one million operations per month per billing account and charges per million operations after that. The API itself has no per-call markup.

How do I drain a queue without losing tasks?

Pause the queue with /v2/{name}:pause so new dispatches stop, let in-flight work complete, then resume or purge as needed. Purge removes all queued tasks irreversibly, so use it only when the queued items can be discarded.

Can I limit what my agent is allowed to do with the Cloud Tasks API?

Yes. Because you run Jentic One yourself, your own rules decide which Cloud Tasks operations and credentials the agent can use. Since the queue and task resource names live in the URL path (for example /v2/{name}:pause and /v2/{name}:run), you can pin the agent to a single queue and grant only pause and resume, so it cannot run or purge tasks unless you add those operations. The OAuth credential stays in your self-hosted instance and is injected only at execution time, so the agent never handles it directly.

Google Cloud Tasks API

Connect the Cloud Tasks API to your agent

Capabilities

Start building with Cloud Tasks API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs