Workflows (event triggers)
Event-driven automations: Wi-Fi, Bluetooth, battery, charger, location, apps, notifications, screen and time triggers with conditions.
A workflow runs a list of tool actions automatically when something happens on your phone. You create and manage workflows by asking CX in chat; there is no separate workflows screen in this version.
When I connect to HomeWiFi, run the "home" SSH command and message me on Telegram.
Every day at 9 pm, if battery is below 30%, remind me to charge.
When a notification from my bank contains "debited", send it to my Telegram.
CX shows an approval card summarising "When … / Do: 1. … 2. …" before saving.
Triggers#
| Trigger | Parameters |
|---|---|
time_cron |
A 5-field cron (max once a minute) or a daily time (HH:mm) with optional days of week. |
wifi_connected / wifi_disconnected |
Optional SSID. |
bluetooth_device_connected / _disconnected |
Optional device address. |
headphones_plugged / _unplugged |
– |
power_connected / power_disconnected |
Charger plug/unplug. |
battery_below / battery_above |
Threshold %, fires on crossing. |
geofence_enter / geofence_exit |
Latitude, longitude, radius 50–5000 m, label. |
app_launched / app_closed |
Package name. |
notification_received |
Package name, title/text contains, or title/text regex. Needs notification access (see note). |
boot_completed, screen_on, screen_off |
– |
manual |
Only runs via "run now". |
All workflow triggers are recurring. For a one-time action use a scheduled job instead.
Conditions (all must pass)#
Time between, after sunset / before sunrise (with offset), day of week, Wi-Fi SSID is / in, battery above/below, charging / not charging, foreground app is / in, screen on/off. Any condition can be inverted ("when NOT on that Wi-Fi").
Actions and limits#
- Each action is a tool call with arguments and optional timeout.
- Cooldown (seconds) and max runs per day prevent runaway workflows.
- A workflow cannot start another workflow (no chaining).
- Actions run without per-tool approval at fire time; hardline blocks still apply.
- Disabled workflows keep their definition and history but unregister their triggers (battery-friendly).
Ask CX to "list my workflows", "disable the battery workflow", "run the home workflow now" or "delete it".
notification_received and the notification tools only work in builds that include notification access. The standard build ships without it (see Notification access). Location triggers need precise location permission; Bluetooth triggers need Nearby devices permission.