App Logo
luma.com

Luma whoami (signed-in account)

Report which Luma account this browser is signed in as: the account email, the Luma user id, the username and the display name. Being signed out is a normal answer (connected false), not an error, so it can check a session before other Luma scripts run, or be passed as a run's login probe.

Input

None

Output

name required

The account's display name. Null when signed out.

userId required

Luma user id, e.g. usr-XXXXXXXXXXXXXXX. It stays the same if the account's email changes. Null when signed out.

account required

The signed-in account's email, which a login probe records on the connector it checked. Null when signed out, or when Luma shows no email.

username required

Luma username (luma.com/user/<username>). Null when signed out, or when the account never picked one.

connected required

Whether this browser is signed in to Luma. Signed out is false, not an error, so the script can be passed as a run's `login.probe`.

FAQ

Report which Luma account this browser is signed in as: the account email, the Luma user id, the username and the display name. Being signed out is a normal answer (connected false), not an error, so it can check a session before other Luma scripts run, or be passed as a run's login probe.
Nothing. It takes no input.
It returns name, userId, account, username, connected.
Yes. It acts as you on luma.com: on your own Chrome it reuses your session, and on a Reduck-hosted browser it loads the luma.com cookies saved by the Reduck extension.
It only reads. It looks things up on luma.com and changes nothing there.
Ask an AI agent connected to Reduck to run reduck/luma.com/whoami, or run it from a terminal with the Reduck CLI: npx @reduck-ai/cli@latest run --script reduck/luma.com/whoami
It is part of Reduck's official curated catalogue.

Start building not clicking