Hookbase
Docs
GuideAPI ReferenceIntegrationsUse CasesCLIMCP
Getting StartedSDK ReferencePortal ComponentsAPI Reference
Get Started

Getting Started

IntroductionQuick StartBest PracticesPipeline Architecture

Core Concepts

SourcesDestinationsRoutes

Advanced Features

TransformsAI TransformsFiltersSchemasDeduplicationCustom DomainsTunnelsCron JobsScheduled Sends

Enterprise Security

OverviewCircuit BreakerFailover DestinationsIP FilteringStatic IP DeliveryNotification ChannelsObservability ExportField EncryptionAudit Logs

Kubernetes

Operator GuideCRD ReferenceHelm Chart

Operations

Plans & LimitsProduction ReadinessTroubleshootingTestingComparison
DocsReceiveGuideScheduled Sends

Scheduled Sends

Schedule a one-time HTTP request to be delivered at a specific date and time.

Overview

While Cron Jobs handle recurring deliveries, Scheduled Sends are for one-time, fire-and-forget requests. Use cases include:

  • Sending deployment notifications at a planned release time
  • Triggering batch jobs at a specific time
  • Scheduling follow-up webhooks after a delay
  • Testing how your system handles future-dated events

Quick Start

1. Create a Scheduled Send

Navigate to Tools → Cron Jobs → Scheduled Sends tab, or use the API:

curl -X POST https://api.hookbase.app/api/organizations/{orgId}/scheduled-sends \
  -H "Authorization: Bearer {token}" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Release notification",
    "url": "https://api.example.com/webhooks/release",
    "method": "POST",
    "payload": {"version": "2.0.0"},
    "scheduledFor": "2026-03-15T14:00:00Z"
  }'

2. Monitor Status

Check the status in the dashboard or via API:

curl https://api.hookbase.app/api/organizations/{orgId}/scheduled-sends/{id} \
  -H "Authorization: Bearer {token}"

3. Cancel or Trigger Early

# Cancel
curl -X DELETE https://api.hookbase.app/api/organizations/{orgId}/scheduled-sends/{id}
 
# Send immediately
curl -X POST https://api.hookbase.app/api/organizations/{orgId}/scheduled-sends/{id}/send-now

How It Works

  1. You create a scheduled send with a target URL and future timestamp
  2. Hookbase's scheduler checks for due sends every minute
  3. When scheduledFor time arrives, the request is enqueued for delivery
  4. The request is executed with your specified method, headers, and payload
  5. Response status, body, and latency are recorded
  6. If the request fails, it retries up to maxAttempts times

Status Lifecycle

pending → sending → sent
                  → failed → (retry) → pending
pending → cancelled

Dashboard

The Scheduled Sends tab in the Cron Jobs page shows all your sends with:

  • Status badges: Pending (yellow), Sending (blue), Sent (green), Failed (red), Cancelled (gray)
  • Scheduled time with timezone
  • Target URL and method
  • Actions: Cancel, Send Now, View details

See Also

  • Scheduled Sends API — Full API reference
  • Cron Jobs — Recurring scheduled deliveries
  • Destinations — Destination configuration
PreviousCron JobsNextOverview

On this page

OverviewQuick Start1. Create a Scheduled Send2. Monitor Status3. Cancel or Trigger EarlyHow It WorksStatus LifecycleDashboardSee Also