Combining Automation Patterns

Introduction

The real power of OpenClaw automation emerges when you combine heartbeats, cron jobs, webhooks, and polling into a cohesive strategy. Each pattern has strengths and weaknesses. Heartbeats batch multiple checks efficiently. Cron jobs provide precise scheduling. Webhooks offer instant event delivery. Polls fill gaps where webhooks are unavailable. This lesson shows how to design a complete automation strategy using all four patterns together.

Key Concepts

• Pattern Complementarity: Each automation pattern covers scenarios the others cannot
• Cost Efficiency: Using the right pattern for each task minimizes total API token spending
• Latency Tradeoffs: Webhooks are instant, heartbeats batch, cron is scheduled, polls have delay
• Redundancy: Combining patterns creates backup detection paths for critical events
• Automation Strategy: A deliberate plan for which pattern handles which tasks

Real World Context

A platform engineering team manages a production environment with OpenClaw. They use heartbeats for routine health checks (batching 5 checks into one turn every 30 minutes), cron jobs for daily reports and weekly audits, webhooks for real-time GitHub PR events, and polling for a legacy monitoring system that does not support webhooks. Together, these four patterns provide comprehensive coverage with minimal cost.

Deep Dive

The Four Patterns Compared

Each pattern serves a different purpose:

json
{
  "patterns": {
    "heartbeat": {
      "trigger": "Fixed interval (default 30 min)",
      "bestFor": "Batching multiple routine checks into one turn",
      "latency": "Up to one interval period",
      "costModel": "One API call per interval, regardless of check count"
    },
    "cron": {
      "trigger": "Precise schedule or interval",
      "bestFor": "Scheduled tasks that need exact timing",
      "latency": "Depends on schedule",
      "costModel": "One API call per job execution"
    },
    "webhook": {
      "trigger": "External event push",
      "bestFor": "Real-time reactions to external events",
      "latency": "Near-instant",
      "costModel": "One API call per event"
    },
    "poll": {
      "trigger": "Periodic pull check",
      "bestFor": "Monitoring services without webhook support",
      "latency": "Up to one interval period",
      "costModel": "One HTTP call per interval + API call on change"
    }
  }
}

This comparison highlights the key tradeoffs. Heartbeats are the most cost-efficient for routine monitoring because they batch multiple checks. Webhooks are the fastest but require the external service to support them. Cron provides precise timing. Polls fill the gap when webhooks are unavailable.

Designing a Complete Strategy

A well-designed automation strategy assigns each task to the most appropriate pattern:

json
{
  "automationStrategy": {
    "heartbeat": [
      "Check API health across all services",
      "Verify database connection pool utilization",
      "Monitor SSL certificate expiry",
      "Check disk and memory usage"
    ],
    "cron": [
      { "task": "Generate daily deployment summary", "schedule": "0 18 * * 1-5" },
      { "task": "Run weekly security audit", "schedule": "0 6 * * 1" },
      { "task": "Renew Gmail API watch", "schedule": "0 0 */5 * *" }
    ],
    "webhooks": [
      { "source": "GitHub", "events": ["pull_request.opened", "pull_request.merged"] },
      { "source": "Gmail", "events": ["new_email"] }
    ],
    "polls": [
      { "source": "Legacy issue tracker", "interval": 300, "check": "New high-priority issues" }
    ]
  }
}

Routine health checks are batched into the heartbeat because they all run at the same interval and benefit from shared context. Scheduled reports and audits use cron for precise timing. GitHub and Gmail events use webhooks for instant reaction. The legacy issue tracker uses polling because it does not support webhooks.

Cost Optimization

The combined strategy optimizes cost by choosing the cheapest pattern for each task:

json
{
  "costAnalysis": {
    "heartbeat": {
      "checks": 4,
      "interval": "30 min",
      "dailyCalls": 48,
      "note": "4 checks batched into 1 turn = 48 turns/day"
    },
    "cron": {
      "dailyJobs": 1,
      "weeklyJobs": 1,
      "note": "Only runs when scheduled"
    },
    "webhooks": {
      "avgDailyEvents": 15,
      "note": "Only fires when events occur"
    },
    "polls": {
      "interval": "5 min",
      "dailyPolls": 288,
      "dailyTriggers": 3,
      "note": "288 HTTP checks, only 3 trigger agent turns"
    }
  }
}

Without batching, 4 individual health checks every 30 minutes would cost 192 agent turns per day. The heartbeat batches them into 48 turns, a 4x savings. Polls are cheap because most checks do not trigger agent turns.

Common Pitfalls

• Using the wrong pattern for a task: Running real-time event handling through heartbeats adds up to 30 minutes of latency. Use webhooks for real-time needs.
• Duplicating checks across patterns: If your heartbeat checks API health and a poll also checks the same endpoint, you are paying twice for the same information.
• Not accounting for combined API usage: Each pattern contributes to your total API usage. Plan the combined load to stay within rate limits.

Best Practices

• Audit your automation patterns quarterly to ensure each task is assigned to the optimal pattern.
• Use heartbeats for batched routine checks and webhooks for real-time events to maximize cost efficiency.
• Document your automation strategy so team members understand which pattern handles which tasks and why.

Summary

• Heartbeats batch multiple routine checks into a single agent turn for cost efficiency
• Cron jobs provide precise scheduling for reports, audits, and maintenance tasks
• Webhooks deliver instant event notification from external services that support them
• Polls fill the gap for services that do not support webhooks
• A well-designed strategy assigns each task to the most appropriate pattern based on latency, cost, and availability