A node red storage module which uses Google Storage (based on the AWS S3 storage module)
Last updated a year ago by psvensson .
MIT · Repository · Bugs · Original npm · Tarball · package.json
$ cnpm install node-red-contrib-storage-google 
SYNC missed versions from official npm registry.


A node red storage module which uses Google Storage (loosely based on the AWS S3 storage module)

This module supports automatic reloading of flows.


npm i --save node-red-contrib-storage-google

Inside the settings.js file, add a line for storagemodule, like this

storageModule: require('node-red-contrib-storage-google')

New properties for settings.js

You must also set the following new settings to be able to make use of the storage module

googleStorageAppname: 'mycoolapp',
googleStorageBucket: '',
googleProjectId: 'something-12345',
googleFirebaseReload: true,         // optional
googleDbUrl: '',  // optional
googleCredentials: {
  "type": "service_account",
  "project_id": "something-12345",
  "private_key_id": "x0i822bae71898b6d00bb0011bbzz0a0089a901010111d98",
  "private_key": "-----BEGIN PRIVATE KEY-----\nOP0PLLL....5ThEUz...\n-----END PRIVATE KEY-----\n",
  "client_email": "",
  "client_id": "88484848484848484848",
  "auth_uri": "",
  "token_uri": "",
  "auth_provider_x509_cert_url": "",
  "client_x509_cert_url": ""

The plugin works by using a service account certificate for a given google cloud project. A good way to get is to create a firebase project, and then from the firebase web console download the project service account certificate.

Firebase service accounts already have the proper rights for cloud storage (among other things)

  1. Create a Firebase project (or go to one you already have)
  2. Go the firebase web console
  3. Click the blue cogwheel icon at the top left
  4. Go to the 'Service Account' tab
  5. Download a new private key. The content of the file is the property 'googleCredenttials' above.

The other google* settings can be found in the very first tab.


Any node-red instance running with the google cloud storage plugin set to a specific configuration will share settings, flows, library entities, et.c. with all others with the same setup.

This means that a developer can develop locally with the google cloud storage plugin, and be able to have the changes shared to other node-red instances running in the cloud, perhaps in docker containers, long running or as cloud functions/lambdas.

To also enable live reloading of all instances, you must use a serivce account certificate from firebase and also set the properties 'googleFirebaseReload' and 'googleDbUrl'.

This will let the plugin register listeners for a specific path in the reactive firebase service, so that they will get a callback whenever the flows have changed (been deployed by the developer). Firebase Rtdb support up to 100000 simultaneous connections, which is then the upper limit for cloud instances.

This usage of firebase is well below the free tier so moderate use (100 instance perhaps?) will never cost anything.

Current Tags

  • 1.0.9                                ...           latest (a year ago)

10 Versions

  • 1.0.9                                ...           a year ago
  • 1.0.8                                ...           a year ago
  • 1.0.7                                ...           a year ago
  • 1.0.6                                ...           a year ago
  • 1.0.5                                ...           a year ago
  • 1.0.4                                ...           a year ago
  • 1.0.3                                ...           a year ago
  • 1.0.2                                ...           a year ago
  • 1.0.1                                ...           a year ago
  • 1.0.0                                ...           a year ago
Maintainers (1)
Today 0
This Week 0
This Month 0
Last Day 0
Last Week 0
Last Month 0
Dependencies (3)
Dev Dependencies (4)
Dependents (0)

Copyright 2014 - 2016 © |