# Identify user with email, without using actions

**URL:** <https://community.auth0.com/t/identify-user-with-email-without-using-actions/112595>\
**Category:** Get Help\
**Tags:** users, management-api\
**Created:** [August 1, 2023, 3:04pm UTC](https://community.auth0.com/t/identify-user-with-email-without-using-actions/112595 "2023-08-01T15:04:20Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Jorritboer](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jorritboer/32/49501_2.png) [@Jorritboer](https://community.auth0.com/u/Jorritboer)\
**Post date:** [August 1, 2023, 3:04pm UTC](https://community.auth0.com/t/identify-user-with-email-without-using-actions/112595/1 "2023-08-01T15:04:20Z")

</div>

I have a SPA React app and an expressjs API.

I would like to identify the user accessing the API using their email address. I found out how to do this using actions. However, this is not available in the free version so we would like a different method.

The alternative I found is using passport to keep a session with the user data. But this I don’t understand. Does implementing the authentication like this use a completely different flow than the Authorization Code Flow? As I understand it, this forces all login requests to happen through the API. But I find this to be a bit clunky. And can I still use the Auth0Provider for React if I use this flow?

Concretely: are actions and passport the only way to get email data in the API? And, am I understanding it correctly that I would need to use a completely different flow?

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [August 1, 2023, 4:50pm UTC](https://community.auth0.com/t/identify-user-with-email-without-using-actions/112595/3 "2023-08-01T16:50:10Z")

</div>

Hello @Jorritboer welcome to the community!

> [@Jorritboer](#):
>
> I would like to identify the user accessing the API using their email address. I found out how to do this using actions. However, this is not available in the free version so we would like a different method.

In looking at [pricing](https://auth0.com/pricing), I believe free plans include 3 Actions - How exactly are you using Actions to accomplish your use case?

> [@Jorritboer](#):
>
> Concretely: are actions and passport the only way to get email data in the API? And, am I understanding it correctly that I would need to use a completely different flow?

You could also look in to utilizing the [/userinfo](https://auth0.com/docs/api/authentication#get-user-info) endpoint, but by far the easiest route is to include the email as a claim in token(s).

---

<div class="post-metadata">

**Author:** ![Jorritboer](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/jorritboer/32/49501_2.png) [@Jorritboer](https://community.auth0.com/u/Jorritboer)\
**Post date:** [August 2, 2023, 4:20pm UTC](https://community.auth0.com/t/identify-user-with-email-without-using-actions/112595/4 "2023-08-02T16:20:07Z")

</div>

Thank you, I misunderstood the pricing table in the settings tab. I will just use an action

---

<div class="post-metadata">

**Author:** ![ty.frith](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/ty.frith/32/58484_2.png) [@ty.frith](https://community.auth0.com/u/ty.frith)\
**Post date:** [August 2, 2023, 5:51pm UTC](https://community.auth0.com/t/identify-user-with-email-without-using-actions/112595/5 "2023-08-02T17:51:13Z")

</div>

Awesome! Thanks for the update 🙂

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/auth0/original/3X/b/5/b560f266932fcce5d57f09a6595bd50518cae3f3.jpeg) [@system](https://community.auth0.com/u/system)\
**Post date:** [August 16, 2023, 5:52pm UTC](https://community.auth0.com/t/identify-user-with-email-without-using-actions/112595/6 "2023-08-16T17:52:00Z")

</div>

This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.
