Stop Tapping. Let Your Phone Do It.
I've been setting up automations on iPhones since the first iOS 5 beta leaked. The core tool you need is the Shortcuts app that Apple ships pre-installed. Everything I'm about to describe runs through it. No jailbreak. No third-party installation services. Just the built-in system. Here's how the actual workflow looks when you're building something useful, not some demo shortcut that works once and breaks. Open Shortcuts. Tap the Automation tab at the bottom. Hit the plus sign in the upper right. Pick "Create Personal Automation." This is where most people get lost because the menu throws everything at you at once. Don't stare at the full list. Start with triggers that happen anyway.
The most reliable trigger to start with is "When I Arrive" or "When I Leave." These use geofencing. On the iPhone 13 Pro Max, location precision is solid because of the dual-frequency GPS module. I've had automations trigger within about 30 meters of my driveway for over two years without skipping a beat. The caveat: if you disable Location Services for the Shortcuts app itself, these stop working entirely. I learned that the hard way when I was tightening privacy settings and my morning routine shortcut just vanished from execution. Another trigger that actually works consistently is "At a Specific Time." This seems obvious but people skip it because they think timed automations aren't "real" automation. They are. I have one that fires at 6:45 AM every weekday. It turns on Do Not Disturb exception for repeated callers, sets my car's CarPlay screen to show my commute map, and reads my calendar events aloud. That's maybe forty-five seconds of manual work compressed into zero seconds of effort. Here's a counter-intuitive thing nobody mentions: the "When I Open an App" trigger is unreliable for anything time-sensitive. I tried building an automation that would launch a focus mode whenever I opened Instagram. It worked maybe half the time. The other half, the system processed the trigger after I'd already been scrolling for thirty seconds. Apple's automation engine prioritizes battery efficiency over trigger latency, so app-open events get queued and sometimes fired late. If you need instant reactions, don't use app-open triggers. Use shortcuts instead, or build it into the app's own workflow.
Let me walk through a real example I use daily. I wanted my phone to automatically connect to my home Wi-Fi, switch to a specific focus mode, launch Spotify, and set the volume to 30 percent when I walk through my front door. Here's the exact sequence: Create automation, choose "When I Arrive," select my home location, skip "Ask Before Running" on the first pass so it executes silently. For the actions, add "Join Wi-Fi Network," enter your SSID exactly as it appears in your Wi-Fi settings. Then "Set Focus," choose or create your home focus, add your usual apps as exceptions. Then "Play Music," set the playlist or artist. Then "Set Volume," type 30. That's it. Five actions. Runs in about four seconds on the A15 chip. Now the edge case that almost broke this entire setup: my router has both 2.4GHz and 5GHz bands with the same SSID. The automation kept connecting to the 5GHz band which has weaker range in my living room, causing spotty connectivity. The fix was creating two separate automations, one for each band's SSID, and letting iOS handle the band selection through normal Wi-Fi behavior. Don't try to force-band selection inside the shortcut. It doesn't work reliably.
Get the Full Details
There's a feature called "Run Immediately" that you need to toggle on for nearly every automation you build. If it's off, iOS shows you a confirmation dialog before executing. That defeats the whole point. The only automations where you should leave it off are ones that perform destructive actions like deleting files or sending messages to contacts. Even then, I'd argue you should just use a shortcut button on your home screen instead and keep the automation silent. The iPhone 13 Pro Max has a specific advantage for automation that the base model doesn't: the LiDAR scanner. You can build automations that trigger based on AR measurement triggers. I have one that detects when I place my phone on my nightstand (roughly 2 centimeters from a specific surface) and automatically starts Charging Focus with sleep-related app exceptions. The LiDAR-based detection is far more reliable than Bluetooth beacons for this use case. Bluetooth trackers drift. LiDAR doesn't. Here's what automation genuinely cannot do, and you'll waste hours trying if you don't know this upfront. It cannot read the contents of arbitrary apps and make decisions based on them. You can't say "check my email and if there's a message from my boss, call me." The Shortcuts app has limited app integration. Email shortcuts exist but they return metadata, not full message content you can parse with conditional logic. This is by design. Apple restricts this for privacy reasons and it's not going to change.
For anything that requires reading app content, you need a workaround. I use a combination of the "Get Current Event" action from Calendar, paired with "Get Details of Calendar Event" which does return the summary and notes fields. From there you can branch logic based on event titles. But this only works for calendar data. It doesn't work for Mail, Messages, or any third-party app. Accept that limitation early and design around it. Nested conditions in Shortcuts are painfully restrictive. You can chain "If" statements but each one opens a new block and the visual editor gets unwieldy fast. I hit a wall once trying to build a routine that checked weather, calendar, and battery level before deciding whether to wake me up at 6 AM or 7 AM. The shortcut grew to twenty-two actions and still failed under edge cases. I ended up splitting it into three separate automations that each handled one condition and called a master shortcut. It's not elegant but it's maintainable. One practical tip that saves everyone grief: test every automation by running it manually from the Shortcuts app before you let it run on a trigger. If you skip this step, you'll have automations firing silently with broken actions and you won't know until something goes wrong. I make it a rule to tap the play button on every new shortcut at least once in manual mode. Takes ten seconds and prevents hours of debugging later.
The Shortcuts app also supports variables across actions within a single shortcut. This means you can capture a value once and reuse it. For example, you can get the current date, format it, store it in a variable, and then use that formatted date in both a note-creation action and a calendar event action. Beginners often repeat the date-fetching action three or four times instead. It works either way but variables make the shortcut faster and easier to modify later. Another thing worth knowing: iOS 16 introduced the ability to run automations while the screen is locked, but only if you disable the "Require Face ID" option during setup. If you leave that enabled, the automation pauses until you unlock your phone. For morning routines and arrival automations, you want it to run before you touch the device. Toggle that setting off. Yes, it means any automation with sensitive actions like sending messages could theoretically run while locked, but you control which automations get that setting. There's a hidden limitation with widgets and automation interaction. You cannot trigger an automation from a home screen widget tap in the same reliable way you can from a shortcut button. Widget taps sometimes register, sometimes don't, and Apple doesn't document the behavior. If you need a manual trigger, use a home screen shortcut button. It's more consistent and you can customize the icon to look like anything.
Don't overlook the Backup and Restore workflow. Once you've built a set of automations you're happy with, export them. In the Shortcuts app, select multiple shortcuts, tap the three-dot menu, and choose Share. You get a .shortcut file you can email to yourself or store in iCloud Drive. I've restored my entire automation setup twice now after switching phones. Saved me probably four hours of reconfiguration work each time. Finally, a realistic assessment of what you're actually gaining. Setting up a comprehensive automation routine takes roughly two to three hours for a first-time user. After that, adding new automations usually takes ten to fifteen minutes each. The payoff isn't dramatic in any single day. It's cumulative. I estimate I save about twenty minutes per day across all my automations combined. Over a year that's roughly fifty hours. Not groundbreaking but completely passive. No extra effort required after the initial build. If you find yourself wanting automations that cross app boundaries in ways Shortcuts can't handle, the alternative is Switchboard or Intents, both third-party frameworks that require sideloading. I don't recommend them unless you need something very specific. They introduce security risk, they break on iOS updates, and they're generally more trouble than they're worth for daily use. Stick with native Shortcuts unless you've genuinely exhausted every option inside the app.
