Studio, automation rules, server actions and email templates

No-code and low-code customisation: Studio fields and views, automation rules triggered by events, server actions and templates.

In this lesson

Studio and what it generates
Automation rules and triggers
Server actions, templates and when to use a module

Key points

Studio adds x_studio_ fields and views in studio_customization
Automation rules: create, update, stage, time-based, webhook triggers
Actions: update, activity, email/SMS, followers, code, webhook, AI agent (Odoo 20)
Complex logic with tests belongs in a module under Git

Real-world example

A collections team wanted a reminder call scheduled 3 days after every invoice's due date if unpaid. An automation rule on account.move, time-based trigger 'Due Date + 3 days', filter 'posted, not paid, customer invoice', action 'create activity: Call' for the salesperson did it in ten minutes, with no code.

Questions and answers

Where do Studio changes live technically?

In the generated studio_customization module (with x_studio_ fields).

When should automation become a module?

When logic is complex, needs tests, version control or reuse across databases.

Read the full lesson, worked example and quiz