Alerts and routines
routineDestructive
Set up a routine: a question RoBot answers again by itself, on a schedule (“every morning at 8: how did my games and their rivals do?”) or when something happens (a trigger), with a note to the person’s notifications (and Discord or email if connected). Use it for “every morning”, “each Monday”, “keep me posted”, “tell me when”, “alert me if”. Each run is RoBot answering, on the person’s RoBot usage. Actions: create (name, question, and every or trigger_sql), update (id, and only what changes), pause, resume, delete, restore, run (once now), list. question is asked whole on each run: name the games and what to compare. Times are New York’s. Opens with RoBot: an account RoBot isn’t open on yet gets not_available.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| at | No | The time of day in New York as HH:MM (24-hour), for day and week; default 08:00 | |
| id | No | The routine’s id (from create or list), for every action but create and list | |
| name | No | A short name in plain words, like "Morning check-in" | |
| every | No | How often, for a routine on a schedule | |
| action | Yes | ||
| deliver | No | Where its note goes (default bell) | |
| minutes | No | For every: minutes, 15 to 1440 | |
| weekday | No | For week; default Mon | |
| question | No | What RoBot is asked on each run, whole and on its own | |
| trigger_sql | No | For a trigger: one read-only SQL query over RoTerminal’s research tables, a row for each thing that has happened, its first column that thing’s key, newest first, LIMIT 50 at most | |
| cooldown_hours | No | For a trigger: the least time between its runs, 0.25 to 168 (default 6) | |
| max_fires_per_day | No | For a trigger: the most runs in a New York day, 1 to 24 (default 3) | |
| check_every_minutes | No | For a trigger: how often it’s checked, 5 to 1440 (default 15) |