Pushcut links smart notifications with Shortcuts, local triggers, webhooks, and Automation Server actions. Strawberry can map a visible automation and identify the decision behind each notification action. It can prepare a test checklist and catch a shortcut that would run in the wrong place or at the wrong time.
01
Trace the tap before it triggers a shortcut.
A Pushcut notification can include actions that invoke a shortcut, open a URL, or trigger an online action. Strawberry can follow the visible setup into a readable action map. This helps you verify what each button actually initiates before it reaches a device.
02
Find trigger collisions before they become strange behaviour.
Time, location, HomeKit, and shortcut-based triggers can overlap in ways that are hard to see from one card at a time. A focused review can identify visible conditions that compete, repeat, or leave an automation with no clear owner.
03
Test the automation with the real context attached.
A webhook URL or a shortcut input can look correct while the real device state makes it unsafe or useless. Strawberry can prepare a scenario-based test sheet from the configured inputs, expected notification, user action, and downstream result.
04
Use a Friday review to protect the weekend automations.
A 16:30 Friday check is a useful point to inspect Pushcut flows that will run while their owner is away. This is especially useful for location or schedule-based triggers. It produces a test and exception list rather than changing an iOS automation on its own.