Four iPhone Shortcuts Worth Building Today

Published August 18, 2026 · Last reviewed September 2, 2026

Automation versus shortcut

A shortcut runs when you tap it — from the home screen, from Control Center, from the Action button, or by asking Siri. An automation runs when something happens: a time, a location, a battery level, an alarm, connecting to CarPlay. Both live in the Shortcuts app; automations are under the Automation tab. Choose Run Immediately when creating one, or iOS will ask permission each time and the automation stops feeling automatic.

1. Arriving home

Trigger: Arrive → Home. Actions: turn off Work Focus, connect to home Wi-Fi if needed, set volume to a chosen level, and optionally start a playlist or turn on lights.

Why it earns its place: the transition from outside to inside is the moment people most reliably forget to change their phone's state, then get a work notification at 19:00 because Work Focus never turned off.

2. Starting the working day

Trigger: Time of Day → 09:00 on weekdays (or Arrive → office). Actions: turn on Work Focus, open your calendar, and optionally set a timer for a first block of work.

This is the single automation that makes Focus modes stick, because it removes the one manual step the whole system depends on.

3. The low-battery routine

Trigger: Battery Level → falls below 30%. Actions: turn on Low Power Mode, reduce screen brightness, and turn off Wi-Fi if you are out.

iOS already offers Low Power Mode at 20%, but 20% on a busy afternoon is too late. Acting at 30% is the difference between arriving home with 8% and arriving home flat.

4. Send my location

Type: a shortcut, not an automation. Actions: Get Current Location → Send Message to a chosen contact. Add it to the home screen, to Control Center, or map it to the Action button on models that have one.

Genuinely useful for a walk home at night, a broken-down car, or telling someone which entrance you are at. It replaces roughly eight taps with one.

Getting each one right

Action

Choose Run Immediately for every automation, and turn off Notify When Run once you trust it.

Why it helps

An automation that asks permission is just a notification with extra steps, and the notification defeats the purpose.

Verification

The automation fires without any prompt appearing.

Action

Test the trigger in real life once, rather than using the Run button in the app.

Why it helps

The Run button proves the actions work; it does not prove the trigger fires. Location triggers in particular need a real arrival.

Verification

The intended change happens when you actually arrive, or when the time actually passes.

Action

Start with two actions and add more only after a week of reliable running.

Why it helps

Long automations fail in ways that are hard to diagnose, and a failed automation is worse than none because you have stopped doing the thing manually.

Verification

Each automation still runs correctly a week later.

Action

Map one shortcut to the Action button if your iPhone has one, or to a Back Tap gesture if it does not.

Why it helps

A shortcut you cannot reach quickly does not get used. Back Tap, under Accessibility, works on models without an Action button.

Verification

The shortcut runs from the button or from a double tap on the back of the phone.

What not to automate

Anything where a failure is expensive or invisible. Automations that send messages without confirmation, delete files, or change security settings are a bad idea, because a mis-triggered automation is discovered late. Keep automations to things that are reversible and visible — Focus modes, brightness, playback, timers, and reminders.

How it works

Shortcuts is a visual action pipeline. Each action produces an output, and that output is passed as the input to the next action — Get Current Location produces a location, which Send Message accepts as content. That chaining is why no code is required: the app only offers you actions that can accept what the previous step produced, so invalid combinations are largely impossible to build.

Automations add a trigger evaluated by the system rather than by the app. Time triggers use the scheduler; location triggers use geofences that iOS monitors with the same low-power hardware behind Reminders and Find My, which is why an arrival automation does not meaningfully affect battery. Battery, alarm, and CarPlay triggers are system events the automation subscribes to.

The Run Immediately setting matters more than it looks. Historically every automation required confirmation, which made them nearly pointless; running without a prompt is what turns them from a novelty into infrastructure. iOS still restricts a few sensitive action types from running unattended, which is the reason to keep automations limited to reversible, visible changes — those are exactly the ones the system will run without asking.

Worked example

Building the low-battery automation, start to finish.

Open Shortcuts, tap Automation, tap +, choose Battery Level. Drag the slider to 30% and select Falls Below 30%. Tap Next. Add the action Set Low Power Mode and confirm it is set to turn on. Add Set Brightness to 40%. Choose Run Immediately and turn off Notify When Run. Done — about ninety seconds.

The test comes that afternoon at 15:40, when the battery reaches 30% during a long day out. Low Power Mode turns on silently, brightness drops, and nothing asks for permission. The phone reaches home at 17% rather than dying — the ten percentage points between the automation firing at 30% and iOS's own prompt at 20% are what made the difference.

One refinement after a week: on days spent at a desk with a charger, the automation is unnecessary but harmless, since plugging in reverses Low Power Mode automatically. The owner leaves it alone rather than adding a condition — which is the right call, because the simplest automation that works is the one still running a year later.