I think you will still have a problem though.
“Data” in the field is indeed unique, but is liable to change. So if the user has another workspace (and thus a second gid/id) added then my worry would be that Bubble would see them as another user.
So I think what is happening is that having got the token, Bubble does a call to your “User Profile Endpoint” to find both an “Id” and “Email”. It does these by trying to read the names from the two fields you have entered out of the response to the user endpoint.
If they don’t exist, then it throws that error. Since gid and id do exist, it must be that it doesn’t like them being in an array.
May be worth asking Asana if there is another endpoint that will give you a consistent id that isn’t in an array ?
Alternatively maybe @emmanuel can advise if there is any way to navigate the JSON response, or does it only look for the key value ?