Realtime Database triggers


With Cloud Functions, you can handle events in the Firebase Realtime Database with no need to update client code. Cloud Functions lets you run Realtime Database operations with full administrative privileges, and ensures that each change to Realtime Database is processed individually. You can make Firebase Realtime Database changes via the data snapshot or via the Admin SDK.

In a typical lifecycle, a Firebase Realtime Database function does the following:

  1. Waits for changes to a particular Realtime Database path.
  2. Triggers when an event occurs and performs its tasks.
  3. Receives a data object that contains a snapshot of the data stored at that path.

You can trigger a function in response to the writing, creating, updating, or deleting of database nodes in Firebase Realtime Database. To control when the function triggers, specify one of the event handlers, and specify the Realtime Database path where it will listen for events.

Setting the function location

Distance between the location of a Realtime Database instance and the location of the function can create significant network latency. Also, a mismatch between regions can result in deployment failure. To avoid these situations, specify the function location so that it matches the database instance location.

Handling Realtime Database events

Functions let you handle Realtime Database events at two levels of specificity; you can listen for specifically for only write, creation, update, or deletion events, or you can listen for any change of any kind to a reference.

These handlers for responding to Realtime Database events are available:

Node.js

  • onValueWritten() Triggered when data is created, updated, or deleted in Realtime Database.
  • onValueCreated() Only triggered when data is created in Realtime Database.
  • onValueUpdated() Only triggered when data is updated in Realtime Database.
  • onValueDeleted() Only triggered when data is deleted in Realtime Database.

Python

  • on_value_written() Triggered when data is created, updated, or deleted in Realtime Database.
  • on_value_created() Only triggered when data is created in Realtime Database.
  • on_value_updated() Only triggered when data is updated in Realtime Database.
  • on_value_deleted() Only triggered when data is deleted in Realtime Database.

Import required modules

In your function source, you must import SDK modules that you want to use. For this sample, it is necessary to import HTTP and Realtime Database modules along with the Firebase Admin SDK module for writing to Realtime Database.

Node.js

// The Cloud Functions for Firebase SDK to setup triggers and logging.
const {onRequest} = require("firebase-functions/v2/https");
const {onValueCreated} = require("firebase-functions/v2/database");
const {logger} = require("firebase-functions");

// The Firebase Admin SDK to access the Firebase Realtime Database.
const admin = require("firebase-admin");
admin.initializeApp();
index.js

Python

# The Cloud Functions for Firebase SDK to create Cloud Functions and set up triggers.
from firebase_functions import db_fn, https_fn

# The Firebase Admin SDK to access the Firebase Realtime Database.
from firebase_admin import initialize_app, db

app = initialize_app()
main.py

Specify instance and path

To control when and where your function should trigger, configure your function with a path and optionally a Realtime Database instance. If you do not specify an instance, the function listens to the all Realtime Database instances in the function region. You may also specify a Realtime Database instance pattern to deploy to a selective subset of instances in the same region.

For example:

Node.js

// All Realtime Database instances in default function region us-central1 at path "/user/{uid}"
// There must be at least one Realtime Database present in us-central1.
const onWrittenFunctionDefault = onValueWritten("/user/{uid}", (event) => {
  // …
});

// Instance named "my-app-db-2", at path "/user/{uid}".
// The "my-app-db-2" instance must exist in this region.
const OnWrittenFunctionInstance = onValueWritten(
  {
    ref: "/user/{uid}",
    instance: "my-app-db-2"
    // This example assumes us-central1, but to set location:
    // region: "europe-west1"
  },
  (event) => {
    // …
  }
);

// Instance with "my-app-db-" prefix, at path "/user/{uid}", where uid ends with @gmail.com.
// There must be at least one Realtime Database with "my-app-db-*" prefix in this region.
const onWrittenFunctionInstance = onValueWritten(
  {
    ref: "/user/{uid=*@gmail.com}",
    instance: "my-app-db-*"
    // This example assumes us-central1, but to set location:
    // region: "europe-west1"
  },
  (event) => {
    // …
  }
);

Python

# All Realtime Database instances in default function region us-central1 at path "/user/{uid}"
# There must be at least one Realtime Database present in us-central1.
@db_fn.on_value_written(r"/user/{uid}")
def onwrittenfunctiondefault(event: db_fn.Event[db_fn.Change]):
    # ...
    pass

# Instance named "my-app-db-2", at path "/user/{uid}".
# The "my-app-db-2" instance must exist in this region.
@db_fn.on_value_written(
    reference=r"/user/{uid}",
    instance="my-app-db-2",
    # This example assumes us-central1, but to set location:
    # region="europe-west1",
)
def on_written_function_instance(event: db_fn.Event[db_fn.Change]):
    # ...
    pass

# Instance with "my-app-db-" prefix, at path "/user/{uid}", where uid ends with @gmail.com.
# There must be at least one Realtime Database with "my-app-db-*" prefix in this region.
@db_fn.on_value_written(
    reference=r"/user/{uid=*@gmail.com}",
    instance="my-app-db-*",
    # This example assumes us-central1, but to set location:
    # region="europe-west1",
)
def on_written_function_instance(event: db_fn.Event[db_fn.Change]):
    # ...
    pass

These parameters direct your function to handle writes at a certain path within the Realtime Database instance.

Path specifications match all writes that touch a path, including writes that happen anywhere below it. If you set the path for your function as /foo/bar, it matches events at both of these locations:

 /foo/bar
 /foo/bar/baz/really/deep/path

In either case, Firebase interprets that the event occurs at /foo/bar, and the event data includes the old and new data at /foo/bar. If the event data might be large, consider using multiple functions at deeper paths instead of a single function near the root of your database. For the best performance, only request data at the deepest level possible.

Wildcarding and capturing

You can use {key}, {key=*}, {key=prefix*}, {key=*suffix} for capturing. *, prefix*, *suffix for single-segment wildcarding. Note: ** represents multi-segment wildcarding, which Realtime Database does not support. See Understand path patterns.

Path wildcarding. You can specify a path component as a wildcard:

  • Using asterisk, *. For example, foo/* matches any children one level of the node hierarchy below foo/.
  • Using a segment containing exactly asterisk, *. For example, foo/app*-us matches any child segments below foo/ with app prefix and -us suffix.

Paths with wildcards can match multiple events from, for example, a single write. An insert of

{
  "foo": {
    "hello": "world",
    "firebase": "functions"
  }
}

matches the path "/foo/*" twice: once with "hello": "world" and again with "firebase": "functions".

Path capturing. You can capture path matches into named variables to be used in your function code (e.g. /user/{uid}, /user/{uid=*-us}).

The values of the capture variables are available within the database.DatabaseEvent.params object of your function.

Instance wildcarding. You can also specify an instance component using wildcarding. A instance wildcard can have prefix, suffix or both (e.g. my-app-*-prod).

Wildcard and capture reference

With Cloud Functions (2nd gen) and Realtime Database, a pattern can be used when specifying ref and instance. Each trigger interface will have the following options for scoping a function:

Specifying ref Specifying instance Behavior
Single (/foo/bar) Not specifying Scopes handler to all instances in the function region.
Single (/foo/bar) Single (‘my-new-db') Scopes handler to the specific instance in the function region.
Single (/foo/bar) Pattern (‘inst-prefix*') Scopes handler to all instances that match the pattern in the function region.
Pattern (/foo/{bar}) Not specifying Scopes handler to all instances in the function region.
Pattern (/foo/{bar}) Single (‘my-new-db') Scopes handler to the specific instance in the function region.
Pattern (/foo/{bar}) Pattern (‘inst-prefix*') Scopes handler to all instances that match the pattern in the function region.

Handle event data

When a Realtime Database event triggers, it passes an Event object to your handler function. This object has a data property, which, for creation and deletion events, contains a snapshot of the data created or deleted.

In this example, the function retrieves the data for the referenced path, converts the string at that location to uppercase, and writes that modified string to the database:

Node.js

// Listens for new messages added to /messages/:pushId/original and creates an
// uppercase version of the message to /messages/:pushId/uppercase
// for all databases in 'us-central1'
exports.makeuppercase = onValueCreated(
    "/messages/{pushId}/original",
    (event) => {
    // Grab the current value of what was written to the Realtime Database.
      const original = event.data.val();
      logger.log("Uppercasing", event.params.pushId, original);
      const uppercase = original.toUpperCase();
      // You must return a Promise when performing
      // asynchronous tasks inside a function, such as
      // writing to the Firebase Realtime Database.
      // Setting an "uppercase" sibling in the
      // Realtime Database returns a Promise.
      return event.data.ref.parent.child("uppercase").set(uppercase);
    },
);
index.js

Python

@db_fn.on_value_created(reference="/messages/{pushId}/original")
def makeuppercase(event: db_fn.Event[Any]) -> None:
    """Listens for new messages added to /messages/{pushId}/original and
    creates an uppercase version of the message to /messages/{pushId}/uppercase
    """

    # Grab the value that was written to the Realtime Database.
    original = event.data
    if not isinstance(original, str):
        print(f"Not a string: {event.reference}")
        return

    # Use the Admin SDK to set an "uppercase" sibling.
    print(f"Uppercasing {event.params['pushId']}: {original}")
    upper = original.upper()
    parent = db.reference(event.reference).parent
    if parent is None:
        print("Message can't be root node.")
        return
    parent.child("uppercase").set(upper)
main.py

Reading the previous value

For write or update events, the data property is a Change object that contains two snapshots that represent the data state before and after the triggering event. The Change object has a before property that lets you inspect what was saved to Realtime Database before the event and an after property that represents the state of the data after the event happened.

For example, the before property can be used to make sure the function only uppercases text when it is first created:

Node.js

  exports makeUppercase = onValueWritten("/messages/{pushId}/original", (event) => {
        // Only edit data when it is first created.
        if (event.data.before.exists()) {
          return null;
        }
        // Exit when the data is deleted.
        if (!event.data.after.exists()) {
          return null;
        }
        // Grab the current value of what was written to the Realtime Database.
        const original = event.data.after.val();
        console.log('Uppercasing', event.params.pushId, original);
        const uppercase = original.toUpperCase();
        // You must return a Promise when performing asynchronous tasks inside a Functions such as
        // writing to the Firebase Realtime Database.
        // Setting an "uppercase" sibling in the Realtime Database returns a Promise.
        return event.data.after.ref.parent.child('uppercase').set(uppercase);
      });

Python

@db_fn.on_value_written(reference="/messages/{pushId}/original")
def makeuppercase2(event: db_fn.Event[db_fn.Change]) -> None:
    """Listens for new messages added to /messages/{pushId}/original and
    creates an uppercase version of the message to /messages/{pushId}/uppercase
    """

    # Only edit data when it is first created.
    if event.data.before is not None:
        return

    # Exit when the data is deleted.
    if event.data.after is None:
        return

    # Grab the value that was written to the Realtime Database.
    original = event.data.after
    if not hasattr(original, "upper"):
        print(f"Not a string: {event.reference}")
        return

    # Use the Admin SDK to set an "uppercase" sibling.
    print(f"Uppercasing {event.params['pushId']}: {original}")
    upper = original.upper()
    parent = db.reference(event.reference).parent
    if parent is None:
        print("Message can't be root node.")
        return
    parent.child("uppercase").set(upper)
main.py