Automating Odoo Without a Developer: What Automated Actions Really Do (and Their Technical Trap)

5 trigger categories, 9 actions executable without code, and the trap of time-based rules that never apply retroactively: what Odoo's official documentation says about automated actions.

Many SMBs pay for custom development of automations that already exist natively in Odoo through "automated actions" (automation rules) — with no code required. Here is precisely what the official documentation (odoo.com/documentation) says about the available triggers, the executable actions, and a technical trap that regularly surprises teams activating them for the first time.

The 5 available trigger categories

✓Values updated: triggers on a specific field change or a tag being added
✓Email events: triggers when an email is sent or received on a record
✓Timing conditions: runs at a defined interval relative to a date (e.g. before or after a deadline, or after a record's creation)
✓Custom triggers: on creation, on creation and edit, on deletion, or on a UI field change before saving
✓External triggers: a notification or webhook sent by a third-party system

The actions executable with zero code

✓Update a record (with optional AI assistance)
✓Create or duplicate a record
✓Create a follow-up activity
✓Send an email or SMS
✓Send a WhatsApp message
✓Add or remove followers on the record
✓Execute Python code (for cases beyond standard configuration)
✓Send a webhook notification to an external system
✓Chain several actions together (multi-actions)

The technical trap: time-based triggers never catch up on history

A point Odoo documents explicitly: for a time-based trigger, the action only runs if the scheduled action checking the rule runs AFTER the calculated trigger time — this mechanism prevents any retroactive execution on records that already existed when the rule was activated.

In practice: if you activate a rule "send a reminder 30 days before a contract deadline" on a database that already contains contracts due in 10 days, those contracts will NOT get a retroactive reminder — the 30-day window has already passed for them at activation time. This is the point that most often trips up teams who wrongly assume automation will "catch up" on existing history as soon as it's turned on.

Precisely filtering with before- and after-trigger domains

Odoo lets you apply domain conditions both before and after the triggering event, to target exactly which records are affected — useful to avoid a generic status change triggering the action on out-of-scope records (for example, only notifying leads from one specific sales pipeline rather than every lead in the database).

3 example rules to build with these building blocks (adapt to your own process)

✓Automatic email follow-up a few days before an unanswered quote's deadline (timing trigger + email action)
✓Webhook notification to your internal tracking tool when a lead moves to "Won" status (values-updated trigger + webhook action)
✓Automatic creation of an HR follow-up activity on a key date in an employee's contract (timing trigger + activity creation)

These are examples to build from, not templates provided by Odoo — assemble them from the documented triggers and actions to fit your actual process.

Figuring out which of your current processes can be automated with these native building blocks (no development needed) rather than a custom module takes a quick audit of your Odoo configuration. Contact us for a free audit — response within 24h.