Feature: I would suggest a new flow/action “Post Delete User”
Description: I would suggest a new flow/action “Post Delete User” similar to the flows “Post User Registration”, “Post Change Password”, … so that you can call some other services.
Use-case: If a user is deleted in Auth0 (manually or by API) then we would like to call some “clean-up” methods in other systems. This could be easily achieved with the new flow “Post Delete User”.
Currently you have to use the extension “Auth0 Management API Webhooks” in order to achieve this which means much more effort and complexity: Is there any hook or call back when a user is deleted from auth0 dashboard? - Auth0 Community
Post actions are usually async, which means that you wouldn’t be able to deny the deletion or guarantee that the deletion would succeed in the remote system.
I would suggest a synchronous Pre Delete User flow instead, which should allow you to do both.
There’s no absolute number. Basically the decision is up to our product team but what they’re taking into consideration is (I’m just gonna mention a few factors):
What type of the customers are the requests coming from? (enterprise, etc.)
How many people / companies are requesting certain features and how it looks like compared to other feature requests
How specific feature request is gonna affect our current stack (how much work / changes it require)
etc.
I’ll reach out to our product team to get their attention for that specific product request. Thank you!
I’m trying to make synchronization to our custom store. When somebody delete user sing Auth0 UI we would like to delete this user internally as well… The Action for this can be helpful so i voted…
When a social (Google, Facebook, Apple, etc.) user is deleted the delete user event is currently not fired on the webhooks. Please make sure the flow/action is also triggered for social users.
Is there any update on the consideration of this feature?
We’ve been migrating responsibilities from our developers handling user ops to having our support team performing that action. We’ve found that they were deleting users and asking them to re-register. This was causing an issue on our application end as the user already existed.
Having a pre-delete user would be exactly what we would need to resolve this.