Overview
This node interacts with Firebase Authentication to retrieve the unique user ID (uid) associated with a given email address. It is useful in scenarios where you need to map user emails to their Firebase Authentication identifiers, such as syncing user data, managing user permissions, or integrating Firebase Auth users with other systems.
For example, if you have a list of user emails and want to fetch their corresponding Firebase uids for further processing or validation, this node can automate that lookup.
Properties
| Name | Meaning |
|---|---|
| The email address of the user whose uid you want to retrieve. This is a required string input. |
Output
The node outputs the original input data augmented with an additional field:
uid: The unique identifier of the user in Firebase Authentication corresponding to the provided email.
The output JSON structure for each item will be the same as the input but with the added uid property inside the json object.
If the node encounters an error for a particular item and "Continue On Fail" is enabled, it outputs an error object alongside the original data for that item.
Dependencies
- Requires a Firebase project with Firebase Authentication enabled.
- Needs credentials containing:
- A private key,
- Project ID,
- Client email,
which are used to initialize the Firebase Admin SDK.
- The node depends on the Firebase Admin SDK (
firebase-adminpackage) to communicate with Firebase services.
Troubleshooting
Common issues:
- Invalid or missing Firebase credentials will cause initialization failure.
- Providing an email that does not exist in Firebase Auth will result in an error when fetching the user.
- Improper formatting of the private key (e.g., missing newline characters) may cause authentication errors.
Error messages:
- Errors from Firebase Admin SDK typically indicate issues like "user not found" or "permission denied".
- If "Continue On Fail" is disabled, the node execution stops at the first error.
- To handle errors gracefully, enable "Continue On Fail" so that errors are returned per item without stopping the entire workflow.