Tasker for Android — 2026 Power-User Guide

Tasker has been the Swiss-army knife of Android automation since 2010, and in 2026 it is still the most capable workflow engine on the platform — by a wide margin. Modern competitors (MacroDroid, Automate, Bixby Routines, Google Routines) are easier on the eyes, but every serious automation request we get at the workshop ends up in Tasker because it is the only tool that can do all of: location, sensors, notifications, networking, accessibility, scripting, plugins, intents, and shell commands in a single profile.

This guide is the working version of what we hand to clients after a setup job. It is not a beginner click-through tutorial — there are 50 of those on YouTube. It is the patterns and gotchas that actually matter once you start building.

What Tasker Is, in One Paragraph

Tasker is an Android app that runs profiles — each profile is one or more contexts (triggers: time, location, app launched, NFC tag, Bluetooth connect, notification posted, etc.) that, when all true, fire a task (a list of actions: change a setting, run a script, send an HTTP request, show a notification, launch an app, control media, etc.). Profiles run continuously in the background. The whole engine costs about 30 MB of RAM and a few percent of battery per day if built sensibly.

That is the entire model. Everything else is detail.

The Seven Profile Patterns That Cover 90% of Real Requests

After three years and hundreds of automation jobs, almost every client request collapses into one of these seven shapes:

1. Context-Aware Profile (Wi-Fi, Bluetooth, Location)

The classic. Office Wi-Fi connects → silent mode + work email enabled. Car Bluetooth connects → DND + Maps + Spotify. Home Wi-Fi connects → restore personal profile. Use the State context (Wi-Fi Connected, BT Connected) instead of polling location — it is event-based and free.

2. Time / Calendar-Driven Profile

Daily 09:00 → run morning script. Calendar event with title containing “Meeting” starts → DND on, mute mic, dim screen. Use Time context for fixed schedules and Event → Calendar Begins for calendar awareness. Avoid 1-minute time loops; they are the #1 cause of unexplained battery drain.

3. NFC-Triggered Workflow

Tap tag → fire one task. The trigger lives outside Tasker (NFC Tools writes the tag to launch a Tasker task by ID via intent), but the task itself is just a normal Tasker task. Toggle pattern: store a global variable, flip it on each tap, branch the task on the value.

4. Notification Listener / Parser

Specific notification arrives → extract data and act. AutoNotification plugin parses fields cleanly; Tasker’s built-in Notification event works for simple cases. Common uses: WhatsApp from a specific contact → read aloud through TTS; banking app pushes balance update → log to a CSV; Uber driver assigned → flash the home lights via Home Assistant.

5. Sensor / Health Reactor

Step out of bed (accelerometer + screen on after wake-up time) → bedroom lights warm. Phone tilted face-down on desk → DND on. Long fingerprint hold → panic-button scene. Use the Sensors category sparingly — most sensors require continuous polling and cost battery if left enabled.

6. HTTP / Webhook Bridge

This is the one that turns a phone into an automation hub. Tasker can fire HTTP requests to anything — your Home Assistant, a Telegram bot, an n8n webhook, your own Cloudflare Worker. Receive incoming webhooks via the HTTP Server action (paid extra) or via Pushbullet / a small AutoRemote setup. We use this in roughly half of all automation jobs we ship.

7. Termux + Tasker Scripted Schedule

When you need real shell scripting on a schedule, Termux is the back-end. The Termux:Tasker plugin lets a Tasker action invoke any script in ~/.termux/tasker/, with arguments and stdout return. Daily backups, scraped reports, scheduled signal-cli messages, podcast downloads — all live in Termux, all triggered by Tasker.

Battery Discipline

The single biggest mistake new Tasker users make is using time-based triggers when an event-based one is available. Polling every minute is roughly 100× more expensive than waiting for a BroadcastReceiver. Rules of thumb:

• Wi-Fi state change: use Wifi Connected State, not Time + If
• Location: use Location Mode State + Cell Near, not GPS polling
• Battery: use Battery Level State, not Time loops checking %BATT
• Notifications: use Event → Notification, not polling status bar

After every build we run BetterBatteryStats for 24 hours and prune anything Tasker is doing more than 60 times per day unless it has to.

Tasker Permissions Worth Knowing

Tasker can do far more if you grant it the right permissions, most of which are one-time:

• Accessibility Service — required for app-launch triggers and AutoInput
• Notification Listener — required to read notification content
• Usage Stats — required for time-in-app conditions
• Display Over Other Apps — required for scenes (custom UI overlays)
• Battery Optimisation Exempt — required if you want profiles to keep firing reliably on most OEM Android skins (especially Xiaomi, OPPO, Vivo)
• Secure Settings via ADB (one-time pm grant net.dinglisch.android.taskerm android.permission.WRITE_SECURE_SETTINGS) — unlocks dozens of system settings without root

The ADB grant is the quiet superpower. With it, Tasker can change accessibility services, default keyboard, immersive mode and many secure settings that normally need root — no Magisk required.

Sharing and Backing Up Profiles

Long-press any profile → Export → Description as XML. You get a .prj.xml (project) or .tsk.xml (single task) that anyone can import via Data → User Import. Always sanitise before sharing publicly — search for hard-coded MAC addresses, IP addresses, account names, and webhook URLs.

Full backup: Data → Data Backup writes a Tasker.prj.xml to internal storage. Restore on a new phone is Data → Data Restore. Migrating to a new device is one of our most common automation jobs because in addition to restoring, we re-test every profile on the new OEM and patch level.

Where Tasker Hits Its Limits

Three places, honestly:

1. App-internal automation that requires UI taps. Tasker can do it via AutoInput, but UI automation is fragile — every app update can break selectors. For repetitive in-app tasks consider whether the app has an API instead.
2. Anything that requires pretending to be a different user. Spam, fake-engagement bots, account farming. We will not build it and Tasker is the wrong tool anyway.
3. High-frequency, low-latency control loops. Anything sub-second polling. Tasker is not a real-time system; build it as a Termux foreground script or move it to a Raspberry Pi.

Worth Buying?

Tasker is $3.49 one-time on the Play Store. There is a 7-day free trial direct from the developer’s site. AutoApps add-ons run $1–$3 each or roughly $7/year for the bundle. For the amount of behaviour you can change with one weekend of building, it is the best ten dollars in the Android ecosystem — if you have the patience for the UI.

If you do not, we build the workflows for you and hand off a ready-to-go phone with a written quick-reference card. Most builds are 60–180 minutes of work and outlive multiple OS upgrades.