Skip to main content

Android Automation

Both connection methods require the OpenCompany Android companion app on your device, which is not yet publicly available — and the Remote Relay path additionally needs a relay server URL. Until the app ships publicly, this tutorial is only usable if you already have access to it. For an automation you can run today, try the Telegram bot tutorial.
OpenCompany can control Android devices for automation tasks like launching apps, monitoring battery, controlling WiFi, and more.

Connection Methods

Set Up Connection

Android device connection is configured in the Credentials Modal (Android panel), not via a workflow node. Open Credentials and pick one of the two methods below.

Option A: Local ADB

  1. Enable Developer Options on your Android device
  2. Enable USB Debugging
  3. Connect device via USB
  4. Run adb devices to verify connection
  5. In the Credentials Modal, open the Android panel and choose Local ADB (ADB port forwarding is set up for you)

Option B: Remote Relay

  1. Open the Credentials Modal and select the Android panel
  2. Click Connect to start the relay connection
  3. Scan the QR code with the companion Android app to pair your device
Remote relay allows controlling devices anywhere with internet access. The relay uses a two-state model: connected (relay WebSocket is up) versus paired (a device has scanned the QR and is ready to run actions). Android nodes require a paired device to execute.

Available Android Nodes

OpenCompany ships 16 Android service nodes across monitoring, apps, automation, sensors, and media. Each one can run as a standalone workflow node or be connected to an AI agent’s tools handle.

System Monitoring

App Management

Automation

Sensors

Media

Example: Battery Alert Workflow

Create a workflow that sends an alert when battery is low.

Workflow Design

Step 1: Add Cron Trigger

Step 2: Add Battery Monitor

Step 3: Add Python Executor

Step 4: Add WhatsApp Send (conditional)

Example: App Launcher Workflow

Launch an app when receiving a webhook.
App Launcher Config:
Test:

Example: WiFi Toggle

WiFi Automation Config:
Test:

Battery Monitor Output

Network Monitor Output

Troubleshooting

  • Run adb devices to check connection
  • Ensure USB debugging is enabled
  • Try different USB cable/port
  • Restart ADB: adb kill-server && adb start-server
  • Verify relay URL is correct
  • Check API key is valid
  • Ensure companion app is installed on device
  • Check firewall settings
  • Some actions require root access
  • Use device automation apps for restricted features
  • Check Android version compatibility

Tips

Start with Battery Monitor and System Info to verify your connection works before building complex workflows.
Use meaningful node names (F2 to rename) when building workflows with multiple Android nodes.

Next Steps

Android Node Reference

Full documentation for all 16 Android nodes

Webhooks

Trigger Android actions via HTTP