User created
Receive Auth0 user.created events through a native Event Stream managed by FastHook. The tenant must have Event Streams access and the required permissions.
Workflow template
Notify a Slack channel when Auth0 reports a new user. The message contains the user ID, event ID and event time, without copying email addresses or other profile fields.
How it works
Receive Auth0 user.created events through a native Event Stream managed by FastHook. The tenant must have Event Streams access and the required permissions.
Post the new user’s ID, provider event ID and event time to your selected Slack channel as plain text.
The result
The prepared message shares identifiers and timing rather than a user profile. Choose a channel whose members should see these identity references.
Auth0 user created User ID: auth0|FICTIONAL_USER Event ID: evt_0000000000000000000000 Event time: 2026-11-02T00:00:00.000Z
Fictional event data. Email addresses, names and other profile values are not mapped into the notification.
Before activation
Create a Machine-to-Machine application for the Management API. Confirm Event Streams entitlement and authorize read:event_streams, create:event_streams and delete:event_streams permissions.
Enter the original HTTPS Auth0 tenant URL, M2M Client ID and Client Secret in the connection. Connect Slack and select the channel for user-created alerts.
Allow FastHook to provision its Event Stream, then create a fictional user in the connected tenant. Check the workflow run and the resulting Slack message.
Native Event Streams are required. A working M2M connection alone is not enough: the tenant needs Event Streams access and the stream-management permissions. This template uses user.created, not an Auth0 log-stream source or an interactive login flow.
Only FastHook-owned subscriptions are managed. Pausing stops this consumer. FastHook removes the stream it owns when no other active workflow needs it; unrelated streams are not removed.
Event deduplication is not an exactly-once message guarantee. Provider event IDs suppress repeated processing. Manual reruns can repeat the Slack effect, and an uncertain external write can still produce a duplicate. Markdown and link/media previews are disabled in the prepared message.
The tenant must also have Event Streams entitlement. The M2M application needs read:event_streams, create:event_streams and delete:event_streams so FastHook can manage its dedicated stream.
No. The prepared mapping includes only User ID, Event ID and Event time. Other fields present in the Auth0 event are not copied into Slack.
The consumer stops. FastHook removes its owned stream when no other active workflow still needs it, while preserving streams it does not own.
No. Provider event IDs suppress repeat processing, but manual reruns and uncertain destination writes can still repeat effects. The template does not promise exactly-once Slack delivery.