Create HTTP Task
cloud_tasks.create_http_task
ActionGoogle Cloudconnection required
Calls POST /projects/{project}/locations/{location}/queues/{queue}/tasks.
Enqueue an HTTP task on a Cloud Tasks queue, optionally scheduled.
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
10 fields, 2 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 | — | — | — |
url Target URL the task will call. | string | Yes | — | — | — |
http_method HTTP method — Cloud Tasks accepts only the listed values. | string | No | POST | one of "POST", "GET", "PUT", "PATCH", "DELETE" | — |
headers Request headers (JSON object). | object | No | — | — | — |
body Request body (sent base64-encoded). | string | No | — | — | — |
service_account_email Service account for an OIDC token (optional). | string | No | — | email format | — |
schedule_time RFC3339 time to run the task (optional). | string | No | — | — | — |
task_id Explicit task id (optional; must be unique). | string | No | — | — | — |
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"http_method": "POST"
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
name | string | — |
schedule_time | string | — |
create_time | string | — |
{
"create_time": "",
"name": "",
"ok": false,
"schedule_time": ""
}Related Google Cloud Tasks nodes
See Create HTTP Task 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.