Cronly
Search…
🪝
Webhooks
Webhooks allow you to actively respond to events, from within your own environment.
How webhooks are used
Webhooks are part of triggers. You can set up a webhook endpoint URL for each trigger you've created. Just go to the trigger, edit the trigger and set a webhook endpoint URL. For every event that occurs that fires that trigger, the webhook endpoint URL is called.
Cronly sends an HTTP request with
POST data, and JSON contents.Request to your webhook
You can match the private key within your own webhook to validate the alert is really coming from Cronly. The private key of each trigger can be found inside your trigger details.
Each event can have one of the following statuses.
notificationThis is for certificates only, to inform you of nearly expiring certificates.alertThere is a problem with either your cron job or certificate.clearedThe existing problem was cleared.
Each event can have one of the following types.
cronThis event is for a cron job monitor.certificateThis event is for an SSL certificate monitor.
The
object can be either a cron job or certificate.Request body example for a cron job
1
{
2
"private_key": "abc847ce-2f24-4c92-99ee-203ccc47d619",
3
"event": {
4
"id": 1,
5
"type": "cron",
6
"status": "alert",
7
"title": "Test trigger",
8
"description": "DEPRECATED",
9
"added": "2022-05-30 14:31:22",
10
"timezone": "UTC"
11
},
12
"object": {
13
"id": 1,
14
"added": "2022-05-30 14:31",
15
"project": null,
16
"name": "Test",
17
"schedule": "* * * * *",
18
"previousRun": "2022-05-30 14:42:55",
19
"nextRun": null,
20
"lastCheck": "2022-05-30 14:42:55",
21
"lastPulse": "2022-05-30 14:42:55",
22
"timezone": "UTC",
23
"status": "alert",
24
"archive": false
25
}
26
}
Copied!
Request body example for an SSL certificate
1
{
2
"private_key": "abc847ce-2f24-4c92-99ee-203ccc47d619",
3
"event": {
4
"id": 1,
5
"type": "certificate",
6
"status": "healthy",
7
"title": "Test trigger",
8
"description": "DEPRECATED",
9
"added": "2022-05-30 14:31:22",
10
"timezone": "UTC"
11
},
12
"object": {
13
"id": 1,
14
"added": "2022-05-30 14:28:32",
15
"project": null,
16
"hostName": "cronly.app",
17
"port": 443,
18
"lastCheck": "2022-05-30 14:28:32",
19
"status": "valid",
20
"archive": false
21
}
22
}
Copied!
Expected response
Successful response
We wait for a response from your webhook and fetch and store the response for you to review. The response should have a
200 OK HTTP response, if everything works as expected. We store your complete response.Error response
Any other response code will be interpreted as an error. Cronly sends out an e-mail notification to all email addresses related to the trigger. You can review the response in Cronly.
Last modified 1mo ago