Actions7
Overview
This node integrates with the Firebase Admin SDK to manage user authentication data. Specifically, the "List All Users" operation retrieves a list of users from a Firebase project, supporting pagination and limiting the number of results returned.
Common scenarios where this node is beneficial include:
- Synchronizing user data from Firebase to other systems.
- Auditing or reporting on registered users.
- Managing large user bases by fetching users in batches.
For example, you can use this node to fetch up to 1000 users at a time and paginate through all users by using the next page token, enabling efficient processing of user lists in your workflows.
Properties
| Name | Meaning |
|---|---|
| Max Results | Maximum number of users to return (minimum 1, maximum 1000). Limits the size of each batch. |
| Next Page Token | Token used for pagination to retrieve the next set of users. Should be empty for the first request. |
Output
The output JSON contains user data structured as follows:
users: An array of user objects, each representing a Firebase user.- Each user object includes fields such as
uid,email,displayName,phoneNumber,emailVerified,disabled,creationTime, andlastSignInTime. - Date/time fields (
creationTimeandlastSignInTime) are ISO 8601 strings. - Metadata and provider-specific data are removed for clarity.
- If pagination is used, the response may also include a
pageTokenfield (not explicitly shown but typically part of Firebase's listUsers response).
No binary data is output by this operation.
Dependencies
- Requires a valid Firebase service account JSON credential with appropriate permissions to access Firebase Authentication.
- The node uses the Firebase Admin SDK internally.
- No additional environment variables are required beyond the provided credentials.
Troubleshooting
- Invalid service account JSON format: Ensure the service account JSON is correctly formatted and pasted without extra characters.
- Failed to initialize Firebase: Verify that the service account has the necessary permissions and the JSON is valid.
- Invalid custom claims JSON format (relevant for other operations): When providing custom claims, ensure the JSON string is valid.
- Pagination issues: If the next page token is invalid or expired, the node may fail to fetch subsequent pages. Always use the token returned from the previous call.
- Max Results out of range: Values must be between 1 and 1000; otherwise, the node will throw an error.
If the node encounters errors during execution and "Continue On Fail" is enabled, it will output an error message in the JSON instead of stopping the workflow.