Authentication trigger functions in Firebase - Time & Space Complexity

Time Complexity: Authentication trigger functions

O(n)

Understanding Time Complexity

When using authentication trigger functions in Firebase, it's important to understand how the time to run these functions changes as more users sign up or log in.

We want to know how the function's work grows when many users trigger it.

Scenario Under Consideration

Analyze the time complexity of the following Firebase authentication trigger function.

exports.onUserCreate = functions.auth.user().onCreate((user) => {
  const userId = user.uid;
  return admin.firestore().collection('profiles').doc(userId).set({
    email: user.email,
    createdAt: admin.firestore.FieldValue.serverTimestamp()
  });
});

This function runs when a new user signs up. It creates a profile document in Firestore for that user.

Identify Repeating Operations

Look for repeated work inside the function.

• Primary operation: Writing one document to Firestore per user creation.
• How many times: Once per user sign-up event.

How Execution Grows With Input

Each new user triggers one write operation to Firestore.

Input Size (n)	Approx. Operations
10	10 writes
100	100 writes
1000	1000 writes

Pattern observation: The work grows directly with the number of users signing up.

Final Time Complexity

Time Complexity: O(n)

This means the time to handle all sign-ups grows linearly with the number of new users.

Common Mistake

[X] Wrong: "The function runs once and handles all users at once."

[OK] Correct: Each user sign-up triggers the function separately, so the work adds up with each new user.

Interview Connect

Understanding how trigger functions scale helps you design systems that handle many users smoothly and predict how your app behaves as it grows.

Self-Check

What if the function also read multiple documents from Firestore for each new user? How would the time complexity change?

Practice

1. What does the Firebase Authentication trigger function onCreate do?

easy

A. It sends a password reset email.

B. It deletes a user from the database.

C. It runs automatically when a new user signs up.

D. It updates user profile information.

Solution

1. Step 1: Understand the purpose of onCreate

   The onCreate trigger runs when a new user account is created in Firebase Authentication.

2. Step 2: Match the trigger to the correct action

   Since it runs on new user sign-up, it does not delete users or send emails directly.

3. Final Answer:

   It runs automatically when a new user signs up. -> Option C

4. Quick Check:

   onCreate = New user signup trigger [OK]

Hint: Remember: onCreate = new user signup trigger [OK]

Common Mistakes:

• Confusing onCreate with onDelete trigger
• Thinking onCreate sends emails automatically
• Assuming onCreate updates user data

2. Which of the following is the correct syntax to define a Firebase Authentication trigger function for user deletion in Node.js?

easy

A. functions.auth.user().onCreate((user) => { /* code */ });

B. exports.userDeleted = functions.auth.user().onDelete((user) => { /* code */ });

C. exports.userDeleted = functions.auth.user().onRemove((user) => { /* code */ });

D. functions.auth.user().delete((user) => { /* code */ });

Solution

1. Step 1: Identify the correct trigger for user deletion

   The correct trigger for user deletion is onDelete attached to functions.auth.user().

2. Step 2: Check the syntax for exporting the function

   The function should be exported using exports.functionName = ... syntax.

3. Final Answer:

   exports.userDeleted = functions.auth.user().onDelete((user) => { /* code */ }); -> Option B

4. Quick Check:

   onDelete trigger syntax = exports.userDeleted = functions.auth.user().onDelete((user) => { /* code */ }); [OK]

Hint: Use exports.functionName = functions.auth.user().onDelete(...) [OK]

Common Mistakes:

• Using onCreate instead of onDelete for deletion
• Using non-existent onRemove trigger
• Not exporting the function properly

3. Given the following Firebase Authentication trigger function, what will be logged when a user signs up?

exports.welcomeUser = functions.auth.user().onCreate((user) => {
  console.log(`Welcome, ${user.email}!`);
});

medium

A. Welcome, undefined!

B. Welcome, user.email!

C. No output, function does not run on sign-up.

D. Welcome, [e-mail]!

Solution

1. Step 1: Understand the onCreate trigger behavior

   The function runs automatically when a new user signs up, receiving the user object with an email property.

2. Step 2: Analyze the console.log statement

   The template string inserts the user's email, so it logs "Welcome, [e-mail]!" if the user's email is [e-mail].

3. Final Answer:

   Welcome, [e-mail]! -> Option D

4. Quick Check:

   onCreate logs user email correctly [OK]

Hint: onCreate passes user object with email property [OK]

Common Mistakes:

• Assuming user.email is undefined
• Thinking function does not run on sign-up
• Misreading template string syntax

4. Identify the error in this Firebase Authentication trigger function code:

exports.deleteUserData = functions.auth.user().onDelete(user => {
  const uid = user.uid;
  admin.database().ref(`/users/${uid}`).remove();
});

medium

A. admin is not initialized or imported.

B. Incorrect trigger function; should use onCreate instead of onDelete.

C. Missing return statement for the database operation.

D. The user parameter should be destructured as { uid }.

Solution

1. Step 1: Check for admin SDK initialization

   The code uses admin.database() but does not show admin being imported or initialized, which causes runtime errors.

2. Step 2: Verify other parts of the code

   The trigger and user parameter usage are correct; missing return is not mandatory but recommended.

3. Final Answer:

   admin is not initialized or imported. -> Option A

4. Quick Check:

   admin SDK must be initialized before use [OK]

Hint: Always import and initialize admin SDK before database calls [OK]

Common Mistakes:

• Confusing onDelete with onCreate trigger
• Ignoring admin SDK initialization
• Thinking return statement is mandatory

5. You want to send a welcome email only to users who sign up with an email ending in @example.com. Which code snippet correctly implements this using Firebase Authentication trigger functions?

hard

A. exports.sendWelcomeEmail = functions.auth.user().onCreate((user) => {
if (user.email.endsWith('@example.com')) {
sendEmail(user.email);
}
});

B. exports.sendWelcomeEmail = functions.auth.user().onDelete((user) => {
if (user.email.includes('@example.com')) {
sendEmail(user.email);
}
});

C. exports.sendWelcomeEmail = functions.auth.user().onCreate((user) => {
if (user.email === '@example.com') {
sendEmail(user.email);
}
});

D. exports.sendWelcomeEmail = functions.auth.user().onCreate((user) => {
if (user.email.indexOf('@example.com') === 0) {
sendEmail(user.email);
}
});

Solution

1. Step 1: Choose the correct trigger for new user sign-up

   Use onCreate to run code when a user signs up, not onDelete.

2. Step 2: Check the email condition for domain matching

   Use endsWith('@example.com') to check if the email ends with the domain. Using includes or equality check is incorrect here.

3. Final Answer:

   exports.sendWelcomeEmail = functions.auth.user().onCreate((user) => { if (user.email.endsWith('@example.com')) { sendEmail(user.email); } }); -> Option A

4. Quick Check:

   Use onCreate + endsWith() for domain check [OK]

Hint: Use onCreate and endsWith('@domain.com') to filter emails [OK]

Common Mistakes:

• Using onDelete instead of onCreate
• Checking email equality instead of endsWith
• Using indexOf === 0 instead of endsWith