Odoo Workflow Automation: Complete Guide to Automated Actions in 2026

What Are Automated Actions in Odoo?

Automated Actions are trigger-based rules that execute when specific conditions are met. Think IF this happens, THEN do that for your database.

Key Components

• Trigger: When the action runs (creation, update, deletion, or time-based)
• Model: Which table to monitor (sales orders, invoices, tasks)
• Conditions: Filters that must be true for execution
• Action Type: What happens (email, update record, Python code)

Where to Find Automated Actions

Navigate to Settings → Technical → Automation → Automated Actions. Enable Developer Mode first.

6 Types of Actions You Can Automate

1. Send Email Notifications

Notify customers, vendors, or team members when events occur.

2. Update Record Fields

Change field values automatically: statuses, assignments, dates.

3. Create Activities

Schedule follow-ups, calls, or meetings based on triggers.

4. Run Python Code

Execute custom logic for complex workflows.

5. Create or Update Records

Generate invoices, tasks, leads or modify existing records.

6. Send Webhook Notifications

Trigger external systems via HTTP requests.

Step-by-Step: Auto-Assign High-Value Orders

Goal: When sales order exceeds $5,000, assign to sales manager and send notification.

Step 1: Enable Developer Mode

Settings → scroll to bottom → Activate Developer Mode.

Step 2: Navigate to Automated Actions

Settings → Technical → Automation → Automated Actions → Create.

Step 3: Configure Basic Settings

• Name: Auto-Assign High-Value Orders
• Model: Sales Order (sale.order)
• Trigger: On Creation

Step 4: Set Domain Filter

Domain Filter: Amount Total > 5000

Step 5: Configure Action

• Action To Do: Update the Record
• Field: Salesperson
• Value: Select sales manager

10 Proven Automation Use Cases

1. Auto-Archive Old Leads

Trigger: Lead 30+ days old with status "New"
Action: Change to "Archived"

2. Invoice Payment Reminders

Trigger: Invoice overdue, unpaid
Action: Send email + create activity

3. Low Stock Alerts

Trigger: Quantity below minimum
Action: Create purchase requisition + notify manager

4. Project Task Escalation

Trigger: Deadline passed, not done
Action: Assign to manager + send email

5. Customer Onboarding

Trigger: New customer created
Action: Welcome email + 3 follow-up activities

6. Sales Order Approval

Trigger: Order exceeds credit limit
Action: Set pending + notify finance

7. Automatic VIP Discount

Trigger: VIP customer, order over $1000
Action: Apply 10% discount

8. Support Ticket Routing

Trigger: Technical category ticket
Action: Assign to tech team

9. Manufacturing Order Creation

Trigger: MTO sales order confirmed
Action: Create manufacturing order

10. Expense Auto-Approval

Trigger: Under $100, policy compliant
Action: Auto-approve + create journal entry

Advanced: Python Server Actions

For complex logic, use Python server actions.

Example: Custom Commission Calculation

order = record
commission = 0
for line in order.order_line:
 if line.product_id.categ_id.name == "Premium":
 commission += line.price_subtotal * 0.15
 elif line.product_id.categ_id.name == "Standard":
 commission += line.price_subtotal * 0.10

env['sales.commission'].create({
 'order_id': order.id,
 'salesperson_id': order.user_id.id,
 'amount': commission,
 'status': 'pending'
})
order.message_post(body=f"Commission: ${commission:.2f}")

Testing and Debugging

Test Before Deploying

1. Create in test database first
2. Use narrow domain filters during testing
3. Check Email Queue for sent emails
4. Review Logs for Python errors

Common Issues

Action Not Triggering

• Verify Developer Mode enabled
• Check model technical name
• Review domain filter
• Confirm action is Active

Email Not Sending

• Verify mail server config
• Check email template fields
• Review Email Queue errors

Python Errors

• Check Logs for traceback
• Verify field technical names
• Test in Python shell first

Performance Best Practices

• Avoid recursive triggers: actions that trigger themselves
• Use specific domain filters: reduce unnecessary executions
• Limit Python complexity: keep under 50 lines
• Monitor execution logs: review weekly
• Archive old actions: disable unused automations

FAQ

Do I need Python for Automated Actions?

No. Most automations require no coding. Python is only for advanced custom logic.

Can actions slow down Odoo?

Well-configured actions have minimal impact. Avoid recursive triggers and monitor logs.

How do I test before deploying?

Use test database, narrow filters, check Email Queue and Logs.

Can multiple actions trigger on one event?

Yes. They execute in sequence order.

Automated Actions vs Server Actions?

Automated Actions are trigger rules. Server Actions are the operations performed.

References

1. Odoo SA: "Automated Actions Documentation" (2026). Odoo Documentation
2. Odoo SA: "Server Actions Guide" (2026). Odoo Documentation
3. Odoo Community Association: "Automation Best Practices" (2025). OCA GitHub
4. Odoo Mates: "Complete Guide to Odoo Automation" (2025). Odoo Mates Blog
5. Cybrosys: "Python Server Actions in Odoo" (2026). Cybrosys Blog