Phone Flows

Build automations with blocks and run them on your Android phone, even in the background.

📱 You need the EverythingYouNeed Android app to run flows on your phone. You can build and test without it, right here in your browser.

Flow editor

No phone connected

Drag blocks from the categories on the left and snap them together. Every flow starts with a block from "Triggers". Create a page with "Page" and show it with a notification or with "Show page".

No output yet. Press "Test" to try your flow.

Connect your phone

Open the EverythingYouNeed app on your Android phone, choose "Connect" and scan this QR code or enter the code.

···· ····

Requesting a code…

The code goes through our connection service at Cloudflare. After that, everything travels directly and encrypted between your browser and your phone. On some school or company networks a direct connection does not work.

Edit text

Choose an app

Connect your phone to see the list of your apps, or type the package name (such as com.spotify.music).

Example flows

Pick an example. It is added to your list as a new flow, so you can change it.

More information & frequently asked questions

How does Phone Flows work?

  1. 1
    Build your flow

    Snap blocks together like puzzle pieces. Every flow starts with a trigger, such as a set time, charging, a notification from another app or arriving at a place.

  2. 2
    Test in your browser

    Press "Test". Blocks such as HTTP, JavaScript, if/else and loops really run, phone blocks are simulated, and you see notifications and pages right in your browser.

  3. 3
    Send it to your phone

    Connect to the app with the code or QR code and send your flow. Turn it on, and the phone runs it, even when the app is closed.

Why Phone Flows?

  • ✅ No account and no cloud: your flows go directly from your browser to your phone
  • ✅ Phone blocks and logic in one flow: from notifications with buttons, your own pages and opening apps to HTTP requests, lists and JavaScript
  • ✅ Passwords and API keys stay on your phone only
  • ✅ Live logs from your phone in your browser while you are connected

Data, variables and pages

Values are round blocks you snap into a slot. An HTTP request returns a response, and with field body.temp of ... you take out a part of it. Store it in a variable, and with remember it is still there next time. With secret apiKey you use a key that is only on your phone.

You build a page from titles, text, images, input fields, switches and buttons, or with your own HTML. A tap on a notification or the "Show page" block opens it on your phone, and every button runs its own blocks. For anything more complex, use the JavaScript block, which runs sandboxed without network access.

Frequently asked questions about Phone Flows

Do my flows go through a server?

No. Only the 8-digit code and the connection details go through our connection service. Your flows and logs travel directly and encrypted between your browser and your phone. In your browser they are kept in local storage.

Does it work when the app is closed?

Yes. If you turn on the background service in the app, a permanent notification stays visible and schedules and triggers keep running when the app is closed. Android can delay such a service under strict battery saving, so turn off battery optimization for the app if your flows need to run on the minute.

Where are my passwords and API keys stored?

Only on your phone, encrypted in Android's secure storage. In the editor you refer to them by name, such as {{ $secrets.weatherKey }}. So they never end up in your browser or in an export. Only connect to your own browser: a flow you receive can use your secrets.

Why is the app not on Google Play?

An automation app needs permissions that Google Play strongly restricts. That is why the app is available as an APK on GitHub, together with its source code. When installing, you have to allow Android once to install apps from that source.

Can I save or share my flows?

Yes. Export downloads a flow as a JSON file that you can keep or pass on. Import opens such a file again. An exported flow never contains your secrets, only their names.

You might also need