Referral Code System

Project Access Link

https://editor.momen.app/tool/X57jbwZw9e6/WEB?code=UoVFchau6nsgK&ref=0562398 

Introduction

• Goal: Create a personalized invitation system where users generate unique codes and new users are automatically linked to their referrers upon code entry.
• Applicable Scenario: Affiliate marketing, reward programs, community growth tracking, and sales attribution.
• Core Logic: Generate a unique string -> Store with owner ID -> Validate input code -> Update the “Invitee” record.

Steps

Data Storage

First, we need to set up the relational structure to track who owns which code and who invited whom.

• account (system table): Add a one-to-one self-referential relationship.

• activity_invite_code: Create this table to store generated credentials.

Logic & State Configuration

We need two primary Actionflows: one to generate the code and one to verify it.

Generate Referral Code

This flow ensures every user gets a unique code. Since random strings can theoretically collide, we implement a Retry Loop to guarantee uniqueness.

1. ​Variable​: Create an Actionflow variable is_generated (Boolean) to track success status.

2. ​Get ID​: Use the “Get ID” node to fetch the current_account_id.
3. ​Set Variable​: Use a “Set Variable” node to initialize is_generated to false.

4. ​Loop​: Use the SEQUENCE(0, 3, 1) formula as the data source. This generates the array [0, 1, 2], meaning the logic will retry up to 3 times (the formula includes the start value but excludes the end value).

5. ​Condition​: Inside the loop, check if is_generated is false.

   • ​If False​(Not Yet Generated): Proceed to the generation branch.
   • If True (Already Generated)​: Skip the iteration.

6. ​Insert Data​: Add a record to the activity_invite_code table.

   • ​invite_code​: Bind to the RANDOM_STRING formula.
   • ​owner_account_id​: Bind to the current_account_id.
   • ​On Conflict​: Set to ​None​.

7. ​Success Check​: Add a Condition node to check if the ID from the “Insert Data” node ​is not null​.

   • If the ID exists, it means the database successfully saved a unique code. Set is_generated to true.
   • If the ID is null (collision occurred), is_generated stays false, and the loop retries.

8. ​Output​: After the loop ends, query the code for the current user.

Verify Referral Code

This flow validates the user’s input and establishes the permanent attribution link in the database.

1. ​Input​: Receive the code string from the UI.
2. ​Variable​: Define a Text variable status to store feedback messages.

3. ​Identity Fetch​: Use “Get ID” and “Query Record” to retrieve the current user’s profile data.
4. ​Pre-check​: Check if the current user’s referrer_id is ​not null​.
   • ​Not Null​: Already bound to an inviter. Set status to “Already Bound” and exit.

5. ​Query Code​: Search the activity_invite_code table where invite_code equals the input code.

6. ​Validation Branches​:
   • ​Case 1​: If the Query result ID ​is null​, set status to “Invalid Code”.

• ​Case 2​: Compare the code’s owner_account_id with the current_account_id. If they are the same, set status to “Cannot invite yourself”.

• ​Case 3​: If the previous conditions aren’t met, set status to “Verification Successful”.

7. ​Update Attribution​: In the Valid branch, use an Update Data node on the account table.
   • Update the referrer_id field with the code owner’s ID.

8. ​Output​: Return the status variable to the UI.

UI Construction & Interaction

1. Page Variable: Define invite_code (Text) to store the result.
2. Display: Bind a Text component to Page Variable.invite_code.

3. Generate Button:
   • ​Action​: OnClick -> Call Generate Referral Code.
   • ​On Success​: Update invite_code variable and “Show Toast” with the result message.

4. Verify Button:
   • ​Action​: OnClick -> Call Verify Referral Code (passing the Input value).
   • ​On Success​: “Show Toast” with the returned status.

Verification

To confirm the system works as intended, use the Preview mode combined with Momen’s “Login Simulation” feature. This allows you to test the logic from the perspective of multiple different users.

Step 1: Generating the Code (User 1)

1. Open the Preview and use the Login Simulation bar at the bottom to create or log in as ​User 1​.
2. Click the “Generate” button.
3. ​Expected Result​: The retry loop executes, a unique 8-character string (e.g., SKGMlszc) is displayed via the page variable, and a “Generation Successful” toast appears.

Step 2: Testing Anti-Cheating Logic (User 1)

1. While still logged in as ​User 1​, enter your own generated code into the input box.
2. Click the “Verify” button.
3. ​Expected Result​: The system identifies that the owner_account_id matches the current_account_id and triggers the “Self-Referral” branch. A toast should display: “Cannot invite yourself.”

Step 3: Successful Attribution (User 2)

1. Switch the Login Simulation to ​User 2​.
2. Enter the code generated by User 1 (SKGMlszc) and click ​**“Verify”**​.
3. ​Expected Result​: The system validates the code, updates the database, and displays: “Verification Successful.”
4. ​Repeat Check​: Try clicking “Verify” again. The flow should trigger the “Already Bound” condition and display: “Already Bound.”

Step 4: Invalid Input (User 3)

1. Switch to ​User 3​.
2. Enter a non-existent or “fake” code (e.g., ABC12345) and click ​**“Verify”**​.
3. ​Expected Result​: The query returns a null ID, triggering the “Code Not Found” branch. The toast should display: “Invalid Code.”

Step 5: Database Final Inspection

Go to Data Center -> Database to perform the final audit of the records:

• ​**activity_invite_code Table**​: Confirm that the code SKGMlszc exists and its owner_account_id matches the system ID of User 1.
• ​**account Table**​: Locate User 2’s record. The referrer_id field should now contain User 1’s ID, and the referrer relationship field should correctly point to User 1’s account profile.