Best practices for connecting user to their data

I’m building a flashcard study app with specific data for each user.I would like anyone with experience to share the best way of connecting user to their data. I’m using firebase auth as the auth backend and Firestore database to store the data. Here’s what I came up with to connect user to their data:

Data structure: a collection named USERS containing documents with the user’s data stores all of user’s data. The id for each document is the same ID as the users ID created by firebase auth.

Connecting the data: through Get current user (Firebase Auth) flow function retrieve current user ID. Use the ID to build the HTTP request URL to retrieve the info from the specific user.

In your experience is that the best way? I also have to figure out how to set security rules properly. Any thoughts on that would be appreciated as well.

Hey, how did you connect or create “The id for each document is the same ID as the users ID created by firebase auth.”?

I have been looking around everywhere but cannot find the solution

When you enable authentication through firebase, your app authenticates to firebase through either one of these flow functions: Get current user (Firebase auth) or Email & password authentication (Firebase Auth). One of the outputs arguments is ``ùid``` which holds the ID for that specific user. You need to use this uid to create the documents.

I have managed to get the the ID from the UID, thank you. However, I don’t know how to assign the ID get to the document ID created. most of the documents that I am creating at the moment have auto-IDs in firestore.

I will attach my screenshots

You gotta define at the url path. Examples:

HTTP request flow function with method set to patch. URL:, in your case, YOURDOCUMENTID is the id for that specific user.

1 Like

That worked, thank you

Hi Thank you,
It is working here this way as well, but in this case do I have to set manually for every single user? Is there a way that we can get the user ID automatically?
In my case even if the access of the whole app would be unique for every user will be grand. It is a equipment register and the do not have access to each other data.
Is there a way that I can do it?

thank you

Hi Maxwell,

About setting the user ids automatically, have you read this part of the post: Best practices for connecting user to their data - #3 by Alan_Alves? Could you get this to work?

As for your second question, yes, you can ensure this on the client-side, by retrieving only the data from that specific user, and modify on the security rules in Firestore, that users can read/write only their related data (that will prevent anyone from messing with with your data). I’ll intend to do a simple post about it later this week.

1 Like


Can you please elaborate it?

When I try the same in my POST call, I get error "“code”: 400,
“message”: “Document parent name “projects/{projectid}/databases/(default)/documents/{collectionID}” lacks “/” at index 69.”

I am using the HTTP request with url as you mentioned “

Hi @DG_L ,

You gotta set the HTTP method to PACTH instead of POST.

Alternatively, to create a document specifying the id, with the POST method, you may use the following:

Note that this last method cannot be used to update documents. In order to update any document use PATCH method.

Post back here if it won’t work.

Thank You @Alan_Alves . The alternative method worked fine. This was useful.

Hi @Alan_Alves,

I’m trying to create a journaling app where each user can see only the journals that they’ve written. I’ve been trying to get this part (users can only see their data) to work for awhile now, but couldn’t find any resources besides this thread on how to do this.

I tried getting ID from the UID using the Get current user (Firebase Auth) function but I got an error saying that the api key was invalid. Our api key is stored as an app variable, so this seems like a weird error to me. Do I need to pass data through this function?

Thank you so much for the help, and if anyone can point me towards more helpful resources for firebase that would be great.

1 Like


It seems you haven’t set the FireBase connector correctly. I suppose you want to you use the FireBase auth API in AppGyver, if that’s the case take a look at the link below. That should solve the API err.


I followed the video and set everything up, but I am still getting the same error.
Right now I have the sign in/ sign up fully functioning, but I am using HTTP requests to do this using I tried using the built in firebase auth functions, but am getting the same API Key error.

Any tips on how to connect user to their data if I am using HTTP requests for the user sign in?

Ok. So you’re saying that you could Auth user using http request, right?

The HTTP request reruns a JSON document. One of then properties of this returned document is the UID. You just need to save it to a variable. I would post an example of this document here if I was typing from a computer.

If you go to you can send an HTTP request with the same settings as you set in your app. It will return the JSON document I’m talking about, so you may see the structure of this doc.

Post back here if get stuck.


I couldn’t get the Postman part as I was getting an “Admin_Only_Operation” error. I tried changing firestore rules but I was still getting this error (maybe because auth is using the Authentication on firebase)

So, I’m not sure the syntax for getting the UID from the HTTP request and setting that to the variable. I attached a screenshot of my logic flow function in case that helps.

1 Like


That’s OK. However, if you’re getting a response to sending an HTTP request through appGyver API, you should as well get the same response from Postman API if you enter the same values. For your convenience take a look at the setting at Postman:

With the correct WEB API KEY, the method set to POST, and body to JSON, and the structure as in the pic above, with an existing email and correct password, you should get a response in the below structure:

  "localId": "ZY1rJK0eYLg...",
  "email": "[]",
  "displayName": "",
  "idToken": "[ID_TOKEN]",
  "registered": true,
  "refreshToken": "[REFRESH_TOKEN]",
  "expiresIn": "3600"

For more info about all the possible responses body, and what any of those keys mean, take a look at this reference doc from FireBase. (If you get errs, you’ll get different responses body depending on the err).

The formula for “Set UID”, should be similar to the pic below:

Hope you’ll be able to set it up now! I reinforce the benefits of testing your HTTP requests on Postman before setting it up on appGyver, as you can see right away the raw response body of your request.

All the best!


@user2, this method will also work for signing up users. The Response Playload is quite similar to the one for signing users in. It has the following structure:

  "idToken": "[ID_TOKEN]",
  "email": "[]",
  "refreshToken": "[REFRESH_TOKEN]",
  "expiresIn": "3600",
  "localId": "tRcfmLH7..."

Therefore, the UID is also on the key localId.

For more info, take a look at this doc.

1 Like


Thank you so much! I was able to get the UID and also create documents where the ID is the UID.

The Data structure I am using is to have each user have a document, and within the document there is a subcollection where all of their journals will be stored (since I am making a journaling app where they can write multiple journals).

I’m a little confused as to how to implement the get/post requests. Before now, I was using data resources and data variables to build the get & post requests by setting the schema, and setting the user input to the data variable. But since the relative path would be different for each user, how would this work?

Also, if two users are using the app at the same time, wouldn’t this interfere with the app variable UID since it will change once a new user logs in? Then it would be difficult to build HTTP requests using the UID for the document ID.

Can you please elaborate this?

I am also facing the same issue… I was able to get the UID from the sign-up request but i coudn’t create record of the same user with document id as UID.

Your support is highly appreciated @user2 @Alan_Alves