Overview

What is MoreLogin Automation?

MoreLogin Automation is a workflow that connects your apps to automate repetitive tasks. Instead of hiring a person to manually click Like on 100 different phones or uploading the same video to 50 accounts one by one, you build a Template (a set of instructions), and the MoreLogin automation executes it across all your cloud devices simultaneously.

No Code Required: Drag and drop blocks like Click, Swipe, and Type.

Cloud-Based: It runs on virtual Android devices in the cloud, not on your local computer.

How Can It Help You?

It transforms manual labor into automated workflows.

Scale Your Business: Manage 100 TikTok accounts as easily as managing one. Run the same Warm-up task on all 100 phones at once
Save Time: Automate repetitive actions like watching videos, liking, following, or posting content.
Precision & Safety: The robots follow exact rules. You can add Random Delays and Coordinate Offsets to make the bot look like a real human finger, reducing the risk of bans
Dynamic Work: Using Initialize Session, one robot can handle different videos and captions for every run, so you don't need to edit the code daily.

Action Nodes

1. Initialization

Definition: The mandatory starting point of every flow. It establishes the connection to the Cloud Phone and defines what data the user needs to provide before running the task. After completing the workflow design, you can execute the workflow by adjusting the initialization parameters.

Allocation:

Create Initialization Form: Click this button to define input variables.

Add Field: Adds a new variable that the user must fill in when creating a Schedule.

Type: Defines the data format:

String: Text (e.g., Captions, Usernames).
Number / Integer: Numerical values (e.g., Scroll counts).
Image / Video: Media files to be uploaded.
Boolean: True/False switches.

Scenario: You want to create a single TikTok Upload template but use it to post different videos on different days. You would create a Video input field here so you can upload the specific file later without editing the code.

View Your Cloud Phone

While designing your workflow, it is necessary to have the cloud phone open for reference and real-time interaction. Click this button/icon to launch your cloud phone (emulated Android device), and once it is open, you can proceed to design and build your workflow.

Download APP

Morelogin allows you to quickly download popular apps without needing to log in to a Google account. Simply click the app icon located in the lower right corner of the emulated mobile interface to open the list of commonly used apps, and then select the one you want to download and install.

If the downloaded app does not appear on the main mobile page/screen, you can try swiping upward on the emulated phone interface to open the app drawer (the full list of installed apps), where you should be able to find it.

2. Launch App

Opens a specific app on the Cloud Phone.

Allocation:

*Package Name (Required): The unique ID of the app **How to find the unique ID of the app?

Click the "Snapshot" icon in the lower right corner of the mobile interface, then create a snapshot. (This step is essential as it forms the foundation for capturing any elements in the cloud phone.)

Once the snapshot is created, find and click the desired element you want to open or interact with (e.g., an app icon). The snapshot system will automatically detect and track the element details of the corresponding app. You can then view the captured element information, including the package name, in the sidebar on the right.

**URI Address: (Optional) A specific deep link to open a specific page inside the app immediately.

3. Tap Element

Definition: Finds a UI element (button, icon) and clicks it.

Allocation:

Selector Type: tells the robot how to locate the target item on the screen.

By Find Element: Once you have selected this option/step, navigate to the desired button in the cloud phone (emulated Android screen). Then, use the snapshot tool to capture it—this will automatically detect and generate the corresponding element selector for the button.

When Condition is Met:

There are several ways to locate elements:

Text

For example, after opening the TikTok app, if you want to click the Profile or Inbox button and the button text (such as "Profile" or "Inbox") is clearly visible on the cloud phone screen, you can select the Text option. Then, choose the matching method Equals and enter "profile" or "inbox" (make sure the capitalization matches the actual displayed text). This will enable the automation to click the corresponding Profile or Inbox button automatically.

Fulid

If the button you want to click is an icon, graphic, or emoji (without any visible text), you can use the fulid to locate the element reliably.

Here’s how to do it:

Create a snapshot (as described earlier).
In the cloud phone interface, find and tap/click the target element or button you want to automate.
In the right sidebar of the snapshot panel, locate the full property for the captured element and copy its value.

Back in your workflow step, select fulid as the locator type, choose the matching method Equals, and paste the copied fulid value. This allows the RPA to automatically and accurately click that graphic element every time.

Use Previous Element: Use the item found in a previous step, which interacts with an element it already identified in an earlier "Find Element" node. **Maximum Wait Time for Element to Appear: How long to wait for the button (Default 3000ms). Increase this for slow pages. **Tap Type:

Single Tap: Standard click.

Double Tap: Used for Like actions.

Long Press: Used to open context menus. **Delay After Tap: Time to pause after clicking (Default 0ms).

4. Tap(x, y)

Definition: Taps a specific pixel location on the screen.

Allocation:

X / Y: The horizontal and vertical pixel coordinates. **Coordinate Random Offset: Adds a random deviation (e.g., 5px) to mimic human inaccuracy and avoid detection. **Tap Type: Single/Double/Long Press. **Delay After Tap: Time to pause after clicking.

Scenario: Clicking Close Ad buttons that don't have text/ID, or playing games.

How to locate your XY element coordinates

To capture an element using XY coordinates, follow these steps:

While viewing the cloud phone (emulated Android screen), click the Snapshot button to create a new snapshot.
Navigate to and tap the target element (e.g., button, icon, or any clickable area) you want to automate within the cloud phone interface.
Once captured, check the right sidebar of the snapshot panel—you will see the exact XY coordinates of the selected element.

5. Swipe Page

Definition: Simulates a finger dragging across the screen.

Allocation:

Swipe Start Coordinates (X, Y): Where the finger touches down. **Swipe End Coordinates (X, Y): Where the finger lifts off. **Coordinate Random Offset: Randomizes the path slightly for safety. **Swipe Duration: Speed of the swipe (ms).

*> 300ms: Fast flick (TikTok scroll).

*> 2000ms: Slow drag.

**Delay After Swipe: Time to wait after the movement finishes.

Scenario: Scrolling feeds, viewing image carousels.

6. Wait

Definition: Pauses execution for stability.

Allocation:

Wait Method:

Fixed value: Wait exactly X ms.

Random Time: Wait between X and Y ms (Best for anti-detection). **Wait Time: Duration in milliseconds (1000ms = 1s).

7. Find Element

Definition: Checks if an element exists without interacting with it.

Allocation:

When Condition is Met: Define what to look for.

There are several ways to locate elements:

Text

Fulid

If the button you want to click is an icon, graphic, or emoji (without any visible text), you can use the fulid to locate the element reliably.

Here’s how to do it:

Create a snapshot (as described earlier).
In the cloud phone interface, find and tap/click the target element or button you want to automate.
In the right sidebar of the snapshot panel, locate the full property for the captured element and copy its value.

Maximum Wait Time for Element to Appear: How long to check before deciding it's missing. **Delay After Finding Element: Buffer time after the check.

Scenario: Check if an Ad Popup exists.

8. Get Element Text

Definition: Reads text from the screen and saves it as a variable.

Allocation:

Selector Type: Identify the text area. **When Condition is Met: Define the target element. **Maximum Wait Time for Element to Appear: Time to wait for the text to load.

Scenario: Scraping a verification code (OTP) or an account username.

9. Text

Definition: Types text into a targeted input field.

Allocation:

Input Selector Type: Use By Find Element to locate the text box. **When Condition is Met: Rules to identify the box (e.g., text Equals Username). **Input Field Timeout: Max time to wait for the field to be ready (Default 3000ms). **Input Text: The content to type. **Clear field before typing: (Toggle) Deletes existing text before typing. **Press Enter after input: (Toggle) Simulates hitting Enter on the keyboard after typing.

Scenario: Logging in, searching, commenting.