Get Target Http Proxy

compute_engine.get_target_http_proxy

ActionGoogle Cloudconnection required

Calls compute v1 GET /projects/{project}/global/targetHttpProxies/{targetHttpProxy}.

Returns the specified TargetHttpProxy resource.

Ask about Google Compute Engine All Google Compute Engine nodes

Connection

Required: Yes — the node will not save without one
Auth type: OAuth 2.0
Providers: Google Compute Engine
Secret shape: {"client_id", "client_secret", "refresh_token"}
Config it needs: project_id, zone
Resolved by: config.connection_id, else node.connection_id

Configuration

1 field, 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
target_http_proxy Target http proxy name or id.	string	Yes	—	—	—

Output

One shape.

result

Extra keys beyond the ones listed can appear.

Field	Type	Example
creationTimestamp	string	—
description	string	—
fingerprint	string	—
httpKeepAliveTimeoutSec	integer	—
id	string	—
kind	string	—
name	string	—
proxyBind	boolean	—
region	string	—
selfLink	string	—
urlMap	string	—

{
  "creationTimestamp": "",
  "description": "",
  "fingerprint": "",
  "httpKeepAliveTimeoutSec": 0,
  "id": "",
  "kind": "",
  "name": "",
  "proxyBind": false,
  "region": "",
  "selfLink": "",
  "urlMap": ""
}

Related Google Compute Engine nodes

See Get Target Http Proxy run in a workflow.

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

Book a technical demo Talk to sales