iOS Shortcuts NFC Triggers: Automations That Actually Work

Quick answer

An NFC Tag trigger in Shortcuts fires a personal automation the moment your iPhone taps a registered tag. It reads the tag's unique identifier only — not whatever's written to it. So you don't need a specific URL, NDEF text record, or vCard sitting on the tag for the automation to fire; a completely blank tag works just as well as one with content. What actually matters is your iPhone model. Background tag reading needs iPhone XS, iPhone XR, or later, running iOS 13.1+.

Coming from Android's Tasker-based NFC automation? Same idea — tap a tag, run a task — but different mechanics. Shortcuts keys off the tag's UID, not its contents, so there's no equivalent to reading a payload as part of the trigger logic.

Step-by-step

Creating the automation. Open Shortcuts, go to the Automation tab, and choose Create Personal Automation. Pick "When I tap an NFC tag," scan the physical tag — hold it near the camera module on newer iPhones — and give it a name you'll actually recognize later.

Adding an action. Attach whatever the tap should do: a HomeKit scene, a Focus mode, an app launch, Do Not Disturb, or a multi-step Shortcut. Want it to run the instant you tap, no confirmation sheet? Turn off "Ask Before Running" in the automation's settings.

Choosing a tag. Any standard NTAG-class tag works, since the trigger reads UID rather than content — a $10 bulk pack of a dozen tags is plenty. Using NFCore to write a label or backup record to the same tag? Order doesn't matter.

Common problems and fixes

"My automation won't fire in the background." Almost always a hardware issue, not a setup mistake. iPhone X and earlier lack the low-power radio needed for background tag reading, so you'd have to launch an app manually before the scan registers — at which point you might as well open the Shortcut directly. Check whether your phone supports NFC before troubleshooting further. Still inconsistent on a supported device? See why iPhone background NFC reading needs a universal link in some configurations.

"It fires, but it asks me to confirm every time." "Ask Before Running" is still switched on for that automation. Turn it off in the automation's detail view for true one-tap execution.

"The tag used to work, and now it doesn't." It may have been overwritten, damaged, or you're scanning it at an odd angle. Skip the troubleshooting — delete the old registration and re-scan the tag as a fresh automation.

Doing this on NFCore specifically

NFCore's job here isn't the automation — Shortcuts owns that — it's managing what's actually on the tag. Use NFCore to write a plain-text label so you can identify the tag later in Tag Inspector, back up its original NDEF record before you repurpose it, or batch-write a stack of identical tags for a family or small team. None of that interferes with a Shortcuts trigger already registered on the same tag; the trigger never reads the payload. Setting up several NFC automations around the house or office? Pair NFCore for tag management with Shortcuts for the automation logic, and download NFCore from the App Store to get started.

Frequently Asked Questions

Does the NFC tag need to have anything written on it for Shortcuts to trigger?

No. The Shortcuts NFC trigger keys off the tag's unique identifier only — whatever else is written to the tag, like a URL, text record, or vCard, gets ignored by the automation. A brand-new, blank tag will still fire the automation once you've scanned and named it.

Why doesn't my NFC automation run in the background?

Background NFC tag reading for Shortcuts requires iPhone XS, iPhone XR, or later on iOS 13.1+. Older models like the iPhone X lack the low-power background NFC radio, so you'd have to open an app first to scan the tag — which defeats the point of a tap-to-trigger automation.

Can I use the same NFC tag for a Shortcuts automation and to store other data with NFCore?

Yes. A Shortcuts automation trigger and an app's read/write session are independent operations. NFCore can write a label, URL, or backup record to a tag, and that same tag can still trigger a Shortcuts automation, since the trigger never inspects the payload.

Do I need to disable "Ask Before Running" for the automation to feel instant?

If you want a true one-tap experience, yes. Leaving the confirmation prompt on turns a single tap into a tap-plus-confirm — the most common complaint about NFC automations feeling slow.

Conclusion

Most "my NFC automation doesn't work" reports trace back to one of two things: an iPhone X or older that can't read tags in the background, or a forgotten "Ask Before Running" prompt. Once you know the trigger only cares about the tag's UID and your device's hardware generation — not what's actually written to the tag — setup and troubleshooting both get simpler. From there, NFCore handles the other half of the job: labeling, backing up, and batch-writing the tags themselves.