User Actions

User event Actions provide authentication and account management for Web and Native App — registration, login, verification codes, contact binding, and account lifecycle.

User Actions include:

1. Refresh current user data
2. Send verification code
3. Verify verification code
4. Register account
5. User login
6. Bind contact information
7. Unbind contact information
8. Reset password
9. Logout
10. Deregister account

Refresh Current User Data

Purpose

Refresh the in-app current user snapshot after profile, binding, or password changes so UI matches the server without a full reload.

Configuration and Output

Add Refresh current user data on a button, or chain it after bind/unbind, password reset, or profile update Actions.

Send Verification Code

Purpose

One-time codes for sign-in, sign-up, password reset, bind/unbind account, and deregistration.

• Built-in service: Momen built-in email delivery (SMS availability depends on project configuration and region).
• Bring your own channel: Connect third-party SMS, email, or other providers via Actionflow.

How it works:

1. Generation: Running Send verification code creates a 6-digit numeric code and stores recipient, code, and scenario in an internal table.
2. Delivery:
   • System mode: Sent through the built-in channel.
   • Custom mode: Passes send to, verification code, and scenario into a designated Actionflow that performs delivery.
3. Verification: On login, register, or other final Actions, inputs are compared to the stored record; a match succeeds.

Configuration

Action settings

Custom delivery setup

Step 1: Create a send Actionflow

1. Create an Actionflow with inputs: send to, verification code, scenario.
2. Add send nodes (e.g., built-in Twilio SMS, email nodes) or call external APIs.
3. Bind Actionflow inputs to send node parameters.

Step 2: Add custom configuration

1. Go to Settings → Verification code and add a custom configuration.
2. Set:
   • Name: Label (e.g., Twilio SMS).
   • Actionflow for sending verification code: Actionflow from Step 1.
   • Actionflow inputs: Under Constant in data binding, map Send to, Verification code, and Scenario to Actionflow inputs.

Step 3: Use the configuration

In Send verification code, select the custom config under Custom config.

Verify Verification Code

Purpose

Validate the code the user entered before running sensitive follow-up Actions.

Configuration and Output

1. Add Verify verification code; choose delivery method; bind phone/email and code inputs.
2. Configure On success / On failure (e.g., Show Toast, proceed to login).

Select Action	Delivery method

Register Account

Purpose

Create a new account with username, email, phone, and password. Supports username, phone, and email registration paths; email/phone verification optional per project settings.

Configuration and Output

Add inputs and a button; configure Register account; bind username, phone, email, verification code, and password fields.

Username	Phone	Email

Notes

1. On success, Momen creates account data and links the account table record.
2. Configure Show Toast on success and failure.

User Login

Purpose

Sign in with username/password, phone (code or password), or email. SSO may be available when configured — see SSO configuration.

Configuration and Output

Add inputs and a button; configure User login; bind credentials and verification fields.

Username	Phone + code	Phone + password	Email

Notes

Configure Show Toast or navigation Actions on success and failure.

Bind Contact Information

Purpose

Add and verify a phone number or email on the account for recovery and notifications. Updates the account record on success.

Configuration and Output

1. Add Bind contact information on a button; bind phone/email input.
2. On the send-code button, set scenario to Bind account.

Bind phone	Bind email

Unbind Contact Information

Purpose

Remove a bound phone number or email. Clears the field on the account record.

Configuration and Output

Add Unbind contact information; bind verification code input.

• Set send-code scenario to Unbind account.

Unbind phone	Unbind email

Reset Password

Purpose

Reset a forgotten password via verified phone or email.

Configuration and Output

Bind phone/email, new password, and verification code; configure Reset password on a button.

Phone reset	Email reset

Logout

Purpose

End the current session. Closing the browser or app does not always clear server session — use Logout for explicit sign-out.

Configuration and Output

Add Logout to a button. Optionally chain refresh or UI update Actions. Logout does not delete database records.

Select Action	Result

Deregister Account

Purpose

Permanently delete the account and associated data. Irreversible; requires verification code or password confirmation.

• Set send-code scenario to Deregistration when using code-based deletion.

Code deregistration	Password deregistration

Configuration and Output

Add inputs (verification code or password) and Deregister account on a button; bind fields.