Firestore trigger functions in Firebase - Step-by-Step Execution

Process Flow - Firestore trigger functions

Event in Firestore

↓

Trigger Function Activated

↓

Read Event Data

↓

Perform Logic (e.g., update, notify)

↓

Write Back or Side Effects

↓

Function Ends

When a Firestore event happens, the trigger function runs, reads event data, does work, then finishes.

Execution Sample

Firebase

exports.onUserCreate = functions.firestore
  .document('users/{userId}')
  .onCreate((snap, context) => {
    const newUser = snap.data();
    console.log('New user:', newUser.name);
  });

This function runs when a new user document is created and logs the user's name.

Process Table

Step	Event	Trigger Function Action	Data Accessed	Output/Effect
1	New document created in 'users/abc123'	Function onUserCreate activates	snap.data() returns {name: 'Alice'}	Logs: 'New user: Alice'
2	Function completes	No further action	No new data	Function ends

💡 Function ends after processing the create event and logging user name

Status Tracker

Variable	Start	After Step 1	Final
snap	undefined	DocumentSnapshot	DocumentSnapshot
newUser	undefined	{name: 'Alice'}	{name: 'Alice'}

Key Moments - 2 Insights

Why does the function only run when a new document is created?

Because the trigger uses .onCreate(), it activates only on document creation events as shown in execution_table step 1.

What is snap.data() and why do we use it?

snap.data() gives the content of the changed document. In step 1, it returns the new user's data so we can use it inside the function.

Visual Quiz - 3 Questions

Look at the execution table, what data does snap.data() return at step 1?

A undefined

B {name: 'Alice'}

C {userId: 'abc123'}

D null

💡 Hint

Check the 'Data Accessed' column in execution_table row for step 1

At which step does the function finish running?

A Step 1

B Before Step 1

C Step 2

D Never finishes

💡 Hint

Look at the 'Output/Effect' column in execution_table for step 2

If the trigger was changed to .onUpdate(), when would the function run?

A When a document is updated

B When a document is deleted

C When a document is created

D When Firestore starts

💡 Hint

Recall the meaning of .onUpdate() triggers in Firestore functions

Concept Snapshot

Firestore trigger functions run automatically on database events.
Use .onCreate(), .onUpdate(), or .onDelete() to specify event type.
Function receives snapshot with event data.
Perform logic inside function, then finish.
Useful for reacting to data changes in real time.

Full Transcript

Firestore trigger functions activate automatically when specific events happen in your Firestore database, like creating, updating, or deleting documents. For example, a function with .onCreate() runs only when a new document is added. Inside the function, you get a snapshot of the changed document's data using snap.data(). You can then perform actions like logging, updating other data, or sending notifications. After the function finishes its work, it ends. This lets your app respond instantly to database changes without manual checks.

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