Firebase Action Listener

Since most of the actions and logic of the plugin's communication with Firebase happens on the Front-end (the user's browser), Bubble has no way, yet, to wait for a front-end action to finish before another starts.

It also does not allow to return values from front-end operations. That's why those actions return no values to a workflow on Bubble.

To mitigate that, plugin developer often use elements as ways to listen to actions and to trigger events on their completion. That's the goal of the Firebase Action Listener: to inform when an action finishes running (e.g. when a new document creation if confirmed) and allow you do do things before that.

This element is crucial for when you need to perform actions in order, like, for instance, when you need to create a document an only then create another, that maybe stores a reference to the one you created earlier.

---

Settings

The Action Listener element has only one setting, the ID you want to define for it. By defining this ID, and providind the same ID on actions, you link them together so that those actino trigger them.

If you leave the ID blank, the elemet will work as a general listener. When you run an action that also has no trigger ID defined, it will trigger all listeners with blank IDs.

So be carefull with ID management for listener. We suggest to always provide one.

---

States and Values

New Document ID

The ID of the last document creation this element was listening for.

User ID

The ID of a user created or authenticated by a signup or log in action this element was listening for.

User Email

The Email of a user created or authenticated by a signup or log in action this element was listening for.

Uploaded File URL

The last file URL generated by an Upload File Base64 action.

Updated Document ID

The ID of the last document update action this element was listening for.

Error Message

If an error occurs, the error message will be stored on this state.

---

Events

Document created

Triggered when the "create a new document" actions runs. The ID of the newly created document will be available on the "new document id" state.

Document updated

Triggered when the "updated a document" actions runs. The ID of the updated document will be available on the "updated document id" state.

Document deleted

Triggered when the "delete a document" actions runs.

List operation finished

Triggered when list operations like "update a list of documents" or "delete a list of document" runs.

User signed up

Triggers when the "Sign the User Up", "Log the User in with Google", "Log the User in with Facebook" or "Log the User in with GitHub" actions create a new user.

User logged in

Triggers when the "Log the User In", "Log the User in with Google", "Log the User in with Facebook" or "Log the User in with GitHub" actions start a new session for a user that has previously signed up.

User logged out

Triggers when the "Log the User Out" action finishes running and ends the user's session.

User updated

Triggers when the any of the updated user functions runs, like change email, password or profile.

File uploaded

Triggers when the "Upload file base64" action completes an upload. It does not trigger on uploads from Storage Button Uploader elements.

File deleted

Triggers when a "Delete uploaded file" action is completed.

Triggers when the any of the update user functions runs (Update User's Profile, Password, Email or Email verification).

Batch Operation Committed

Triggers when a "Batch operation commit" action is completed.

Error in action

Triggers if something went wrong in a front-end action, storing the "error message" as a state.