Google Cloud Tasks
Google CloudOAuth 2.0Connection test available
Enqueue and manage HTTP tasks on Google Cloud Tasks queues (Google OAuth2).
OCNORA ships 19 typed Google Cloud Tasks 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 Tasks
- 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 Tasks
Operations, grouped by what they do to your data.
Create and send 3
Read and search 8
Delete and cancel 3
Other operations 1
A sample Google Cloud Tasks workflow
- 1A core triggerStart the run from a chat, form, manual, schedule, webhook, workflow trigger — no Google Cloud Tasks trigger is needed.
- 2Get Cmek Config Locationcloud_tasks.get_cmek_config_locationGets the CMEK config.
- 3Buffer Taskcloud_tasks.buffer_taskCreates and buffers a new task without the need to explicitly define a Task message.
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 19
- Buffer TaskCreates and buffers a new task without the need to explicitly define a Task message.cloud_tasks.buffer_task
- Create HTTP TaskEnqueue an HTTP task on a Cloud Tasks queue, optionally scheduled.cloud_tasks.create_http_task
- Create QueueCreates a queue.cloud_tasks.create_queue
- Delete QueueDeletes a queue.cloud_tasks.delete_queue
- Delete TaskDelete a task from a Cloud Tasks queue.cloud_tasks.delete_task
- Get Cmek Config LocationGets the CMEK config.cloud_tasks.get_cmek_config_location
- Get LocationGets information about a location.cloud_tasks.get_location
- Get OperationGets the latest state of a long-running operation.cloud_tasks.get_operation
- Get QueueGets a queue.cloud_tasks.get_queue
- Get TaskGets a task.cloud_tasks.get_task
- List LocationsLists information about the supported locations for this service.cloud_tasks.list_locations
- List QueuesList Cloud Tasks queues in a project location.cloud_tasks.list_queues
- List TasksList pending tasks on a Cloud Tasks queue.cloud_tasks.list_tasks
- Pause QueuePauses the queue.cloud_tasks.pause_queue
- Purge QueuePurge all tasks from a Cloud Tasks queue.cloud_tasks.purge_queue
- Resume QueueResume a queue.cloud_tasks.resume_queue
- Run TaskForces a task to run now.cloud_tasks.run_task
- Update Cmek Config LocationCreates or Updates a CMEK config.cloud_tasks.update_cmek_config_location
- Update QueueUpdates a queue.cloud_tasks.update_queue
Google Cloud Tasks questions
- How does OCNORA authenticate with Google Cloud Tasks?
- 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 Tasks?
- 19 typed operations, each with a reference page listing its config fields and the shapes it emits.
- What if the Google Cloud Tasks operation I need is not listed?
- Where Google Cloud Tasks 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 Tasks?
- Not yet. Start from a blank workflow, or describe the workflow to Build with AI.
- How are Google Cloud Tasks 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 Tasks 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.