Hooksbase

Channels / April 8, 2026

Schedule recurring agent runs with cron

Scheduled webhook configuration

Some agents are event-driven (they wake up when Stripe sends a webhook). Others need to run on a cadence — daily summaries, periodic health checks, recurring reports. Scheduled webhooks handle the second pattern.

What you get

  • Per-webhook cron schedules, minimum 1-minute granularity
  • Configurable JSON payload template per schedule
  • Same ingest pipeline as HTTP — routing, transforms, retries, delivery history, replay all work identically
  • Pause, resume, and delete via REST or the dashboard

Scheduled webhooks are available on Starter+ ($25/mo).

Configure a schedule

  1. Open the webhook in the dashboard.
  2. Go to the Schedules tab.
  3. Click Add schedule.
  4. Give it a name (e.g. daily-standup-summary).
  5. Set a cron expression. 0 9 * * 1-5 fires weekdays at 9am UTC.
  6. (Optional) Paste a static JSON payload template. If omitted, Hooksbase sends a default envelope with source, scheduleId, webhookId, cronExpression, and firedAt.
  7. Save.

Example cron expressions

  • */15 * * * * — every 15 minutes
  • 0 * * * * — every hour on the hour
  • 0 9 * * * — daily at 9am UTC
  • 0 9 * * 1-5 — weekdays at 9am UTC
  • 0 0 1 * * — first of each month at midnight UTC
  • 0 0 * * 0 — weekly, Sunday at midnight UTC

All times are UTC. If you need user-local cadence, pick a UTC time that maps to a reasonable local time for most of your users.

Payload template

You can send a static JSON payload, which the agent receives as the event body:

{
  "task": "daily-standup-summary",
  "lookback_hours": 24,
  "audience": "engineering"
}

Your agent gets this as structured JSON just like any other delivery.

Scheduled events don't catch up

Common agent recipes

  • Daily standup summary: cron fires daily → agent queries recent commits/PRs/tickets → drafts a Slack post
  • Hourly health check: cron fires hourly → agent pings critical endpoints, checks SLOs → emits alert if anything drifts
  • Weekly recap: cron fires weekly → agent aggregates the week's activity → emails stakeholders
  • Monthly cleanup: cron fires on the 1st → agent archives old data, resets counters, runs maintenance

What next

Related guides

Back to guides