Sign the User Up
This action creates a new user account on Firebase Authentication, with email/password authentication, as well as a new Document on Firestore Database, linked to the user.
The standard is to link the user to a "users" collection.
Inputs and Settings
Email
The email of the the new user.
Password
The password for the new user to log in.
The only limitation for the password, from Firebase Auth's, is that it must be at least 6 characters long. But it is recommended to apply password security standards, like having at least a uppercase letter, special character and number.
Password Confirmation
The confirmation of the password defined by the user. If th "password" and "password confirmation" don't match, it will result in an error.
Trigger ID (optional)
This will link the action with a Action Listener of the same ID.
If left blank, all listener on the page with blank ID's will be triggered at the same time, so we suggest to always define a Trigger ID.
When the function finishes running, it will trigger the User Signed Up event, storing the new User ID and User Email on the listener's states.
Profile and Other User Data
Copy profile data into Firestore collection
If you check this option, the user's profile data will be stored not only on the user, from the Firebase Authentication service, but also on the user's document.
It is recommended to left it checked, since it gives more flexibility while accessing this information, as well as utilizing it on queries and filters for users.
Display Name
The profile name of the user, associated with the account.
Photo URL
The URL of the profile picture for the user. This profile picture is stored directly on Firebase Authentication, and not on Firebase Storage.
Phone Number (E.164 format)
The users phone number, that must be provided in the E.164 format, which means a number without spaces and with a plus sign on front of the country code at the begining (e.g. +14155552671).
Users Collection
The name or ID of the collection where user's should be stored in. A document will be created with the same ID of the newly created user account.
Fields
Since a new document is being created, you can store data in it the same way it is done to any new document.
When you create a document on Firestore, you must inform which fields and which content each will have on it's structure, in JSON format. This input allows you to set as many fields as you want.
For each field you must specify the "key" and the "value" that will be stored. For instance, you might want to store a "status" for the new user, of "active", to control access to your app. You'd need to define the "key" = "status" and the "value" = "active".
Field Types
For each key/value pair you define and provide a value on the Fields list, you must provide the same key, but with the type of the value, on the Field Types input. That allows the plugin to turn the texts being fed into the plugin into corresponding values on the JSON structure sent to Firestore.
If the number of Fields and Field Types don't match, the action will result in an error.
See the field types table to see which types are currently supported by the plugin and how to define them.
Triggered events
Those events are triggered by an Action Listener with the same ID as the Trigger ID provided on the action.
User Signed Up (if the action was successful)
Error in Action (if an error occurs)
Stored values on the listener
User ID
The ID of the user and document created by the action.
User Email
The email of the user account created by the action.
Error Message
If an error occurs, you can check its details on this state on the action listener.
Last updated