Execute Http Request
integration_connectors.execute_http_request
ActionGoogle Cloudconnection required
Calls Connectors POST /v2/projects/{projectsId}/locations/{locationsId}/connections/{connectionsId}:executeHttpRequest.
Executes a generic HTTP request. This supports all payload formats including REST/JSON, GraphQL, XML, SOAP, and Multipart by passing the rendered payload as raw bytes.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- OAuth 2.0
- Providers
- Google Connectors
- Secret shape
- {"client_id", "client_secret", "refresh_token"}
- Config it needs
- location, project_id
- Resolved by
- config.connection_id, else node.connection_id
Configuration
4 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 Location / region (overrides connection). | string | No | — | — | — |
connection Connection id. | string | Yes | — | — | — |
body Request body (ExecuteHttpRequestRequest) as JSON. | object | No | — | — | — |
Output
One shape.
result
| Field | Type | Example |
|---|---|---|
ok | boolean | — |
reason | string | — |
headers | array | — |
statusCode | number | — |
body | string | — |
{
"body": "",
"headers": [],
"ok": false,
"reason": "",
"statusCode": 0
}Related Google Connectors nodes
See Execute Http Request run in a workflow.
In a technical demo we add the Google Connectors connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.