User ID received
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
Ready-made Workflow
Receive a JSON webhook containing user_id and retrieve that user from your connected Auth0 tenant. Connect a dedicated M2M application authorized for read:users. Send an existing user ID you may access; the example ID is fictional. This template reads a profile and does not create or update users or send messages. Map the returned profile into later steps when needed. No private IDs, credentials or webhook URLs are included. Pause disables the source.
What gets copied
FastHook recreates every Step, route, field mapping, and setting with new IDs in your workspace.
Receive a JSON submission from your existing form backend at this Workflow's private webhook URL.
Retrieve user details. A list of fields to include or exclude may also be specified. For more information, see [Retrieve Users with the Get Users Endpoint](https://auth0.com/docs/manage-users/user-search/retrieve-users-with-get-users-endpoint).
Before activation
Send JSON submissions from your existing backend to the private webhook URL created in your Draft. No Webhook account is needed.
Connect your own Auth0 account and review the provider settings used by this Workflow.
Questions
No. FastHook creates a disconnected Draft. Connect your own Auth0 accounts before activation.
Yes. The copied Workflow is an editable Draft. Review every Step, input, mapping, and route before you activate it.
FastHook recreates the Trigger configuration, Action Steps, routes, and mappings with new IDs. Provider accounts, credentials, and secrets are never copied.
Only after you connect the required accounts, finish the configuration, and explicitly activate the Draft.