# Cronly integrations: job monitors and projects

> Create a job monitor, create a project and create a certificate monitor in Cronly, and start a workflow when Cronly sends “Cron job alert”.

**Canonical page:** https://tray.ai/connectors/cronly-integrations/
**Categories:** IT
**Connects through:** HTTP Connector

## Overview

Cronly watches scheduled cron jobs through check-in URLs, runs HTTP endpoints on a schedule, and tracks SSL certificate expiry, alerting teams when something fails. Tray.ai connects to Cronly through the HTTP Connector, so your workflows can call the Cronly API alongside the rest of your stack.

## Use cases

### Job monitors

Read, create, and delete job monitors in Cronly from any Tray.ai workflow. The Cronly API covers calls such as list job monitors and get a job monitor.

- List job monitors
- Get a job monitor
- Create a job monitor

### Projects

Read, create, and delete projects in Cronly from any Tray.ai workflow. The Cronly API covers calls such as list projects and get a project.

- List projects
- Get a project
- Create a project

### SSL certificates

Read, create, and delete ssl certificates in Cronly from any Tray.ai workflow. The Cronly API covers calls such as list certificate monitors and get a certificate monitor.

- List certificate monitors
- Get a certificate monitor
- Create a certificate monitor

### Servers

Read, create, and delete servers in Cronly from any Tray.ai workflow. The Cronly API covers calls such as list servers and get a server.

- List servers
- Get a server
- Create a server

### Cronly events

Start a Tray.ai workflow the moment something happens in Cronly. Cronly sends events such as cron job alert and cron job alert cleared to a Tray.ai webhook trigger.

- Cron job alert
- Cron job alert cleared
- SSL certificate alert

## Challenges Tray.ai solves

### Keeping Cronly credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Cronly credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Cronly API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Cronly API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Cronly?

Yes. Tray.ai connects to Cronly through the HTTP Connector, which calls the Cronly API directly. Any call the Cronly API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Cronly?

The Cronly API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Cronly connector?

Cronly runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Cronly connector from the Cronly API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/