Review a Job Monitor
Inspect a monitor’s returned schedule and notification settings.
/oo Cronitor: Read Cronitor monitor [monitor key]. Summarize its returned type, schedule, assertions, and notification settings.
Choose a monitor key to review its settings, or supply a job schedule for a new monitor.
Copy a prompt into your agent with the oo Skill installed. Add your page links and source notes before running it.
Inspect a monitor’s returned schedule and notification settings.
/oo Cronitor: Read Cronitor monitor [monitor key]. Summarize its returned type, schedule, assertions, and notification settings.
Register a monitor using an explicit job schedule and timezone.
/oo Cronitor: Create a Cronitor job monitor with key [unique monitor key], name “[job name]”, schedule [cron expression], and timezone [timezone]. Report the returned configuration.
Set up oo CLI and the oo Skill in your agent.
Install OOMOL →Connect a Cronitor API key.
Connect Cronitor →Use /oo with the pages to read, the changes to make, and where to save the result.
Connection Guide →Choose Your Agent
This connection lists, reads, creates, updates, and deletes Cronitor monitors.
Inspect and manage monitor definitions.
List Cronitor monitors in the current account.
cronitor.list_monitors Get a Cronitor monitor by key.
cronitor.get_monitor Create one Cronitor monitor.
cronitor.create_monitor Update one Cronitor monitor by key.
cronitor.update_monitor Delete a Cronitor monitor by key.
cronitor.delete_monitor No matching tools.
Monitor creation accepts job, check, heartbeat, or site. Choose the type matching what you want to monitor.
Yes. Monitor configuration accepts a timezone used to evaluate the schedule.
It creates the monitor definition. Execution reporting requires the job’s Cronitor integration; this connection does not send execution telemetry.
Manage which optional storage OOMOL can use. You can change these choices from the footer at any time.