n8n Workflow: Run Mobile QA on Android via MobileRun

Run Mobile QA on your Android device from n8n—automatically, with results back in the form

This n8n workflow lets you submit a QA test instruction to a specific Android device in MobileRun and then waits for completion—returning the final task status and result as the form response.

What this workflow does

• Receives an authenticated form submission containing a MobileRun device ID and a QA test instruction.
• Sends the instruction to the specified Android device using the MobileRun (DroidRun) node.
• Runs the task with vision and accessibility enabled (as configured by the workflow) so the QA instruction can be executed on the device.
• Waits up to 300 seconds for the Android task to finish.
• Returns the final task status and result to the requester as the form response.

Use cases

• QA instruction intake: collect test requirements from internal teams via an n8n form, then execute on a real Android device.
• Device-specific testing: target a known device by MobileRun device ID for consistent reproduction of issues.
• Automation for SaaS operators: trigger MobileRun QA tasks on demand and capture outcome data without manual device handling.
• Engineering triage: run the same QA instruction across a device set and compare returned results.

Technical details

• Self-hosted n8n required
• Install community node package: @droidrun/n8n-nodes-droidrun
• Create a MobileRun API credential in n8n and select it in the MobileRun node
• Use MobileRun device management to start/connect an Android device, then copy its device ID
• Workflow nodes include: sticky note, form trigger, and droidrunn8n-nodes-droidrunmobilerun (MobileRun/DroidRun integration)