Actionable notification triggers

Pushcut sends notifications whose buttons can start a shortcut or automation, and a Beam agent decides when to fire them. Reading an event from a connected system, the agent checks it against your rules and sends the matching Pushcut notification with the right action attached. A routine trigger, like a reminder tied to a schedule, goes out on its own. An event that would run an action you marked as impactful, such as unlocking or a bulk change, is instead sent for a person to confirm with a tap before anything in the home responds.

Scheduled scene routines

Pushcut can run scenes and shortcuts on a timer, and a Beam agent keeps those routines aligned with real conditions. Ahead of each scheduled run, the agent reads the inputs the routine depends on, such as presence or a sensor state, and lets the scene proceed only when your rule agrees it should. Routines that pass run as planned. A run whose conditions look contradictory, or whose sensor data is missing, is skipped and reported to the owner, so the home does not act on stale or conflicting readings without a person looking.

Server and webhook automation

Pushcut exposes automation servers and webhooks that let outside events start a shortcut, and a Beam agent drives those endpoints under your rules. When an upstream trigger arrives, the agent reads its payload, decides which Pushcut automation fits, and calls the endpoint with the values it needs, then notes the outcome. Standard automations proceed without help. A call that would touch a device your rules treat as critical, or that carries an unrecognized payload, is paused and escalated to a person before the agent invokes anything sensitive.