How to Use Odoo's Automated Actions and Scheduled Actions to Eliminate Manual Work
One of the most underutilized capabilities in Odoo is the automation engine built right into the platform. Most businesses that implement Odoo spend the early months learning the core workflows: entering orders, managing inventory, processing invoices. That is exactly as it should be. But once the fundamentals are solid, there is a significant amount of additional value available to any business willing to explore what Odoo can do automatically without anyone lifting a finger.
At Custom Pixel Design, automating repetitive workflows is one of the areas where we consistently deliver value to clients long after their initial implementation. This article is a practical guide to Odoo's two primary automation tools: Automated Actions and Scheduled Actions. You do not need to be a developer to use most of these capabilities effectively, and even the more technical options are accessible to anyone with a basic comfort level in Odoo's interface.
Why Automation Matters More Than Most Businesses Realize
Before getting into the mechanics, it is worth being clear about why this matters. Every repetitive manual task in your business represents a combination of three costs: the time it takes to perform, the opportunity cost of that person's attention being elsewhere, and the probability of human error.
A salesperson who manually updates CRM stage on every deal they advance, a warehouse manager who sends a manual email every time inventory drops below a threshold, an accountant who manually tags every transaction in the same category the same way every month: these are not unusual tasks and none of them individually is a crisis. But they add up. In a business running dozens or hundreds of these small manual processes daily, the cumulative cost is significant.
Odoo's automation tools allow you to define rules that execute these processes automatically when the right conditions are met. The trigger, the condition, and the action are all configurable, and the range of things you can automate is broader than most users expect.
Automated Actions: Event-Driven Automation
Automated Actions are rules that fire when something happens in Odoo. When a record is created, when a field is updated, when a specific condition is met. They work across every model in Odoo, meaning you can create automation rules for sales orders, customer records, inventory items, projects, invoices, or virtually anything else in the system.
To access Automated Actions, enable developer mode in Odoo settings and navigate to Settings, then Technical, then Automated Actions. You will find all existing automation rules here and can create new ones.
An Automated Action has three components: a trigger, a condition, and an action.
The trigger defines what event causes the rule to fire. The available triggers include when a record is created, when a record is updated, when a specific field changes value, when a record is deleted, or based on a date or time condition. The date-based trigger is particularly powerful because it allows actions to fire a specified number of minutes, hours, days, or months before or after a date field on the record. Want to send a follow-up email seven days after an opportunity is created without a response? That is a date-based trigger.
The condition narrows down which records the rule applies to. You can apply conditions using Odoo's domain filter syntax, which allows you to specify things like "only apply this rule when the opportunity is in the Proposal stage" or "only fire when the customer type is wholesale." This means your automation rules can be surgical rather than broad, applying exactly where you intend and nowhere else.
The action is what happens when the trigger fires and the condition is met. The available action types without any code include updating a field value, sending an email, creating a new record, scheduling an activity, and triggering multiple actions simultaneously. With a small amount of Python code, you can extend this further to include virtually any operation the system can perform.
Practical Examples of Automated Actions
The best way to understand what Automated Actions can do is to look at concrete examples of how businesses use them.
Automatic CRM stage progression triggers. When a quotation is confirmed, automatically move the associated CRM opportunity to the Won stage. When a proposal sits in a stage for more than fourteen days without activity, automatically create a follow-up activity assigned to the salesperson. These rules keep the pipeline accurate without requiring salespeople to manually update records as deals progress.
Customer credit limit notifications. When a customer's outstanding balance exceeds a defined threshold, automatically send a notification to the accounts receivable team and flag the customer record. This surfaces credit risk in real time rather than during a weekly review.
Automatic product category assignment. When a new product is created with a specific attribute or tag, automatically assign it to the correct internal category and apply the corresponding revenue account. This enforces consistency without training every team member on category rules.
Lead source tracking. When a lead is created from a specific source, automatically assign it to the appropriate sales team and set the initial stage to the right starting point for that source type.
Invoice follow-up scheduling. When a customer invoice reaches thirty days past due, automatically create a follow-up activity for the account manager and send a polite reminder email to the customer. At sixty days past due, escalate with a more direct communication and a task for finance review.
Project task creation from sales orders. When a sales order is confirmed for a specific product or service type, automatically create a project task with the relevant details pre-populated and assign it to the appropriate project manager. This eliminates the handoff gap between sales and delivery.
Scheduled Actions: Time-Based Automation
Where Automated Actions fire in response to events, Scheduled Actions run on a time schedule. These are background tasks that Odoo executes at defined intervals regardless of what is happening in the foreground.
Scheduled Actions are accessible from Settings, then Technical, then Scheduled Actions when developer mode is enabled. Many Scheduled Actions already exist in your Odoo instance by default, handling things like sending queued emails, checking for overdue invoices, and syncing bank feeds. You can also create your own.
A custom Scheduled Action defines a model, a method or code to execute, and a frequency. Common use cases for custom Scheduled Actions include:
Daily inventory level checks. Every morning, check all products against their minimum stock rules and generate purchase requests for anything that has fallen below the reorder threshold. This ensures purchasing is always driven by actual stock levels rather than whoever happens to notice an empty shelf.
Weekly KPI reports. Every Monday morning, generate a summary report of the previous week's key metrics, whether that is sales by region, open service tickets, or outstanding receivables over sixty days, and send it to the appropriate people automatically.
Recurring invoice generation. For subscription customers or ongoing service contracts, generate invoices automatically at the specified billing interval. Odoo's subscription module handles this natively for most use cases, but custom Scheduled Actions allow more flexibility for businesses with non-standard billing structures.
Data cleanup and maintenance. Archive records that have been inactive for more than a defined period. Merge duplicate customer records that meet specific criteria. Update calculated fields that need to be refreshed periodically. These housekeeping tasks are easy to forget when done manually and easy to automate when done systematically.
Using Odoo Studio for No-Code Automation
For businesses that want to build automation without engaging a developer for every change, Odoo Studio provides a no-code interface for creating and managing Automated Actions. Studio is available in the Enterprise edition and allows you to define triggers, conditions, and actions through a visual interface rather than directly in the technical settings.
Studio is particularly useful for business users who understand the process they want to automate but are not comfortable working in the technical automation interface. The visual interface provides guardrails that prevent some of the more advanced but risky configurations, which is a reasonable trade-off for most use cases.
What Requires a Developer
Most of the automation described in this article is achievable without custom development. But there are some automation use cases that go beyond what the standard tools can accomplish without code.
Complex multi-step workflows that involve logic branching based on conditions, integrations with external systems triggered by events in Odoo, computed field values that require business logic beyond simple field assignments, and automation that spans multiple models in non-standard ways all typically require a developer to implement properly.
This is where working with a partner like Custom Pixel Design adds value beyond implementation. We help clients identify automation opportunities across their workflows, build custom automation rules where standard tools are insufficient, and maintain those rules as the business and the system evolve.
If your Odoo implementation is up and running and you are wondering whether there is more value to be extracted from the automation capabilities you already have, reach out to our team. A workflow audit often surfaces a significant number of opportunities that nobody had time to explore during the initial implementation.