Firestore trigger functions in Firebase - Mini Project: Build & Apply

Firestore Trigger Functions

📖 Scenario: You are building a simple Firebase backend that reacts to changes in a Firestore database. You want to create functions that automatically run when documents are created or updated in a specific collection.

🎯 Goal: Build Firestore trigger functions that run when a document is created and when a document is updated in the users collection.

📋 What You'll Learn

Create a Firestore trigger function for document creation in the users collection.

Create a Firestore trigger function for document updates in the users collection.

Log a message inside each trigger function indicating the event type and document ID.

💡 Why This Matters

🌍 Real World

Automatically respond to database changes, such as sending notifications or updating related data.

💼 Career

Understanding Firestore triggers is essential for backend development with Firebase and building reactive cloud applications.

1

Set up Firebase Functions and import Firestore

Write the code to import functions from firebase-functions and initialize Firestore by importing admin from firebase-admin and calling admin.initializeApp().

Firebase

# Your code here

Hint

Use require to import modules and call admin.initializeApp() to start Firebase Admin SDK.

2

Create a Firestore trigger for document creation

Create a Firestore trigger function called onUserCreate that runs when a document is created in the users collection. Use functions.firestore.document('users/{userId}').onCreate and log the message 'User created:' followed by the userId parameter.

Firebase

const functions = require('firebase-functions');
const admin = require('firebase-admin');
admin.initializeApp();

// Your code here

Hint

Use context.params.userId to get the document ID from the path.

3

Create a Firestore trigger for document updates

Create a Firestore trigger function called onUserUpdate that runs when a document is updated in the users collection. Use functions.firestore.document('users/{userId}').onUpdate and log the message 'User updated:' followed by the userId parameter.

Firebase

const functions = require('firebase-functions');
const admin = require('firebase-admin');
admin.initializeApp();

exports.onUserCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => {
  const userId = context.params.userId;
  console.log('User created:', userId);
});

// Your code here

Hint

Use onUpdate and context.params.userId to get the document ID.

4

Export both trigger functions

Ensure both onUserCreate and onUserUpdate functions are exported from the module so Firebase can deploy them.

Firebase

const functions = require('firebase-functions');
const admin = require('firebase-admin');
admin.initializeApp();

exports.onUserCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => {
  const userId = context.params.userId;
  console.log('User created:', userId);
});

exports.onUserUpdate = functions.firestore.document('users/{userId}').onUpdate((change, context) => {
  const userId = context.params.userId;
  console.log('User updated:', userId);
});

// Your code here

Hint

Make sure both functions are assigned to exports so Firebase can find them.

Practice

1. What does a Firestore trigger function do in a Firebase project?

easy

A. Deletes Firestore data without any event

B. Manually updates Firestore data when called

C. Creates a new Firestore database

D. Automatically runs code when data changes in Firestore

Solution

1. Step 1: Understand Firestore triggers

   Firestore triggers are special functions that run automatically when data changes in Firestore.

2. Step 2: Identify the trigger's purpose

   They help keep your app reactive by running code on create, update, or delete events without manual calls.

3. Final Answer:

   Automatically runs code when data changes in Firestore -> Option D

4. Quick Check:

   Firestore triggers = automatic code run on data change [OK]

Hint: Triggers run code automatically on Firestore data changes [OK]

Common Mistakes:

• Thinking triggers run manually
• Confusing triggers with database creation
• Assuming triggers delete data without events

2. Which of the following is the correct syntax to create a Firestore trigger for document creation in Node.js Firebase Functions?

easy

A. exports.onCreate = functions.firestore.document('users').onCreate((snap, context) => { });

B. exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { });

C. functions.firestore.onCreate('users/{userId}', (snap, context) => { });

D. functions.firestore.document('users/{userId}').create((snap, context) => { });

Solution

1. Step 1: Recall Firestore trigger syntax

   The correct syntax uses exports, functions.firestore.document(path).onCreate(handler).

2. Step 2: Match syntax to options

   exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { }); matches this pattern exactly with document path and onCreate event.

3. Final Answer:

   exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { }); -> Option B

4. Quick Check:

   Correct Firestore onCreate syntax = exports.onCreate = functions.firestore.document('users/{userId}').onCreate((snap, context) => { }); [OK]

Hint: Use exports with document(path).onCreate(handler) for create triggers [OK]

Common Mistakes:

• Missing exports keyword
• Using onCreate directly on firestore without document
• Wrong method name like create instead of onCreate

3. Given this Firestore trigger function, what will be logged when a document is updated?

exports.logUpdate = functions.firestore.document('posts/{postId}').onUpdate((change, context) => {
  const before = change.before.data();
  const after = change.after.data();
  console.log('Title before:', before.title);
  console.log('Title after:', after.title);
});

medium

A. Logs the title before and after the update

B. Logs only the new title after update

C. Logs only the old title before update

D. Throws an error because change.before is undefined

Solution

1. Step 1: Understand onUpdate trigger parameters

   The onUpdate trigger receives a change object with before and after snapshots of the document.

2. Step 2: Analyze the console logs

   The code logs before.title and after.title, so both old and new titles are printed.

3. Final Answer:

   Logs the title before and after the update -> Option A

4. Quick Check:

   onUpdate logs before and after data [OK]

Hint: onUpdate provides before and after data snapshots [OK]

Common Mistakes:

• Assuming only new data is available
• Thinking change.before is undefined
• Confusing onUpdate with onCreate

4. Identify the error in this Firestore trigger function code:

exports.deleteUser = functions.firestore.document('users/{userId}').onDelete((snap, context) => {
  const userData = snap.data;
  console.log('Deleted user:', userData.name);
});

medium

A. Missing async keyword for the function

B. onDelete trigger cannot be used on 'users/{userId}' path

C. snap.data should be snap.data() to get document data

D. context parameter is not allowed in onDelete triggers

Solution

1. Step 1: Check how to access document data

   Firestore document snapshot data is accessed by calling snap.data(), not snap.data property.

2. Step 2: Identify the error in code

   The code uses snap.data without parentheses, causing undefined userData and runtime error.

3. Final Answer:

   snap.data should be snap.data() to get document data -> Option C

4. Quick Check:

   Use snap.data() method to access document data [OK]

Hint: Use snap.data() method, not snap.data property [OK]

Common Mistakes:

• Using snap.data instead of snap.data()
• Thinking onDelete can't use context parameter
• Assuming async is always required

5. You want to create a Firestore trigger that updates a user's profile summary whenever their profile document changes. Which approach correctly ensures the trigger only runs when the 'bio' field changes, avoiding infinite loops?

hard

A. Use onUpdate trigger and compare change.before.data().bio with change.after.data().bio before updating

B. Use onWrite trigger and update the document unconditionally inside the trigger

C. Use onCreate trigger to update bio field after document creation

D. Use onUpdate trigger and update the document without checking any field changes

Solution

1. Step 1: Choose the right trigger for updates

   onUpdate triggers run on any document update, suitable for detecting changes.

2. Step 2: Prevent infinite loops by checking field changes

   Compare bio field before and after update; only proceed if bio changed to avoid recursive updates.

3. Final Answer:

   Use onUpdate trigger and compare change.before.data().bio with change.after.data().bio before updating -> Option A

4. Quick Check:

   Check field changes in onUpdate to avoid loops [OK]

Hint: Compare before and after fields in onUpdate to avoid loops [OK]

Common Mistakes:

• Using onWrite and updating unconditionally causing loops
• Using onCreate which triggers only once
• Not checking field changes before updating