# Run a Macro from the Marketplace: Your First Run > Run a macro from the MAS Marketplace: install a bot, add your BlueStacks or cloud device to a device group, set its options, and start a clean first run. Source: https://automationmacro.com/docs/run-macro-from-marketplace (Studio, updated 2026-09-04) This guide shows how to run a macro from the Macro Automation Studio (MAS) Marketplace: install a bot, put a device in a group, and launch a first run you can watch in the logs. It is written for a first-time user with one emulator open. > [!NOTE] > The screenshots below were taken before the sidebar was redesigned. **Marketplace** and **Device Groups** now sit in the left sidebar instead of the top bar, and some buttons have new labels. The steps and their order are the same. ## Before you start - The latest MAS build installed and signed in. See [Install](/docs/install); the app is a free download for the trial from the [download page](/download). - One emulator running with ADB enabled, or a cloud device allocated on **Cloud Devices**. See [Devices](/docs/devices). - An active trial or subscription, so the Marketplace can load. ## Steps ### 1. Open the Marketplace Click **Marketplace** in the sidebar. The listings open sorted by **Most downloads**. Use the search box or the **Category** filter to find the bot you want.
Marketplace page with available macros
The Marketplace, with a card for every published bot.
### 2. Install the bot to run on BlueStacks or a cloud device Click **Download** on the card. MAS adds the bot to **Macros** with a **Market** badge. Nothing is stored on disk: the script is fetched from MAS each time a run starts, and you stay on the version you installed until you click **Update**. [Marketplace](/docs/marketplace) explains installing, updating and removing bots in detail.
Download button for the selected marketplace macro
Download adds the bot to your Macros library.
### 3. Open Device Groups Click **Device Groups** in the sidebar. A group holds the devices you want to manage together, so you can start and stop them as one.
Device Groups page for managing groups of devices
Device Groups lists every group you created.
### 4. Create a group 1. Click **Create Group**. 2. Enter a **Name** of at least 3 characters. 3. Choose the **Type**: **Local** for emulators on this computer, or **Cloud** for cloud devices. 4. Add a **Description** if you like, then click **Create Group**. The type cannot be changed after the group exists, so pick it for the devices you plan to add.
Create Group dialog with name and description fields
The Create Group dialog. The Type select was added after this screenshot.
### 5. Choose a cloud device group, if you have cloud devices If the bot should run on a cloud device, create the group with the type **Cloud**. In a cloud group the header button reads **Add cloud device** instead of **Add Device**. Click it, pick one of the devices you allocated on **Cloud Devices**, and click **Add**. No port is needed, because the device runs on MAS servers. Skip steps 6 and 7 and continue with step 8. See [Cloud devices](/docs/cloud-devices) for allocating one. ### 6. Click Add Device In a local group, click **Add Device** at the top right of the group page.
Add Device button in the group page
Add Device opens the device details form.
### 7. Enter the device details 1. Type a **Device Name**. 2. Pick the emulator's **Port** from the list. Click **Refresh** if you started the emulator after opening the dialog, or choose **Custom Port** and type the number. 3. Under **Startup Macro**, select the bot you downloaded. 4. Click **Add Device**. If the port list is empty, the emulator is not exposing ADB yet. The [BlueStacks guide](/docs/bluestacks-setup-guide) shows where to enable it and how to read the port.
Device details form with name, port and macro selection
Name, port and startup macro for the new device.
### 8. Run the macro from the Marketplace Click **Start** on the device card, then click **Show** to open the logs. The status badge moves from Starting to Running, and the first log lines appear. Watch the whole first run: a bot that reaches its loop and repeats it once is set up correctly. Click **Stop** to end the run.
Device card with the run control and the logs panel
Start the run and follow it in the logs panel.
> [!TIP] > Once the first run is clean, **Start All** runs every device in the group, and the [Scheduler](/docs/scheduler) can start the group daily, weekly or monthly. ### 9. Set the macro's options Some bots have their own settings, such as which tasks to run or how long to wait. Click **Macro settings** under the macro select on the device card. This labeled button replaced the menu icon shown in the screenshot. The form lists every option the publisher exposed. Values are saved for this device, or shared across devices through a [settings profile](/docs/settings-profiles).
Macro settings menu on the device card
The macro's own options. The entry point is now the Macro settings button.
## Common issues ### Macro cannot find buttons The bot takes screenshots and looks for template images, so the screen has to match what the publisher recorded. Set the emulator resolution and DPI named in the listing description, run the game in the language it expects, and keep the emulator window unobstructed. In the logs, repeated image-not-found lines point at the template that fails. ### Run stops early Open the logs with **Show** and read the last lines before the stop. Common causes: no macro selected on the card, a required field in **Macro settings** left empty, or the game showing a popup the bot does not handle. Fix the cause, then click **Start** again. ### Device not found MAS could not reach the port you entered. The emulator was closed, restarted on a different port, or has ADB turned off. Click **Refresh** in the device dialog to rescan, or edit the device and enter the new port. If the emulator is running and still does not appear, follow [ADB troubleshooting](/docs/adb-troubleshooting).