Event Triggers

Availability note for event-driven workflows in Spala.

Event Triggers

Advanced availability

The current builder focuses on database triggers. If Event Triggers are not visible in your workspace, use database triggers, scheduled tasks, project agents, or explicit function calls for event-driven workflows.

Event-driven workflows are still useful in Spala, but the visible product surface you should rely on today is:

Database Triggers
Run a function when records are inserted, updated, or deleted.
/triggers/database-triggers

Scheduled Tasks
Run recurring or manual backend jobs.
/tasks/scheduled-tasks

Project Agents
Run agent workflows from manual, webhook, schedule, database change, or websocket triggers.
/features/project-agents

Run Function
Call reusable backend logic from endpoints, tasks, triggers, or other functions.
/flows

Practical Alternatives

- Use a database trigger when the workflow starts from a record change.
- Use a scheduled task when the workflow starts from time or manual admin action.
- Use a project agent when the workflow needs AI reasoning, chat, or multi-step agent execution.
- Use Run Function when one backend action should call another reusable function directly.

Database Triggers
/triggers/database-triggers
Fire functions on insert, update, and delete operations
Triggers Overview
/triggers
Understand visible trigger workflows
Project Agents
/features/project-agents
Use agent workflows for richer event handling