OdooWiki OCA HUB

Mail Activity on Fetchmail with Team Activity

fetchmail_mail_activity_team_activity folder_open OCA/social open_in_new
Hidden License: AGPL-3

* Uses mail.activity.team to configure automatic activities when mails arrive for the specified models. * The configuration to add RMA and PO models (Settings --> Technical --> Activity Teams menu)

auto_awesome What this module does

AI-generated from the code · Odoo 15.0

Automatically creates an email activity for the responsible team when an incoming email is routed to a record of a configured model, so the team is notified to follow up.

This hidden module connects incoming email handling with activity teams. When Odoo receives an email and decides which record it belongs to, it checks whether that record's model is listed in an activity team configuration.

If a matching team is found and the record already exists, Odoo schedules an email activity on that record for the team's responsible user (or the first team member). The activity is marked as automated and linked to the team, so it appears in the record's activity list and in the team's activity views.

  • Only models that support activities are considered.
  • If the record already has an automated email activity, no duplicate is created.
  • If no team is configured for the model, or the record does not exist yet, nothing happens.

Configuration is done through the Activity Teams menu (Settings > Technical > Activity Teams), where you link models to a team and choose the responsible user or members. The module extends the generic mail thread behaviour, so it applies to any model that uses messages and activities, such as sales orders, purchase orders or RMAs, provided the model is added to a team.

Models and fields (1)
  • mail.thread · extends an existing model

Text generated by AI (DeepSeek) from reading the Odoo 15.0 code on GitHub; it may contain mistakes, so check the code before deciding. View the code on GitHub

Availability by version

Reviewed: 2026-11-03
Confirmed (verified in repository and branch) Estimated (unverified) No information

Confirmation status: 1 confirmed, 8 with no information of 9 versions.

terminal Installation and usage

No verified information

Installation instructions, the distribution package, dependencies and configuration steps are not shown because they have not yet been verified in the module documentation for any version.

info

Data imported from GitHub: this sheet reflects the latest catalog review, not a live lookup. Always check the module documentation and staging before installing in production.