Concept > Cron Jobs

Cron Job

Basics

Name

Each cron job has a name. You are free to choose what ever you want for the name. We recommend something like the app name plus the action that the hook is triggering.

Url

The url represents the endpoint in your application and must be a valid url.

Method

For the http method you have two options. The request can be made as a POST or as a GET request.

Frequency and Timezone

Cron Expression

A cron expression is a string consisting of five or six subexpressions (fields) that describe individual details of the schedule. These fields, separated by white space, can contain any of the allowed values with various combinations of the allowed characters for that field.

Name Required Allowed Values Allowed Special Characters

Minutes

Y

0-59

, - * /

Hours

Y

0-23

, - * /

Day of month

Y

1-31

, - * / L W C

Month

Y

0-11 or JAN-DEC

, - * /

Day of week

Y

1-7 or SUN-SAT

, - * /

Examples

Expression Means
0 12 * * * Fire at 12:00 PM (noon) every day

Timezone

If your cron expression is an exact point in time on a specific date or day, it is important to specify the right timezone.

For example: Your expression is 0 12 * * *. The expression stands for every day at 12 pm. Now it is important to select the timezone the cron job is expected to run in.

Headers

You can specify as many headers as you want for each cron job. Each header consists of a key and a value. There are no limitations for the content of this fields.

Payload

You can set a payload via the JSON editor in the cron job form. Every data structure is possible as long as it is valid JSON.

Authorization

If your endpoint is secured by the base auth method, you can store the username and password here. The authorization header will be automatically generated when the request is made.

You can specify custom headers to achieve all other sorts of authorisation method.

Read more about securing your endpoints in the security section.

SSL Verification

In the default configuration we are looking for a valid ssl cert on the endpoint. If you do not want this, for some reason, you can deactivate this on each cron job individually.