Firebase Functions：匿名用户关联邮箱后如何通过触发器同步邮箱至用户文档

Great question—this is a super common scenario when working with Firebase's anonymous authentication flow, and you’re right to want to avoid client-side updates to keep your user data consistent. Let’s break down the answers to your questions clearly:

1. Does Firebase provide an auth.user().onUpdate trigger? #

Absolutely! This is exactly the tool you need here. Firebase Cloud Functions includes an Auth trigger that fires whenever a user’s authentication record is updated—including when an anonymous user links an email/password credential (which adds the email field to their Auth profile).

2. How to sync the email to Firestore without client code? #

Use the auth.user().onUpdate Cloud Function to listen for the email being added to the Auth user, then write that email directly to the corresponding Firestore user document. Here’s a working example in JavaScript:

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

exports.syncEmailToUserDocument = functions.auth.user().onUpdate(async (change, context) => {
  const updatedUser = change.after;
  const originalUser = change.before;

  // Only run if the email was just added (or changed)
  if (originalUser.email !== updatedUser.email) {
    const userDoc = admin.firestore().collection("users").doc(updatedUser.uid);
    
    // Use merge: true to avoid overwriting existing user data
    await userDoc.set(
      {
        email: updatedUser.email,
        emailVerified: updatedUser.emailVerified,
        lastAuthUpdate: admin.firestore.FieldValue.serverTimestamp()
      },
      { merge: true }
    );

    functions.logger.info(`Successfully synced email ${updatedUser.email} to user document ${updatedUser.uid}`);
  }

  return null;
});

Key details about this function: #

• It only triggers when the user’s email changes (so it won’t run on irrelevant Auth updates like password resets)
• Uses merge: true to preserve any existing data in the Firestore user document (like display name, preferences, etc.)
• Runs entirely on Firebase’s backend, so no client-side code is needed
• Has full admin access via the Firebase Admin SDK, so it can write to Firestore without permission issues

3. Can this be done with only Firestore triggers? #

No, this isn’t feasible. Firestore triggers only fire when a Firestore document is created, updated, or deleted. When an anonymous user links an email credential, the change happens in Firebase Auth—not in Firestore. There’s no automatic Firestore event generated by this Auth action, so a Firestore trigger wouldn’t have anything to listen for. The only way to trigger a Firestore update here without client code would be to use the Auth trigger we discussed above.

Bonus Tips #

• Add error handling with try/catch blocks to log and handle any failures (e.g., Firestore write errors)
• If you also create the Firestore user document when the anonymous user first signs up, use the auth.user().onCreate trigger for that initial creation
• For users who might update their email later (not just link from anonymous), the same function will handle that scenario too, since it checks for any change in the email field

内容的提问来源于stack exchange，提问作者Eric Larson