Time-Based And Event-Based Heartbeats: Choosing The Trigger

OpenClaw souls can wake on a clock, on a webhook, on a message, or on an internal signal. The trigger you pick shapes what kind of agent you actually have.

10 min · Reviewed 2026

The four trigger families

Every OpenClaw heartbeat reduces to a question: what makes the soul wake up? There are four answers worth knowing — interval, cron, event, and self-paced — and most production souls compose two or three of them.

Interval heartbeats

The simplest trigger: 'wake every N seconds.' Good for monitoring loops, ambient awareness, gentle background reflection. The runtime keeps a timer; when it fires, the soul runs one beat and the timer resets.

soul:
  name: inbox-watcher
  heartbeat:
    type: interval
    every: 5m
    max_iterations: 200An interval heartbeat. Every 5 minutes, the soul wakes up and checks its inbox. After 200 beats it stops on its own — a safety cap we cover in lesson three.

Cron heartbeats

When 'every 5 minutes' isn't precise enough, a cron expression nails the soul to a calendar. Useful for daily digests, weekly summaries, end-of-month reports — anything that should run at a specific time, not a relative one.

soul:
  name: morning-briefing
  heartbeat:
    type: cron
    schedule: "0 8 * * 1-5"   # 8:00 AM, weekdays only
    timezone: America/New_YorkA cron heartbeat fires the soul at 8 AM Eastern, weekdays only. The runtime handles DST; you handle the timezone.

Event heartbeats

Sometimes the world should wake the soul, not the clock. Event heartbeats fire on incoming webhooks, queue messages, file changes, or other runtime signals. The soul reacts — but inside the agent loop, with full memory, not as a stateless handler.

soul:
  name: pr-reviewer
  heartbeat:
    type: event
    on:
      - webhook: github.pull_request.opened
      - webhook: github.pull_request.synchronize
    debounce: 30sWake on GitHub PR events. Debounce coalesces a flurry of pushes into a single beat — without it, a 10-commit push fires 10 reviews.

Self-paced heartbeats

The most agentic option: the soul itself sets the next beat. After running, it can return 'wake me in 90 seconds' or 'wake me when X arrives.' Useful when the rhythm depends on what the soul just learned — a slow heartbeat while idle, a fast one while a task is in flight.

Choosing the right trigger

You want	Use	Why
Background reflection on memory	Interval (slow, e.g. 1h)	Doesn't need to be precise
8 AM digest, weekdays only	Cron	Calendar-anchored, DST-safe
React to a webhook in seconds	Event	Latency matters; events carry context
A goal that needs faster polling while active	Self-paced + interval cap	Adaptive rhythm
Watch an inbox and write a daily summary	Event (on new mail) + Cron (8 AM digest)	Composed triggers
Free-running brainstorm with no real-time need	Cron once a day	Cheapest pattern that still feels alive

Composing triggers

Most useful souls have two triggers, not one — one for routine work, one for reactive work
Compose them in priority order: an event beat preempts a scheduled beat (the soul wakes immediately)
Add a debounce to event triggers to avoid thrashing on bursty signals
Add a floor to all triggers — no soul should beat more than once per second by default
Log every beat with its trigger source — 'why did the soul wake up?' is the first debugging question

The big idea: pick the trigger that matches the soul's job. Interval for ambient. Cron for calendar. Event for reactive. Self-paced for adaptive. Most production souls compose two.

End-of-lesson check

15 questions · take it digitally for instant feedback at tendril.neural-forge.io/learn/quiz/end-openclaw-heartbeats-time-vs-event-creators

What is the core idea behind "Time-Based And Event-Based Heartbeats: Choosing The Trigger"?
1. OpenClaw souls can wake on a clock, on a webhook, on a message, or on an internal signal. The trigger you pick shapes what kind of agent you actually have.
2. The runtime fires the heartbeat (timer or event)
3. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
4. infinite loop
Which term best describes a foundational idea in "Time-Based And Event-Based Heartbeats: Choosing The Trigger"?
1. cron schedule
2. interval
3. event trigger
4. self-paced
A learner studying Time-Based And Event-Based Heartbeats: Choosing The Trigger would need to understand which concept?
1. interval
2. event trigger
3. cron schedule
4. self-paced
Which of these is directly relevant to Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. interval
2. cron schedule
3. self-paced
4. event trigger
Which of the following is a key point about Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. Most useful souls have two triggers, not one — one for routine work, one for reactive work
2. Compose them in priority order: an event beat preempts a scheduled beat (the soul wakes immediately)
3. Add a debounce to event triggers to avoid thrashing on bursty signals
4. Add a floor to all triggers — no soul should beat more than once per second by default
Which of these does NOT belong in a discussion of Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. The runtime fires the heartbeat (timer or event)
2. Compose them in priority order: an event beat preempts a scheduled beat (the soul wakes immediately)
3. Most useful souls have two triggers, not one — one for routine work, one for reactive work
4. Add a debounce to event triggers to avoid thrashing on bursty signals
What is the key insight about "Self-paced is powerful and dangerous" in the context of Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. The runtime fires the heartbeat (timer or event)
2. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
3. A soul that picks its own next beat can also pick zero. Always combine self-paced with a max-interval cap and a runtime-…
4. infinite loop
What is the key insight about "Don't pick the trigger by feel" in the context of Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. The runtime fires the heartbeat (timer or event)
2. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
3. infinite loop
4. 'It should run sometimes' is not a trigger spec. Decide if you need calendar accuracy (cron), reactive latency (event), …
What is the recommended tip about "Evaluate systematically" in the context of Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. Before adopting any AI tool: check the data policy, benchmark on your actual use cases, and plan an exit strategy.
2. The runtime fires the heartbeat (timer or event)
3. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
4. infinite loop
Which statement accurately describes an aspect of Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. The runtime fires the heartbeat (timer or event)
2. Every OpenClaw heartbeat reduces to a question: what makes the soul wake up? There are four answers worth knowing — interval, cron, event, a…
3. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
4. infinite loop
What does working with Time-Based And Event-Based Heartbeats: Choosing The Trigger typically involve?
1. The runtime fires the heartbeat (timer or event)
2. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
3. The simplest trigger: 'wake every N seconds.' Good for monitoring loops, ambient awareness, gentle background reflection.
4. infinite loop
Which of the following is true about Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. The runtime fires the heartbeat (timer or event)
2. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
3. infinite loop
4. When 'every 5 minutes' isn't precise enough, a cron expression nails the soul to a calendar.
Which best describes the scope of "Time-Based And Event-Based Heartbeats: Choosing The Trigger"?
1. It focuses on OpenClaw souls can wake on a clock, on a webhook, on a message, or on an internal signal. The trigge
2. It is unrelated to tools workflows
3. It applies only to the opposite beginner tier
4. It was deprecated in 2024 and no longer relevant
Which section heading best belongs in a lesson about Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. The runtime fires the heartbeat (timer or event)
2. Interval heartbeats
3. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
4. infinite loop
Which section heading best belongs in a lesson about Time-Based And Event-Based Heartbeats: Choosing The Trigger?
1. The runtime fires the heartbeat (timer or event)
2. A heartbeat is what makes an OpenClaw soul autonomous — a run-loop the runtime f…
3. Cron heartbeats
4. infinite loop

← Back to interactive lesson

Tendril · Creators · Tools Literacy