steedos-object-triggers

Server-side data validation in Steedos is automated using .trigger.yml files. You define trigger handlers with inline code to run on lifecycle hooks like beforeInsert, enforcing validation rules automatically whenever a record changes.

Yes, you can trigger external API calls on Steedos object updates by defining an afterUpdate trigger. Using .trigger.yml files, your inline handler code executes automatically to send data to external systems whenever the specified lifecycle event occurs.

Steedos object triggers support all data-change lifecycle hooks, including beforeInsert and afterUpdate. These hooks allow you to intercept record changes at specific stages to perform data validation, auto-fill, cascade updates, or external integrations.

You need a valid SKILL.md frontmatter and triggers code stored in a triggers/ directory using type: code. You can also use optional directories like scripts/, references/, and assets/ to support your trigger implementation.

The best way to auto-fill fields during a Steedos record insertion is by using a beforeInsert trigger. You define a .trigger.yml file with inline handler code that accesses context via ctx.params and modifies the object data before it is saved.

Server-side triggers enforce data automation and validation consistently across all access methods. Unlike client-side scripts, .trigger.yml files run directly on the server, ensuring that validation, cascade updates, and external API calls execute reliably regardless of the client.