Cloud Run: Node.js Client

release level npm version

Cloud Run Admin API

A comprehensive list of changes in each version may be found in the CHANGELOG.

Read more about the client libraries for Cloud APIs, including the older Google APIs Client Libraries, in Client Libraries Explained.

Table of contents:


Before you begin

  1. Select or create a Cloud Platform project.
  2. Enable billing for your project.
  3. Enable the Cloud Run API.
  4. Set up authentication with a service account so you can access the API from your local workstation.

Installing the client library

npm install @google-cloud/run

Using the client library

 * TODO(developer): Uncomment these variables before running the sample.
 *  Required. The location and project to list resources on.
 *  Location must be a valid GCP region, and may not be the "-" wildcard.
 *  Format: projects/{projectnumber}/locations/{location}
// const parent = 'abc123'
 *  Maximum number of Services to return in this call.
// const pageSize = 1234
 *  A page token received from a previous call to ListServices.
 *  All other parameters must match.
// const pageToken = 'abc123'

 *  If true, returns deleted (but unexpired) resources along with active ones.
// const showDeleted = true
// Imports the Run library
const {ServicesClient} = require('@google-cloud/run').v2;

// Instantiates a client
const runClient = new ServicesClient();

async function callListServices() {
  // Construct request
  const request = {

  // Run request
  const iterable = await runClient.listServicesAsync(request);
  for await (const response of iterable) {



Samples are in the samples/ directory. Each sample's has instructions for running its sample.

SampleSource CodeTry it
Executions.cancel_executionsource codeOpen in Cloud Shell
Executions.delete_executionsource codeOpen in Cloud Shell
Executions.get_executionsource codeOpen in Cloud Shell
Executions.list_executionssource codeOpen in Cloud Shell
Jobs.create_jobsource codeOpen in Cloud Shell
Jobs.delete_jobsource codeOpen in Cloud Shell
Jobs.get_iam_policysource codeOpen in Cloud Shell
Jobs.get_jobsource codeOpen in Cloud Shell
Jobs.list_jobssource codeOpen in Cloud Shell
Jobs.run_jobsource codeOpen in Cloud Shell
Jobs.set_iam_policysource codeOpen in Cloud Shell
Jobs.test_iam_permissionssource codeOpen in Cloud Shell
Jobs.update_jobsource codeOpen in Cloud Shell
Revisions.delete_revisionsource codeOpen in Cloud Shell
Revisions.get_revisionsource codeOpen in Cloud Shell
Revisions.list_revisionssource codeOpen in Cloud Shell
Services.create_servicesource codeOpen in Cloud Shell
Services.delete_servicesource codeOpen in Cloud Shell
Services.get_iam_policysource codeOpen in Cloud Shell
Services.get_servicesource codeOpen in Cloud Shell
Services.list_servicessource codeOpen in Cloud Shell
Services.set_iam_policysource codeOpen in Cloud Shell
Services.test_iam_permissionssource codeOpen in Cloud Shell
Services.update_servicesource codeOpen in Cloud Shell
Tasks.get_tasksource codeOpen in Cloud Shell
Tasks.list_taskssource codeOpen in Cloud Shell
Quickstartsource codeOpen in Cloud Shell

The Cloud Run Node.js Client API Reference documentation also contains samples.

Supported Node.js Versions

Our client libraries follow the Node.js release schedule. Libraries are compatible with all current active and maintenance versions of Node.js. If you are using an end-of-life version of Node.js, we recommend that you update as soon as possible to an actively supported LTS version.

Google's client libraries support legacy versions of Node.js runtimes on a best-efforts basis with the following warnings:

  • Legacy versions are not tested in continuous integration.
  • Some security patches and features cannot be backported.
  • Dependencies cannot be kept up-to-date.

Client libraries targeting some end-of-life versions of Node.js are available, and can be installed through npm dist-tags. The dist-tags follow the naming convention legacy-(version). For example, npm install @google-cloud/run@legacy-8 installs client libraries for versions compatible with Node.js 8.


This library follows Semantic Versioning.

This library is considered to be stable. The code surface will not change in backwards-incompatible ways unless absolutely necessary (e.g. because of critical security issues) or with an extensive deprecation period. Issues and requests against stable libraries are addressed with the highest priority.

More Information: Google Cloud Platform Launch Stages


Contributions welcome! See the Contributing Guide.

Please note that this, the samples/, and a variety of configuration files in this repository (including .nycrc and tsconfig.json) are generated from a central template. To edit one of these files, make an edit to its templates in directory.


Apache Version 2.0