Skip to content

Start building

Integration · Developer

AI agents for Cronitor

Watch cron jobs, heartbeats and uptime checks in Cronitor.

Actions
9
Read
3
Write
6

Actions

What your agents can do in Cronitor

Watch cron jobs, heartbeats and uptime checks in Cronitor: find failing or paused monitors, read a monitor's latest run, create monitors, pause and resume them around maintenance, and open, update and resolve issues, with a Cronitor API key.

Read 3

Look things up. Nothing changes.

  • List monitors

    Lists monitors (cron jobs, heartbeats, uptime checks, sites), searched by name or key and filtered by type, state (failing, passing, paused, running), group, tags or environment.

  • Get a monitor

    Reads one monitor by key: its configuration (schedules, assertions, notify, grace_seconds, timezone, the check's request), its status.

  • List issues

    Lists issues (incidents Cronitor opened on a failure, or ones people opened), newest first, filtered by state.

Write 6

Create, change or send.

  • Create a monitor

    Creates a monitor: a job (a cron job that pings Cronitor when it runs, expected on schedules such as "0 0 * * *" or "every 5 minutes"), a heartbeat, or a check.

  • Pause a monitor

    Pauses one monitor's alerts for a number of hours, for a maintenance window or a deploy; it resumes on its own afterwards.

  • Resume a monitor

    Ends a monitor's pause now, so its alerts and checks start again.

  • Delete a monitorDeletes data

    Deletes a monitor and its history for good.

  • Open an issue

    Opens an issue with a name, severity and state, and optionally a first update message, the email of the team member it is assigned to, and the status pages (and their components) to publish it on.

  • Update an issue

    Changes an issue's state (resolve it with resolved), severity, name or assignee, and adds an update message to its timeline.

A person can approve first

Any write action can be set to wait for a person's approval before it runs, so an agent asks before it changes anything. Actions that delete data ask first by default.

Connection

How it connects

Connect it once in the console, then give it to the agents and workflows that need it.

Username and key

Enter the API credentials from your Cronitor account.

What you enter

  • API key

Kept safe

  • Credentials are stored encrypted with your organization's own keys.
  • They are opened only by the process that makes the call, at the moment it runs, and never go into a prompt or the browser.
  • Calls go only to the tool's own servers.

How we protect your data

Ideas

Ideas to start with

Starting points made only from the actions above. Mix them with any other tool your agents can use.

  • 01

    Ask about your Cronitor data

    Ask a question in plain words. The agent can list monitors, get a monitor or list issues in Cronitor, then answers with what it found.

  • 02

    Let an agent update Cronitor

    Have the agent create a monitor or pause a monitor in Cronitor as part of a larger task. Turn on approval and a person signs off on each change first.

  • 03

    Share what it finds in Slack

    Give one agent Cronitor and Slack: it can list monitors in Cronitor and post a summary to a Slack channel in the same run.

FAQ

Cronitor and MyDeepAgents

Can MyDeepAgents connect to Cronitor?

Yes. The Cronitor connector has 9 actions: 3 read and 6 make changes. Your agents can call them as tools, and your workflows can run them as steps.

How do I connect Cronitor?

Enter the API credentials from your Cronitor account. You'll need: API key. Credentials are stored encrypted with your organization's own keys and are opened only at the moment of a call.

Can an agent change data in Cronitor without asking?

Only if you let it. Each of the 6 actions that change data can be set to wait for a person's approval before it runs, and the one that deletes data asks first by default.

Can I use Cronitor in workflows as well as agents?

Yes. Every Cronitor action also works as a step in a workflow, and the same connection serves your agents and your workflows.

Early access

Put Cronitor to work

Connect it in a few minutes, give an agent the actions it needs, and decide which changes wait for a person.