Android Automation

Automate your Android.

On your device, on your terms.

Flowroid builds automation flows from device triggers and actions. They run on your phone, with no account and no cloud relay — and an optional assistant that builds them for you when describing it is faster than wiring it.

No account. Your automations stay on your phone. 14 days free, then $4.99 / month or $39.99 / year.


What Flowroid does

  • Automation stays on-device

    Flows, variables and logs live on your phone and run with no connection at all. No analytics track them, and we have no way to read them.

  • 32 triggers, 45 actions

    Wire any device event to any device action: geofence arrivals, battery levels, notifications, schedules, and more.

  • Or just ask for it

    Describe what you want and the assistant drafts the flow, or runs one on the spot. It asks before it changes anything — and it is the one part that uses a server.

  • Your phone as a server

    Enable the built-in HTTP API and let other systems trigger flows on your device over your local network.


How a flow works

Every flow is the same three parts, whichever way you build it.

  1. Trigger

    A device event starts the flow. Incoming call, geofence entry, schedule, battery level, notification — your choice.

  2. Conditions

    Optional guards. Run only if the time is right, a variable matches, or the device state passes your check.

  3. Actions

    What happens next. Send an HTTP request, change a setting, play a sound, run another flow, write a file — 45 options.


Two ways to build one

Draw it on a canvas, or describe it and read back what the assistant drafted. Below is the same flow, arriving through both doors.

Visual builder

Flows → + → Blank canvas

Calendar EventWork calendarRinger Mode

Drop a trigger, drop what should follow it, and wire them in the order they run. Branches, loops and sub-flows are nodes too, and every trigger and action on the device is in the palette.

Build with AI

Flows → + → Create with AI

You typed

Silence my phone during calendar events, and put it back after.

It drafted

  1. Starts on Calendar Event
  2. only if Work calendar
  3. then Ringer Mode

One sentence, and it drafts the flow — then shows you what it means to build before anything is saved. Refine it in words, or open it on the canvas and finish it by hand.

Same flow either way: the same nodes, the same on-device engine, the same place in your list. A flow you asked for opens on the canvas; a flow you drew can be revised by asking. Yours is live the moment you save it — the assistant's is saved switched off until you turn it on.


What people build with it

Each of these is one trigger and the actions it runs. Nothing here needs root, a PC, or an account.

See all 26 automation ideas