> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hookpulse.io/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Add Schedule (Cron)

> Create a new cron-based schedule that executes a webhook or workflow using standard cron expressions

Create a new cron-based schedule that executes a webhook or workflow using standard cron expressions with full timezone support.

## Base URL

All API requests should be made to:

```
https://api.hookpulse.io
```

## Example request

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://api.hookpulse.io/v1/api/add_cron_schedule/" \
    -H "x-hookpulse-api-key: {{x-hookpulse-api-key}}" \
    -H "x-brand-uuid: {{x-brand-uuid}}" \
    -H "Content-Type: application/json" \
    -d '{
      "cron_expression": "0 0 * * *",
      "cron_timezone": "Asia/Kolkata",
      "is_one_off_task": false,
      "schedule_to": "webhook",
      "model_to_schedule_uuid": "{{model_to_schedule_uuid}}",
      "initial_context_template": {
        "key": "value"
      }
    }'
  ```

  ```javascript JavaScript theme={null}
  const response = await fetch('https://api.hookpulse.io/v1/api/add_cron_schedule/', {
    method: 'POST',
    headers: {
      'x-hookpulse-api-key': '{{x-hookpulse-api-key}}',
      'x-brand-uuid': '{{x-brand-uuid}}',
      'Content-Type': 'application/json'
    },
    body: JSON.stringify({
      cron_expression: '0 0 * * *',
      cron_timezone: 'Asia/Kolkata',
      is_one_off_task: false,
      schedule_to: 'webhook',
      model_to_schedule_uuid: '{{model_to_schedule_uuid}}',
      initial_context_template: {
        key: 'value'
      }
    })
  });

  const data = await response.json();
  console.log(data);
  ```

  ```python Python theme={null}
  import requests

  url = 'https://api.hookpulse.io/v1/api/add_cron_schedule/'
  headers = {
      'x-hookpulse-api-key': '{{x-hookpulse-api-key}}',
      'x-brand-uuid': '{{x-brand-uuid}}',
      'Content-Type': 'application/json'
  }
  payload = {
      'cron_expression': '0 0 * * *',
      'cron_timezone': 'Asia/Kolkata',
      'is_one_off_task': False,
      'schedule_to': 'webhook',
      'model_to_schedule_uuid': '{{model_to_schedule_uuid}}',
      'initial_context_template': {
          'key': 'value'
      }
  }

  response = requests.post(url, headers=headers, json=payload)
  print(response.json())
  ```

  ```ruby Ruby theme={null}
  require 'net/http'
  require 'json'
  require 'uri'

  uri = URI('https://api.hookpulse.io/v1/api/add_cron_schedule/')
  http = Net::HTTP.new(uri.host, uri.port)
  http.use_ssl = true

  request = Net::HTTP::Post.new(uri)
  request['x-hookpulse-api-key'] = '{{x-hookpulse-api-key}}'
  request['x-brand-uuid'] = '{{x-brand-uuid}}'
  request['Content-Type'] = 'application/json'
  request.body = {
    cron_expression: '0 0 * * *',
    cron_timezone: 'Asia/Kolkata',
    is_one_off_task: false,
    schedule_to: 'webhook',
    model_to_schedule_uuid: '{{model_to_schedule_uuid}}',
    initial_context_template: {
      key: 'value'
    }
  }.to_json

  response = http.request(request)
  puts JSON.parse(response.body)
  ```

  ```php PHP theme={null}
  <?php

  $url = "https://api.hookpulse.io/v1/api/add_cron_schedule/";
  $data = [
      'cron_expression' => '0 0 * * *',
      'cron_timezone' => 'Asia/Kolkata',
      'is_one_off_task' => false,
      'schedule_to' => 'webhook',
      'model_to_schedule_uuid' => '{{model_to_schedule_uuid}}',
      'initial_context_template' => [
          'key' => 'value'
      ]
  ];

  $ch = curl_init($url);
  curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
  curl_setopt($ch, CURLOPT_POST, true);
  curl_setopt($ch, CURLOPT_POSTFIELDS, json_encode($data));
  curl_setopt($ch, CURLOPT_HTTPHEADER, [
      'x-hookpulse-api-key: {{x-hookpulse-api-key}}',
      'x-brand-uuid: {{x-brand-uuid}}',
      'Content-Type: application/json'
  ]);

  $response = curl_exec($ch);
  curl_close($ch);

  echo $response;
  ?>
  ```
</RequestExample>

## Request body

| Field                      | Type    | Required | Description                                                                                                                |
| -------------------------- | ------- | -------- | -------------------------------------------------------------------------------------------------------------------------- |
| `cron_expression`          | string  | Yes      | Standard cron expression (e.g., `"0 0 * * *"` for daily at midnight)                                                       |
| `cron_timezone`            | string  | Yes      | IANA timezone identifier (use [Get Timezone Options](/docs/api-reference/scheduling/timezone-options) to get valid values) |
| `is_one_off_task`          | boolean | Yes      | Set to `true` if the schedule should run only once, `false` for recurring execution                                        |
| `schedule_to`              | string  | Yes      | Target type: `"webhook"` or `"workflow"`                                                                                   |
| `model_to_schedule_uuid`   | string  | Yes      | UUID of the webhook or workflow template to schedule (as per `schedule_to`)                                                |
| `initial_context_template` | object  | No       | Key-value pairs passed as `{{ initial.key }}` variables to the webhook/workflow                                            |

## Example response

<ResponseExample>
  ```json theme={null}
  {
    "success": true,
    "details": "Schedule added successfully"
  }
  ```
</ResponseExample>

## Response fields

| Field     | Type    | Description                                        |
| --------- | ------- | -------------------------------------------------- |
| `success` | boolean | Indicates if the schedule was created successfully |
| `details` | string  | Success message                                    |

## Cron Expression Format

Cron expressions use the standard 5-field format:

```
* * * * *
│ │ │ │ │
│ │ │ │ └─── Day of week (0-7, where 0 and 7 are Sunday)
│ │ │ └───── Month (1-12)
│ │ └─────── Day of month (1-31)
│ └───────── Hour (0-23)
└─────────── Minute (0-59)
```

### Common Cron Examples

| Expression       | Description                             |
| ---------------- | --------------------------------------- |
| `0 0 * * *`      | Every day at midnight                   |
| `0 9 * * 1-5`    | Every weekday at 9 AM                   |
| `0 */6 * * *`    | Every 6 hours                           |
| `0 0 1 * *`      | First day of every month at midnight    |
| `0 0 1,15 * *`   | 1st and 15th of every month at midnight |
| `0 9 * * 0`      | Every Sunday at 9 AM                    |
| `*/15 * * * *`   | Every 15 minutes                        |
| `0 0-23/2 * * *` | Every 2 hours                           |

## Timezone Support

HookPulse supports all 500+ IANA timezones. Use the [Get Timezone Options](/docs/api-reference/scheduling/timezone-options) endpoint to get the complete list.

Common timezones:

* `America/New_York` - Eastern Time
* `America/Chicago` - Central Time
* `America/Los_Angeles` - Pacific Time
* `Europe/London` - GMT/BST
* `Asia/Kolkata` - India Standard Time
* `UTC` - Coordinated Universal Time

## Initial Context Template

The `initial_context_template` object allows you to pass variables to your webhook or workflow that can be accessed using `{{ initial.key }}` syntax:

* **In request body**: `{{ initial.key }}` will be replaced with the value
* **In headers**: `{{ initial.key }}` can be used in header values
* **In query params**: `{{ initial.key }}` can be used in query parameters
* **In path**: `{{ initial.key }}` can be used in URL paths

You can also combine with:

* **System secrets**: `{{ #secret_key }}` for vault secrets
* **Workflow step responses**: `{{ step.response.variable }}` in workflows

## Use Cases

* **Daily Reports**: Generate reports every day at 9 AM
* **Weekly Maintenance**: Run maintenance tasks every Sunday at 2 AM
* **Monthly Billing**: Process billing on the 1st of every month
* **Business Hours**: Execute during business hours only (with rules)
* **Complex Patterns**: Create sophisticated scheduling patterns

## Examples

### Daily at 9 AM (Business Days) - Recurring

```json theme={null}
{
  "cron_expression": "0 9 * * 1-5",
  "cron_timezone": "America/New_York",
  "is_one_off_task": false,
  "schedule_to": "webhook",
  "model_to_schedule_uuid": "{{model_to_schedule_uuid}}"
}
```

### Every Hour - Recurring

```json theme={null}
{
  "cron_expression": "0 * * * *",
  "cron_timezone": "UTC",
  "is_one_off_task": false,
  "schedule_to": "webhook",
  "model_to_schedule_uuid": "{{model_to_schedule_uuid}}"
}
```

### Monthly on 1st and 15th - Recurring

```json theme={null}
{
  "cron_expression": "0 0 1,15 * *",
  "cron_timezone": "Asia/Kolkata",
  "is_one_off_task": false,
  "schedule_to": "workflow",
  "model_to_schedule_uuid": "{{model_to_schedule_uuid}}",
  "initial_context_template": {
    "billing_cycle": "bi-monthly"
  }
}
```

### One-Time Execution at Specific Time

```json theme={null}
{
  "cron_expression": "0 9 1 1 *",
  "cron_timezone": "America/New_York",
  "is_one_off_task": true,
  "schedule_to": "webhook",
  "model_to_schedule_uuid": "{{model_to_schedule_uuid}}"
}
```

## Related Documentation

* [Scheduling Overview](/docs/api-reference/scheduling/overview) - Learn about all scheduling types and rules
* [Get Timezone Options](/docs/api-reference/scheduling/timezone-options) - Get list of available timezones
* [Add Interval Schedule](/docs/api-reference/scheduling/add-interval-schedule) - Create interval-based schedules


## OpenAPI

````yaml POST /v1/api/add_cron_schedule/
openapi: 3.0.3
info:
  title: Hookpulse API
  description: >-
    Complete API documentation for Hookpulse. Build powerful integrations with
    our RESTful API.
  version: 1.0.0
  contact:
    name: Hookpulse Support
    email: care@hookpulse.io
    url: https://hookpulse.io
servers:
  - url: https://api.hookpulse.io
    description: Production server
security:
  - apiKeyAuth: []
    brandUuidAuth: []
paths:
  /v1/api/add_cron_schedule/:
    post:
      description: >-
        Create a new cron-based schedule that executes a webhook or workflow
        using standard cron expressions
      requestBody:
        description: Cron schedule configuration
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AddCronScheduleRequest'
      responses:
        '200':
          description: Schedule created successfully
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ScheduleResponse'
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
components:
  schemas:
    AddCronScheduleRequest:
      required:
        - cron_expression
        - cron_timezone
        - schedule_to
        - model_to_schedule_uuid
      type: object
      properties:
        cron_expression:
          type: string
          description: Standard cron expression (e.g., '0 0 * * *' for daily at midnight)
        cron_timezone:
          type: string
          description: IANA timezone identifier
        schedule_to:
          type: string
          enum:
            - webhook
            - workflow
          description: 'Target type: ''webhook'' or ''workflow'''
        model_to_schedule_uuid:
          type: string
          description: UUID of the webhook or workflow template to schedule
        initial_context_template:
          type: object
          description: >-
            Key-value pairs passed as {{ initial.key }} variables to the
            webhook/workflow
          additionalProperties: true
    ScheduleResponse:
      type: object
      properties:
        success:
          type: boolean
          description: Indicates if the schedule was created successfully
        details:
          type: string
          description: Success message
    Error:
      required:
        - error
        - message
      type: object
      properties:
        error:
          type: integer
          format: int32
        message:
          type: string
  securitySchemes:
    apiKeyAuth:
      type: apiKey
      in: header
      name: x-hookpulse-api-key
      description: >-
        API key for authentication. Get this from your dashboard by selecting a
        brand and going to API Keys section.
    brandUuidAuth:
      type: apiKey
      in: header
      name: x-brand-uuid
      description: >-
        Brand UUID for authentication. Get this from your dashboard after adding
        a brand - it will be displayed in the UI.

````