> **Building with AI coding agents?** Install the authstack plugin with one command. This equips your agent with accurate Scalekit implementation patterns.
>
> **Recommended** (the `-y` flags skip prompts, so the command runs without an interactive terminal):
> ```bash
> npx -y @scalekit-inc/cli setup -y
> ```
>
> Global:
> ```bash
> npm install -g @scalekit-inc/cli
> scalekit setup -y
> ```
>
> Supports Claude Code, Cursor, GitHub Copilot, Codex + skills for other Agent Skills-compatible agents in `~/.agents/skills`.
> Skills: integrate-agentkit, implement-saaskit, add-mcp-oauth, implement-sso, implement-scim.
> [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Connect AI agents to Cronly

The Cronly connector lets your AI agent act in each user's Cronly account. Each user connects their own Cronly access token once, and Scalekit sends it with every call, so your agent never handles credentials. It comes with 24 tools.

**Authentication:** Bearer Token
**Categories:** Monitoring, Developer Tools
**Tools:** 24: 14 read, 5 write, 5 destructive
**Users sign in with:** Access token
**Built by:** Scalekit connector
**Try it:** [Playground in the Scalekit dashboard](https://app.scalekit.com/ws/signup?sk_intent=playground&provider=CRONLY)

## Setup

1. ### Install the SDK

   **Node.js**

   ```bash
   npm install @scalekit-sdk/node dotenv
   ```

   **Python**

   ```bash
   pip install scalekit-sdk-python python-dotenv
   ```

2. ### Set your credentials

   Add your Scalekit credentials to your `.env` file. Find values in **[app.scalekit.com](https://app.scalekit.com)** > **Developers** > **API Credentials**.

   ```sh title=".env"
   SCALEKIT_ENVIRONMENT_URL=<your-environment-url>
   SCALEKIT_CLIENT_ID=<your-client-id>
   SCALEKIT_CLIENT_SECRET=<your-client-secret>
   ```

3. ### Create the Cronly connection

   In **AgentKit > Connections**, create a Cronly connection. The name you give it is the `connection_name` your code passes. See [Configure connections](/agentkit/connections/).

4. ### Authorize a user and make your first call

   **Node.js** (`quickstart.mts`)

   ```typescript
   import { ScalekitClient } from '@scalekit-sdk/node'
   import 'dotenv/config'
   import { createInterface } from 'node:readline/promises'

   const scalekit = new ScalekitClient(
     process.env.SCALEKIT_ENVIRONMENT_URL,
     process.env.SCALEKIT_CLIENT_ID,
     process.env.SCALEKIT_CLIENT_SECRET,
   )
   const actions = scalekit.actions

   const connector = 'cronly'
   const identifier = 'user_123'

   // Generate an authorization link for the user
   const { link } = await actions.getAuthorizationLink({ connectionName: connector, identifier })
   console.log('Authorize Cronly:', link)
   const rl = createInterface({ input: process.stdin, output: process.stdout })
   await rl.question('Press Enter after authorizing...')
   rl.close()

   // Make your first call
   const result = await actions.executeTool({
     connector,
     identifier,
     toolName: 'cronly_backups_list',
     toolInput: {},
   })
   console.log(result)
   ```

   ```bash
   npx tsx quickstart.mts
   ```

   **Python** (`quickstart.py`)

   ```python
   import os
   from scalekit import ScalekitClient
   from dotenv import load_dotenv
   load_dotenv()

   scalekit_client = ScalekitClient(
       env_url=os.getenv("SCALEKIT_ENVIRONMENT_URL"),
       client_id=os.getenv("SCALEKIT_CLIENT_ID"),
       client_secret=os.getenv("SCALEKIT_CLIENT_SECRET"),
   )
   actions = scalekit_client.actions

   connection_name = "cronly"
   identifier = "user_123"

   # Generate an authorization link for the user
   link_response = actions.get_authorization_link(
       connection_name=connection_name,
       identifier=identifier,
   )
   print("Authorize Cronly:", link_response.link)
   input("Press Enter after authorizing...")

   # Make your first call
   result = actions.execute_tool(
       tool_input={},
       tool_name="cronly_backups_list",
       connection_name=connection_name,
       identifier=identifier,
   )
   print(result)
   ```

   ```bash
   python quickstart.py
   ```

   Each user opens the link once and enters their Cronly credentials there. See [Authorize a user](/agentkit/tools/authorize/) for the full flow and statuses.

## Tools

Pass the exact name to `execute_tool`, with an input like each tool's example. To ask for a tool that's missing, use the [request form](https://scalekitsupport.portal.usepylon.com/forms/request-a-connector-tool).

**Node.js**

```typescript
const result = await actions.executeTool({
  toolName: 'cronly_backup_get',
  toolInput: {
    server_id: '<server_id>',
    username: '<username>',
  },
  connector: 'cronly',
  identifier: 'user_123',
})
```

**Python**

```python
result = actions.execute_tool(
    tool_name="cronly_backup_get",
    tool_input={
        "server_id": "<server_id>",
        "username": "<username>",
    },
    connection_name="cronly",
    identifier="user_123",
)
```

`result.data` is the app's response as JSON, and `result.execution_id` (`executionId` in Node.js) is the ID of the call.

### `cronly_backup_get`

Get Crontab Back-up · Read-only

Get the crontab back-up for one user on one server, with its snapshots.
Returns the back-up and its crontab file contents; 404 when not found.
Use cronly_backups_list to see what exists.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `server_id` (`string`, required): Identifier of the server (the identifier you set when creating it), from cronly_servers_list. Example: web-01.
- `username` (`string`, required): Username on the server whose crontab back-up this is. Example: deploy.

Example input: `{"server_id":"<server_id>","username":"<username>"}`

### `cronly_backups_list`

List Crontab Back-ups · Read-only

List the crontab back-ups stored in Cronly.
Returns each back-up's server, username and snapshots.
Use cronly_backup_get for one back-up's contents.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `cronly_certificate_get`

Get SSL Certificate Monitor · Read-only

Get one SSL certificate monitor.
Returns its hostname, port, certificate details, expiry date and status; 404 when not found.
Use cronly_certificates_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `certificate_id` (`integer`, required): Numeric ID of the certificate. Get it from cronly_certificates_list. Example: 88.

Example input: `{"certificate_id":88}`

### `cronly_certificates_list`

List SSL Certificate Monitors · Read-only

List the SSL certificate monitors in your Cronly account.
Returns each monitor's id, hostname, port, issuer, expiry date and status.
Use this to see which certificates expire soon.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `cronly_company_get`

Get Company · Read-only

Get your Cronly company (organisation) details and notification settings.
Returns the company's name, timezone, plan and notification channel settings.
Use this to check the connection works.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `cronly_monitor_get`

Get Job Monitor · Read-only

Get one cron job monitor with its schedule, status and recent pings.
Returns the monitor's id, name, token, schedule, timezone, duration, project and status; 404 when not found.
Use cronly_monitors_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `monitor_id` (`integer`, required): Numeric ID of the monitor. Get it from cronly_monitors_list. Example: 1042.

Example input: `{"monitor_id":1042}`

### `cronly_monitors_list`

List Job Monitors · Read-only

List all cron job monitors in your Cronly account.
Returns each monitor's id, name, ping token, schedule, timezone, maximum duration, project and current status.
Use this to find a monitor ID or its ping token.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `cronly_notifications_list`

List Notifications · Read-only

List the notifications Cronly has raised (late, failed or recovered jobs, expiring certificates), newest first, with paging.
Returns data with each notification's type, message, related monitor and time, plus paging info.
Use this to see recent alerts.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `page` (`integer`, optional): Page to return. Defaults to 1. Example: 1.
- `per_page` (`integer`, optional): Results per page. Defaults to 10. Example: 10.

Example input: `{}`

### `cronly_project_get`

Get Project · Read-only

Get one Cronly project with its monitors.
Returns the project's id, name and monitors; 404 when not found.
Use cronly_projects_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Get it from cronly_projects_list. Example: 12.

Example input: `{"project_id":12}`

### `cronly_projects_list`

List Projects · Read-only

List the projects used to group monitors in Cronly.
Returns each project's id and name.
Use this to find a project_id.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `cronly_server_get`

Get Server · Read-only

Get one registered server.
Returns the server's id, name, identifier and IP address; 404 when not found.
Use cronly_servers_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `server_id` (`integer`, required): Numeric ID of the server. Get it from cronly_servers_list. Example: 3.

Example input: `{"server_id":3}`

### `cronly_servers_list`

List Servers · Read-only

List the servers registered for crontab back-ups.
Returns each server's id, name, identifier and IP address.
Use this to find a server identifier for back-ups.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `cronly_user_get`

Get User · Read-only

Get one user in your Cronly organisation.
Returns the user's id, name, email and role; 404 when not found.
Use cronly_users_list to find IDs.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs:

- `user_id` (`integer`, required): Numeric ID of the user. Get it from cronly_users_list. Example: 7.

Example input: `{"user_id":7}`

### `cronly_users_list`

List Users · Read-only

List the users (employees) in your Cronly organisation.
Returns each user's id, name, email and role.
Use this to see who has access.

Read only: yes. Destructive: no. Idempotent (safe to retry): yes.

Inputs: none.

Example input: `{}`

### `cronly_certificate_create`

Create SSL Certificate Monitor · Write

Start monitoring the SSL certificate of a hostname so Cronly warns you before it expires.
Returns the new certificate monitor.
Use cronly_certificates_list to see all monitored hosts.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `hostname` (`string`, required): Hostname to check, without https://. Example: www.example.com.
- `port` (`integer`, optional): TLS port. Defaults to 443. Example: 443.
- `project_id` (`integer`, optional): Project to group it under, from cronly_projects_list. Example: 12.

Example input: `{"hostname":"<hostname>"}`

### `cronly_monitor_create`

Create Job Monitor · Write

Create a cron job monitor that expects a ping on a cron schedule and alerts you when a run is late or too slow.
Returns the new monitor with its id and the token your job pings.
Make the job call https://cronly.app/api/monitors/pulse/<token> (or use cronly_monitor_pulse) each time it runs.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `duration` (`integer`, required): Maximum minutes the job may run before it counts as late. Example: 30.
- `name` (`string`, required): Monitor name. Example: Nightly database backup.
- `schedule` (`string`, required): Cron expression for when the job runs. Example: 0 2 * * *.
- `timezone` (`string`, required): IANA time zone the schedule is in. Example: UTC.
- `project_id` (`integer`, optional): Project to group it under, from cronly_projects_list. Example: 12.

Example input: `{"duration":30,"name":"<name>","schedule":"<schedule>","timezone":"<timezone>"}`

### `cronly_monitor_pulse`

Send Monitor Ping · Write

Record a heartbeat (pulse) for a job monitor, the same ping a monitored job sends when it runs.
Returns status ok.
Use this to mark a job run from an agent or workflow. The token comes from cronly_monitors_list.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `monitor_token` (`string`, required): The monitor's ping token (a UUID), from cronly_monitors_list or cronly_monitor_create. Example: 6e9c5250-a609-4fcc-aec8-710104fd744e.

Example input: `{"monitor_token":"<monitor_token>"}`

### `cronly_project_create`

Create Project · Write

Create a project to group monitors.
Returns the new project with its id.
Pass its id as project_id when creating monitors.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `name` (`string`, required): Project name. Example: Billing service.

Example input: `{"name":"<name>"}`

### `cronly_server_create`

Register Server · Write

Register a server whose crontab back-ups Cronly stores. Back-ups are only accepted from the server's IP address.
Returns the new server.
Use the identifier you set here as server_id in the back-up tools.

Read only: no. Destructive: no. Idempotent (safe to retry): no.

Inputs:

- `identifier` (`string`, required): Your own unique identifier for the server. Example: web-01.
- `ip_address` (`string`, required): Public IP address the server sends back-ups from. Example: 203.0.113.10.
- `name` (`string`, required): Server name. Example: Web server 1.

Example input: `{"identifier":"<identifier>","ip_address":"<ip_address>","name":"<name>"}`

### `cronly_backup_delete`

Delete Crontab Back-up · Destructive

Delete the crontab back-up for one user on one server.
Returns status ok, or 404 when not found.
Use cronly_backups_list to see what exists.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `server_id` (`string`, required): Identifier of the server (the identifier you set when creating it), from cronly_servers_list. Example: web-01.
- `username` (`string`, required): Username on the server whose crontab back-up this is. Example: deploy.

Example input: `{"server_id":"<server_id>","username":"<username>"}`

### `cronly_certificate_delete`

Delete SSL Certificate Monitor · Destructive

Stop monitoring a certificate and delete its monitor.
Returns status ok, or 404 when not found.
Use cronly_certificates_list to find IDs.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `certificate_id` (`integer`, required): Numeric ID of the certificate. Get it from cronly_certificates_list. Example: 88.

Example input: `{"certificate_id":88}`

### `cronly_monitor_delete`

Delete Job Monitor · Destructive

Delete a cron job monitor. Pings to its token stop being recorded.
Returns status ok, or 404 when not found.
Use cronly_monitors_list to find IDs.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `monitor_id` (`integer`, required): Numeric ID of the monitor. Get it from cronly_monitors_list. Example: 1042.

Example input: `{"monitor_id":1042}`

### `cronly_project_delete`

Delete Project · Destructive

Delete a Cronly project.
Returns status ok, or 404 when not found.
Use cronly_projects_list to find IDs.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `project_id` (`integer`, required): Numeric ID of the project. Get it from cronly_projects_list. Example: 12.

Example input: `{"project_id":12}`

### `cronly_server_delete`

Delete Server · Destructive

Delete a registered server.
Returns status ok, or 404 when not found.
Use cronly_servers_list to find it.

Read only: no. Destructive: yes. Idempotent (safe to retry): yes.

Inputs:

- `server_id` (`integer`, required): Numeric ID of the server, from cronly_servers_list. Example: 3.

Example input: `{"server_id":3}`

## Related

Other Monitoring connectors ([all 48](/agentkit/connectors/?category=monitoring)):

- [Datadog](/agentkit/connectors/datadog/): Scalekit connector, API key, 105 tools
- [1Password](/agentkit/connectors/onepassword/): Scalekit connector, Access token, 4 tools
- [Malwarebytes](/agentkit/connectors/malwarebytes/): Scalekit connector, Service account, 74 tools


---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |
