Memory-triggered automations

When memory changes, your systems react — webhooks on decisions, gates, and milestones.

error_outline

Without memory

Your memory system knows things the rest of your stack should react to — a decision was recorded, an agent hit a gate, a goal was reached — but that knowledge sits inert unless a human happens to look.

check_circle

With Rekall

Webhooks fire on memory events: decision recorded → post to the architecture channel; gate pending → page the approver; agent run failed → open a ticket. Memory becomes an event source for the systems you already run.

How it works

Subscribe to event types

Decision, gate, agent, and memory events each carry typed payloads — subscribe per event type per endpoint.

Delivery is production-grade

Signed payloads, retries with backoff, and SSRF-guarded endpoints — the worker handles redelivery so you don’t.

Downstream reacts

Slack posts, tickets, pages, sync jobs — anything with an HTTP endpoint becomes memory-aware.

See it in action

Memory as an event source

await rekall.webhooks.create({
  url: 'https://hooks.internal/rekall',
  events: ['decision.recorded', 'gate.pending',
           'agent.run.failed'],
})
// decision.recorded → #architecture channel
// gate.pending     → page the on-call approver
// agent.run.failed → auto-open an incident ticket