Different Types of Actions in Odoo

Odoo is a modular ERP platform in which actions connect menus, buttons, views, reports, and backend operations. For example, clicking a menu can open a list of customers, selecting a button can launch a wizard, and a report action can generate a PDF document.

Understanding these mechanisms helps developers determine where a process should run, what information it should use, and how the result should be presented to the user.

What Are Actions in Odoo?

Actions are records or returned action descriptions that instruct Odoo on what should happen next. Depending on the action type, Odoo can open a model view, execute backend logic, navigate to a URL, invoke a client-side component, or generate a report.

Actions are commonly defined through XML records, configured through the user interface where supported, or returned by Python methods. Their behavior depends on the action type and the relevant model, view, context, and execution environment.

Core Action Types in Odoo

Odoo's core action framework includes five main ir.actions.* types. Scheduled actions are also important for automation, but use the separate ir.cron model.

In Odoo, action records can be inspected through technical menus when developer mode and the required access rights are enabled. In versions that expose the relevant menus, navigate to Settings → Technical → Actions. The exact menu organization can vary by version.

Odoo technical action configuration screen from the original tutorial.

Common Fields Used in Odoo Actions

The fields available depend on the action model. When reviewing or creating an action, developers may encounter fields such as the following.

Not every field applies to every action model. For example, window action view settings are not interchangeable with report action configuration.

1. Server Actions in Odoo

Server actions use the model ir.actions.server and perform operations on the server side. Depending on the Odoo version and configuration, server actions can execute Python code, create records, update records, or run a sequence of configured actions.

They are useful when users need to trigger a defined operation from a contextual menu or when an administrator wants to configure a supported server-side operation without building a separate interface.

Common server action operations include:

• Execute Python code supported by the action environment.
• Create a new record with specified values.
• Update values on an existing record.
• Execute multiple configured actions in sequence where supported.

Important fields in the original Odoo 13 context:

• Model: The business model associated with the operation.
• Binding Model: The model whose contextual menu can expose the action.
• Binding View Types: Specifies applicable view types for the binding, subject to version support.
• State: Identifies the configured server action operation.
• Code: Holds the Python code for a code-based action.

In the original Odoo 13 implementation, server action states include names such as code, object_create, object_write, and multi. Verify these implementation details against the target version.

Server action example from the original Odoo development tutorial.

A server action can be used for tasks such as updating selected records or triggering a defined business operation. Python code executed by a server action must follow Odoo's execution restrictions and security model. Avoid granting excessive permissions or executing untrusted code.

Related resource: Odoo development services.

2. Window Actions in Odoo

Window actions use ir.actions.act_window. They open model views and allow users to interact with business records.

For example, selecting a Customers menu can open a list of customer records. Selecting a record can open its form view, while another menu may display the same model using a kanban view.

Window action configuration example.

Common window action fields include:

• Res Model: The model whose records should be displayed.
• Res ID: The record ID to open when a specific record is required.
• View Mode: The view types available for the action, subject to version support.
• View ID: A reference to a particular view.
• View IDs: View-specific configuration used to determine available views and their order.
• Search View: The search interface associated with the action where configured.
• Context: Additional values passed into the view or model environment.
• Domain: A filter used to limit which records are displayed.
• Target: The display destination supported by the version and action type.

Example use case: A custom button on a sales order can open a related list or a wizard. The implementation depends on whether the action needs to display existing records, open a form, or launch a transient wizard.

Python action example from the original Odoo tutorial.

3. URL Actions in Odoo

URL actions use ir.actions.act_url. They allow Odoo to navigate to a specified URL, which may point to a website or another web resource.

A URL action can be useful when a user needs to open an external service, navigate to a relevant web page, or access a URL generated for a business process.

URL action configuration example.

Key fields:

• URL: The destination address.
• Target: Controls how the destination is opened, according to the action's supported options.

Python URL action example from the original tutorial.

In the original Odoo 13 context, target options include self for the current window and new for opening a new window. Confirm supported target values for the Odoo version in use.

Always validate URLs and avoid sending confidential information through an external URL unless the destination and data handling have been reviewed.

4. Client Actions in Odoo

Client actions use ir.actions.client. They are handled by the Odoo web client rather than being defined solely by a server-side operation. A client action typically uses a tag that identifies the frontend behavior to execute.

Developers can use client actions for custom frontend screens, dashboards, or interactive interfaces when standard view types do not meet the requirement. The frontend implementation must be registered using APIs supported by the target Odoo version.

Client action definition from the original Odoo example.

Important concepts:

• Tag: Identifies the client-side action implementation.
• Params: Supplies additional parameters to the client action where supported.
• Target: Controls presentation behavior supported by the relevant client action and version.

The original tutorial references a client-side widget named pdf_report_page. This is an example identifier, not a built-in client action that can be assumed to exist in every Odoo installation.

Client-side APIs have changed across Odoo versions. Older widget-based examples may require significant changes when moving to newer frontend frameworks and registries.

5. Report Actions in Odoo

Report actions use ir.actions.report. They allow users to generate or display reports for business records, including quotations, invoices, delivery slips, and other operational documents.

Report action configuration example.

Common report action fields include:

• Name: The report action's descriptive name.
• Model: The business model associated with the report.
• Report Type: The report rendering type supported by the version and configuration.
• Report Name: The technical report identifier used to locate the report template.
• Groups: Access restrictions controlling which user groups can use the report action.
• Paper Format: Print layout settings where applicable.
• Attachment: Configuration used to determine an attachment name where supported.
• Attachment Use: Controls reuse of stored report attachments according to the report configuration.

Report action example from the original Odoo tutorial.

Odoo report actions commonly work with QWeb templates to generate printable documents. Rendering formats and supported configuration depend on the version and installed components.

When developing custom reports, check template identifiers, access permissions, record data, paper format, and whether attachment caching is appropriate for the document.

6. Scheduled Actions in Odoo

Scheduled actions use ir.cron. They allow configured server-side jobs to run at defined intervals, making them useful for recurring processes that should not depend on a user clicking a button.

Depending on the implementation, scheduled jobs may process queued tasks, perform periodic maintenance, synchronize information, or execute other recurring operations.

Common scheduled action settings include:

• Model or Method: The model and method associated with the scheduled job.
• Interval: The configured interval between executions.
• Next Execution: The scheduled time for the next run.
• Active: Whether the scheduled action is enabled.
• Execution Limits: Additional controls available in the relevant version and configuration.

Scheduled actions should be designed to handle failures, avoid unintended duplicate processing, and operate efficiently on large datasets. Review execution logs and access rights when troubleshooting a scheduled job.

7. Automated Actions in Odoo

Automated Actions allow businesses to trigger configured operations when specified record events or conditions occur. Unlike scheduled actions, which run according to a time-based schedule, automated actions are generally associated with changes or events involving business records.

In relevant Odoo versions, automation rules are commonly implemented through the automation framework, including the base.automation model. Available triggers and configuration options depend on the version and installed modules.

Common use cases include:

• Updating a field when a configured condition is met.
• Creating an activity or notification in response to a business event.
• Executing an approved server-side operation when a record changes.
• Triggering a workflow based on defined record conditions.

For example, an automation rule could perform a follow-up operation when a sales opportunity reaches a particular stage, subject to the available triggers and configuration.

8. Action Bindings in Odoo

Action bindings determine where certain actions appear in the Odoo user interface. They associate an action with a particular business model so users can access it from relevant contextual menus.

For example, a server action may appear in the Action menu when users select customer records. A report action may be available from the Print menu for a supported model.

Important binding fields include:

• Binding Model: Identifies the model with which the action is associated.
• Binding Type: Determines the contextual menu category, such as Action or Print, where supported.
• Binding View Types: Specifies applicable view types, subject to version support.

Action bindings do not execute a new type of business operation by themselves. They control how supported actions are exposed to users in the interface.

9. Menu Actions in Odoo

Menu items provide the navigation structure of Odoo applications. A menu item can be associated with an action so selecting the menu opens the corresponding view or interface.

Menu items are represented by the ir.ui.menu model. The linked action can be a window action, client action, or another supported action type.

For example, a custom Inventory menu can open a list of stock records using a window action. A custom application menu can also open a frontend component through a client action.

When developing menu navigation, consider the menu hierarchy, action reference, user permissions, and applicable access rules. The menu itself is a navigation mechanism rather than a separate ir.actions.* action subtype.

10. Actions Returned From Python Methods

Odoo button methods can return action descriptions as Python dictionaries. The web client interprets the returned value and performs the requested action, provided the response follows the expected format for that Odoo version.

A method may return a window action to open a particular record, a client action to display a custom interface, or another supported action descriptor.

A simplified example of returning a window action is shown below:

def action_open_partner(self):
    self.ensure_one()

    return {
        "type": "ir.actions.act_window",
        "name": "Customer",
        "res_model": "res.partner",
        "views": [[False, "form"]],
        "res_id": self.partner_id.id,
        "target": "current",
    }

This example assumes the model has a valid partner_id field and that the user has appropriate access to the linked customer record. Adapt the method to the actual model and requirements before using it in a custom module.

11. Closing Dialogs and Returning No Action

In supported Odoo client flows, returning False from an action-related method can close an open dialog or indicate that no further action should be performed. This is a response behavior, not a separate action model.

For example, a wizard may complete its operation and close without opening another view. The correct return value depends on the button flow and the Odoo version.

Test dialog behavior in the intended interface, especially when a wizard modifies records or returns a follow-up action.

12. How These Odoo Action Mechanisms Work Together

Odoo actions are often used together to complete a business process. Understanding their roles helps developers choose the correct implementation rather than creating unnecessary custom code.

Important Considerations When Developing Odoo Actions

• Version compatibility: Verify field names, XML definitions, return formats, and frontend APIs for the Odoo version being used.
• Access rights: Ensure the action respects appropriate model access controls and record rules.
• Context and domain: Pass only required context values and use correct domain expressions.
• Performance: Avoid unnecessary repeated searches, expensive computations, and unbounded processing.
• Error handling: Provide useful feedback and design recurring jobs to recover safely from failures.
• Testing: Test actions with intended user roles and realistic business records before deployment.
• Maintainability: Prefer clear, documented implementations over unnecessary custom behavior.

Frequently Asked Questions About Actions in Odoo