Skip to main content
POST
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:

Example request

Request body

Example response

Response fields

Cron Expression Format

Cron expressions use the standard 5-field format:

Common Cron Examples

Timezone Support

HookPulse supports all 500+ IANA timezones. Use the Get 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

Every Hour - Recurring

Monthly on 1st and 15th - Recurring

One-Time Execution at Specific Time

Authorizations

x-hookpulse-api-key
string
header
required

API key for authentication. Get this from your dashboard by selecting a brand and going to API Keys section.

x-brand-uuid
string
header
required

Brand UUID for authentication. Get this from your dashboard after adding a brand - it will be displayed in the UI.

Body

application/json

Cron schedule configuration

cron_expression
string
required

Standard cron expression (e.g., '0 0 * * *' for daily at midnight)

cron_timezone
string
required

IANA timezone identifier

schedule_to
enum<string>
required

Target type: 'webhook' or 'workflow'

Available options:
webhook,
workflow
model_to_schedule_uuid
string
required

UUID of the webhook or workflow template to schedule

initial_context_template
object

Key-value pairs passed as {{ initial.key }} variables to the webhook/workflow

Response

Schedule created successfully

success
boolean

Indicates if the schedule was created successfully

details
string

Success message