Launch a Multilogin cloud phone from NextBrowser
Connect Multilogin in NextBrowser, choose an Android cloud phone and verify its launch and live view before assigning an app task.
About this reference video
The clip demonstrates a Multilogin cloud phone launch from an agent workspace and the Android home screen. These instructions use the NextBrowser Multilogin connector and cloud-phone selection. Launching a phone does not demonstrate that a subsequent Android app task succeeded.
Go to the NextBrowser workflow ↓Overview
NextBrowser can coordinate a Multilogin Android device as well as browser profiles. The first check is the device connection itself: the correct workspace and phone must be selected, the launch must complete, and the remote view must show the intended device before an agent works inside an app.
What happens in the video
The operator selects a Multilogin cloud phone profile and asks the agent to start it. The workspace reports launch progress, opens a live remote-control view, and shows the Android home screen. The recording verifies device launch and visibility, but does not perform a task inside an Android app.
Before you start
- NextBrowser with an installed and authenticated local agent
- A Multilogin account with access to the intended Android cloud phone
- The correct Multilogin workspace, folder and phone identity
Run this in NextBrowser
Follow these steps in your own NextBrowser workspace. The video summary records the source demonstration; your result needs the checks below.
Connect Multilogin in NextBrowser
Open the Multilogin connector from the NextBrowser sidebar and connect your account using its secure connection flow. Confirm the workspace. Keep account tokens in the connector rather than placing them in Chat or a reusable prompt.
Choose the cloud phone
Open Cloud phones in the connector, select the appropriate folder and device, and set the intended device selection for this workspace. Browser profiles and cloud phones are different resources; check the selected phone name and identifier.
Ask the agent to launch the selected device
Choose your local agent in NextBrowser and send the prompt below. Watch launch status and the remote-control view. If the phone is unavailable, inspect the connection and device state instead of switching silently to another phone.
Verify the Android starting state
Wait for the device view to show the Android home screen or its actual current app. Confirm the selected device and visible state before continuing. Treat an app task as a separate request with its own result check.
Send this prompt in NextBrowser Chat
In NextBrowser, use the connected Multilogin workspace [workspace] and cloud phone [phone name or ID]. Confirm the selected device, start it and open its live view. Report the visible Android state. Do not open apps, post content or change settings during this launch check.
Replace the placeholders, then send this in NextBrowser Chat with the intended profile and agent selected. This is a suggested task, not the recording transcript.
What to verify in your run
- The intended Multilogin cloud phone running and visible from NextBrowser
- A launch report naming the selected device and its actual visible Android state
Questions about this workflow
Is a cloud phone the same as a browser profile?
No. The connector separates Browser profiles and Cloud phones. Select the Android resource for this workflow.
Does the video demonstrate an Android app task?
No. It shows device launch and the Android home screen. App navigation and any result inside an app require a separate check.
Keep exploring
NextBrowser documentation
NextBrowser documentation ↗Product guide: profiles, agents and sessions ↗NextBrowser Multilogin connector ↗From the blog
Explore the foundations of browser automation and structured research.
Related use cases
Web Scraping and Browser Research ↗NextBrowser workflow adapted . Recording reviewed . Video source: published video and description.


