automation-recipes

To build event-driven automation routines, you use standardized recipes that implement cron-based tasks, reaction-based workflows, and interactive UI interactions while ensuring state persistence and idempotency. These recipes run within the Ravi runtime environment.

State persistence for cron-based workflows is maintained using durable local storage primitives integrated with the runtime's event bus. This ensures agent routines survive restarts, maintain idempotency, and preserve context without losing data or triggering unnecessary LLM calls.

Triggering task execution via Slack reactions involves a cron job that identifies pending tasks and posts them for human approval. The final action executes only after a valid reaction is detected and processed through the event-driven state management system.

Yes, this approach requires integration with Ravi's internal event bus, local storage primitives, and shell-based execution environment. These components are necessary to facilitate durable state management and event-driven reactions properly.

Configuring a cron-based sentinel routine involves using the automation recipes to monitor for approval candidates and handle reaction-based state updates. This standardizes the creation of scheduled tasks within the event-driven runtime.

Event-driven agent automations lose context or trigger duplicate LLM calls when they lack durable local storage patterns and idempotency controls. Implementing standardized state management recipes ensures routines survive restarts and prevent unnecessary API requests.