Purge Queue
cloud_tasks.purge_queue
ActionGoogle Cloudconnection required
Calls POST /projects/{project}/locations/{location}/queues/{queue}:purge.
Purge all tasks from a Cloud Tasks queue.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Cloud Tasks
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- project_id, location
- Resolved by
- config.connection_id, else node.connection_id
Configuration
3 fields, 1 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
project_id GCP project id (overrides connection). | string | No | — | — | — |
location GCP location/region (overrides connection). | string | No | — | — | — |
queue Queue id (short name). | string | Yes | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
name | string | — |
state | string | — |
purge_time | string | — |
{
"name": "",
"ok": false,
"purge_time": "",
"state": ""
}Related Google Cloud Tasks nodes
See Purge Queue run in a workflow.
In a technical demo we add the Google Cloud Tasks connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.