Base44: Automations for Backend Functions
Base44Base44 launched Automations for Backend Functions, enabling developers to schedule backend functions on cron expressions, simple time intervals, or trigger them in response to database entity events such as record creation, updates, or deletions. Automations are configured in function-level JSONC files and deployed atomically alongside function code, eliminating the need for external cron services or job schedulers.
Sources & Mentions
3 external resources covering this update
Overview
Base44 released Automations for Backend Functions, a scheduling and event-trigger system that allows backend functions to execute automatically without manual invocation. Developers can configure multiple automation rules per function, covering three distinct triggering mechanisms: cron-based schedules, simple interval schedules, and database entity event hooks.
Automation Types
Cron-Based Scheduling
For precise timing control, Base44 automations accept standard 5-field cron expressions. This enables patterns like "every weekday at midnight" or "the first of every month at 9am."
Simple Interval Scheduling
For straightforward recurring tasks, Base44 offers a human-friendly alternative to cron syntax. Developers specify a repeat_unit (minutes, hours, days, weeks, or months) and a repeat_interval value.
Entity Event Triggers
Functions can be triggered reactively when database records change. Developers specify the entity name and one or more event types — create, update, or delete — making it possible to build event-driven workflows without polling.
Configuration and Deployment
All automations are defined in the function's function.jsonc file alongside the function code itself. This keeps scheduling logic co-located with application logic and under version control. Deployments are atomic per function: both the code and all attached automations must deploy successfully, or the entire deployment rolls back.
Developer Impact
Eliminating External Schedulers
Before this feature, Base44 developers who needed scheduled workflows had to rely on external services — Zapier, cron-as-a-service platforms, or custom cloud infrastructure — to trigger their functions. Automations bring scheduling natively into the Base44 runtime, removing that dependency entirely.
Event-Driven Architecture Made Simple
Entity event triggers enable patterns that previously required complex webhook infrastructure or polling loops. A function can now react to a new database record being created in milliseconds, without any external message broker or event bus.