Google Cloud Run

Deploy and manage containerized services on Google Cloud Run.

Detail	Value
Category	Cloud & Infra
Base URL	https://run.googleapis.com/v2
Authentication	See connector docs
Endpoints	8
Connector key	gcp-cloud-run

Using Google Cloud Run in a workflow

1. Go to Connections and click New Connection.
2. Pick Google Cloud Run from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown — the full list is below.

Available endpoints

Endpoint	Summary
GET /projects/{projectId}/locations/{location}/services	List services
POST /projects/{projectId}/locations/{location}/services	Create a service
GET /projects/{projectId}/locations/{location}/services/{serviceId}	Get service details
PATCH /projects/{projectId}/locations/{location}/services/{serviceId}	Update a service
DELETE /projects/{projectId}/locations/{location}/services/{serviceId}	Delete a service
GET /projects/{projectId}/locations/{location}/services/{serviceId}/revisions	List revisions
GET /projects/{projectId}/locations/{location}/jobs	List jobs
POST /projects/{projectId}/locations/{location}/jobs/{jobId}:run	Run a job

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET /projects/{projectId}/locations/{location}/services

List services

Detail	Value
Operation ID	cloud.listServices
Method	GET
Path	/projects/{projectId}/locations/{location}/services

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listServices.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.

POST /projects/{projectId}/locations/{location}/services

Create a service

Detail	Value
Operation ID	cloud.createService
Method	POST
Path	/projects/{projectId}/locations/{location}/services

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.createService.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.

GET /projects/{projectId}/locations/{location}/services/{serviceId}

Get service details

Detail	Value
Operation ID	cloud.getService
Method	GET
Path	/projects/{projectId}/locations/{location}/services/{serviceId}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.getService.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.

PATCH /projects/{projectId}/locations/{location}/services/{serviceId}

Update a service

Detail	Value
Operation ID	cloud.updateService
Method	PATCH
Path	/projects/{projectId}/locations/{location}/services/{serviceId}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.updateService.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.

DELETE /projects/{projectId}/locations/{location}/services/{serviceId}

Delete a service

Detail	Value
Operation ID	cloud.deleteService
Method	DELETE
Path	/projects/{projectId}/locations/{location}/services/{serviceId}

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.deleteService.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.

GET /projects/{projectId}/locations/{location}/services/{serviceId}/revisions

List revisions

Detail	Value
Operation ID	cloud.listRevisions
Method	GET
Path	/projects/{projectId}/locations/{location}/services/{serviceId}/revisions

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listRevisions.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.

GET /projects/{projectId}/locations/{location}/jobs

List jobs

Detail	Value
Operation ID	cloud.listJobs
Method	GET
Path	/projects/{projectId}/locations/{location}/jobs

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.listJobs.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.

POST /projects/{projectId}/locations/{location}/jobs/{jobId}:run

Run a job

Detail	Value
Operation ID	cloud.runJob
Method	POST
Path	/projects/{projectId}/locations/{location}/jobs/{jobId}:run

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Google Cloud Run connection from the Connection dropdown.
3. In the Operation dropdown, select cloud.runJob.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Google Cloud Run API reference.