Request Magic Link

Asks the backend to email a one-click sign-in link. Succeeds identically whether or not the address has an account.

Request Magic Link posts email (string value) to the backend's /auth/magic-link when send (Do, signal) is triggered. The backend mails a single-use, short-lived link; clicking it signs the user in on the page named by redirect (defaulting to the page the request was made from), where the runtime picks up the one-time code and establishes an ordinary session. done (signal) means THE REQUEST WAS ACCEPTED — never that an account exists. The endpoint answers identically for known and unknown addresses on purpose, because a public endpoint that answers differently is an account-existence oracle. failure (signal) with error (string value) means the request itself failed: no backend configured, a network error, or the rate limit.

When to use it

For passwordless sign-in, and as a password-free recovery path on backends that use provider sign-in. Requires the backend to have SMTP configured (BAK-002) and magic links enabled in the Auth section — with either missing, the request is still accepted and no mail is sent, which is deliberate anti-enumeration and shows up in the backend's log rather than in the app.

At a glance

Category	Cloud Services
Type name	net.noodl.user.RequestMagicLink
Available in	browser
SSR compatibility	partial — Sends a request from the browser; a server render never triggers it.
Provided by	noodl-viewer-react

Inputs

Values

Name	Type	Default	Description
email	String	—	Address to send the sign-in link to
redirect	String	—	Page the link should return to; leave blank to come back to the page the request was made from

Signals

Name	Type	Default	Description
send	Signal	—	Asks the backend to email a one-click sign-in link to Email

Outputs

Signals

Name	Type	Default	Description
completed	Signal	—	Fires after every invocation, whatever the outcome — wire this to carry on regardless. Failure still fires and still carries its reason, so this cannot hide an error
done	Signal	—	Fires once the request has been accepted, which never means an account exists for that address

Failure outputs

Name	Type	Default	Description
error	String	—	Why the last request failed; empty until one does
failure	Signal	—	Fires when the request itself failed — no backend, no network, or rate limited — never because the address is unknown

Patterns

• Text Input text → email, Button onClick → send, done → a neutral confirmation message.
• Put a Sign In With node on the landing page named by redirect so the app can react to the click's outcome.

Watch out for

• Showing 'check your inbox' only when the account exists — this node cannot tell you that, and a UI that appears to know re-creates the oracle the backend removed.
• Treating done as 'signed in'. The sign-in happens when the user clicks the link, on a later page load.

Related nodes

Sign In With, User, Log In, Request Password Reset

Generated

This page is generated from node-catalog-enriched.json. Do not edit it by hand — run npm run docs:nodes to regenerate, and fix the source enrichment instead.