Resume Queue

cloud_tasks.resume_queue
ActionGoogle Cloudconnection required

Calls cloudtasks v2 POST /v2/projects/{projectsId}/locations/{locationsId}/queues/{queuesId}:resume.

Resume a 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, 2 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
location
Location or region; taken from the connection when unset.
stringNo———
queue
Queue name or id.
stringYes———
body
The ResumeQueueRequest resource, as the API defines it.
objectYes———

Output

One shape.

result

Extra keys beyond the ones listed can appear.

FieldTypeExample
appEngineRoutingOverride
object—
httpTarget
object—
name
string—
purgeTime
string—
rateLimits
object—
retryConfig
object—
stackdriverLoggingConfig
object—
state
string—
{
  "appEngineRoutingOverride": {},
  "httpTarget": {},
  "name": "",
  "purgeTime": "",
  "rateLimits": {},
  "retryConfig": {},
  "stackdriverLoggingConfig": {},
  "state": ""
}

See Resume 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.