# iOS 27 Notifications and New Shortcuts

**URL:** <https://community.homey.app/t/ios-27-notifications-and-new-shortcuts/156044>\
**Category:** Ideas & Suggestions\
**Created:** [June 11, 2026, 9:04am UTC](https://community.homey.app/t/ios-27-notifications-and-new-shortcuts/156044 "2026-06-11T09:04:50Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_Evans](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_evans/32/80256_2.png) [@Michael\_Evans](https://community.homey.app/u/Michael_Evans)\
**Post date:** [June 11, 2026, 9:04am UTC](https://community.homey.app/t/ios-27-notifications-and-new-shortcuts/156044/1 "2026-06-11T09:04:50Z")

</div>

I’ve been playing with the new shortcuts in iOS 27 and one new feature is to automate a shortcut based on notifications. I tried a flow from Homey to send a push notification to me and created a shortcut to act on it, and it worked. BUT, I’m assuming the notification format coming from Homey isn’t completely compliant as the shortcut can’t read the content of the notification.

If the push notification from homey did work then it opens up a whole new step on potential on apple device automations as well as being able to make homepods speak.

For example, I created a shortcut that ran a command to speak “testing speach” on my homepod in my office if a notification came through from Homey. What I couldn’t do was get it to speak the text in the notification. If we could extract the text from a notification and act on it then it opens up so much.

---

<div class="post-metadata">

**Author:** ![smarthomesven](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/smarthomesven/32/79712_2.png) [@smarthomesven](https://community.homey.app/u/smarthomesven)\
**Post date:** [June 11, 2026, 10:12am UTC](https://community.homey.app/t/ios-27-notifications-and-new-shortcuts/156044/2 "2026-06-11T10:12:02Z")

</div>

> [@Michael\_Evans](#):
>
> If we could extract the text from a notification and act on it then it opens up so much

What can Homey do about it? That sounds like an issue with Apple.

---

<div class="post-metadata">

**Author:** ![Peter\_Kawa](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/peter_kawa/32/173848_2.png) [@Peter\_Kawa](https://community.homey.app/u/Peter_Kawa)\
**Post date:** [June 11, 2026, 11:08am UTC](https://community.homey.app/t/ios-27-notifications-and-new-shortcuts/156044/3 "2026-06-11T11:08:28Z")

</div>

All is possible with Android. Not to nag, just you might need other hardware.

---

<div class="post-metadata">

**Author:** ![Michael\_Evans](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/michael_evans/32/80256_2.png) [@Michael\_Evans](https://community.homey.app/u/Michael_Evans)\
**Post date:** [June 11, 2026, 1:14pm UTC](https://community.homey.app/t/ios-27-notifications-and-new-shortcuts/156044/4 "2026-06-11T13:14:57Z")

</div>

I believe it’s the way the notification is formatted so it is something Homey could change for iOS devices.

---

<div class="post-metadata">

**Author:** ![John\_William\_Brekke](https://sea1.discourse-cdn.com/flex025/user_avatar/community.homey.app/john_william_brekke/32/111887_2.png) [@John\_William\_Brekke](https://community.homey.app/u/John_William_Brekke)\
**Post date:** [June 12, 2026, 3:14pm UTC](https://community.homey.app/t/ios-27-notifications-and-new-shortcuts/156044/5 "2026-06-12T15:14:23Z")

</div>

In fact this is a Apple beta issue. The information isn’t extracted from any other apps even Apple’s own messages app. It might be available in later updates.