Create HTTP Job

cloud_scheduler.create_http_job
ActionGoogle Cloudconnection required

Calls POST /projects/{project}/locations/{location}/jobs with an httpTarget.

Create a Cloud Scheduler cron job that calls an HTTP endpoint.

Connection

Required
Yes — the node will not save without one
Auth type
OAuth 2.0
Providers
Google Cloud Scheduler
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, 3 required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.

FieldTypeRequiredDefaultConstraintsExample
project_id
GCP project id (overrides connection).
stringNo———
location
GCP location/region (overrides connection).
stringNo———
job_id
Job id (short name).
stringYes———
schedule
Crontab (*/5 * * * *) or an English-like schedule (every 5 minutes).
stringYes———
time_zone
IANA time zone.
stringNoUTC——
url
Absolute http(s) URL the job calls on every fire.
stringYes———
http_method
HTTP method — Cloud Scheduler accepts only the listed values.
stringNoPOSTone of "POST", "GET", "PUT", "PATCH", "DELETE"—
body
Request body (sent base64-encoded).
stringNo———
headers
Request headers (JSON object).
objectNo———
description
Job description (optional).
stringNo———

Example configuration

Every value below is the contract’s own example or default — nothing invented.

{
  "http_method": "POST",
  "time_zone": "UTC"
}

Output

One shape.

result

FieldTypeExample
ok
boolean—
name
string—
job_id
string—
schedule
string—
time_zone
string—
state
string—
next_run_time
string—
{
  "job_id": "",
  "name": "",
  "next_run_time": "",
  "ok": false,
  "schedule": "",
  "state": "",
  "time_zone": ""
}

See Create HTTP Job run in a workflow.

In a technical demo we add the Google Cloud Scheduler connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.