Odoo 19.0 Community · Persistent

mail.activity.type: fields, relations and API

The mail.activity.type model ("Activity Type") is a persistent model declared by the Discuss module, then extended by 3 other modules. It exposes 27 fields, 22 of them declared directly on the model; 16 fields from other models point to it. Below you will find every field with its technical name, type, label and relations, followed by an Odoo 19 JSON-2 API call.

View source code Search another model

Model identity

Technical name: mail.activity.type
Label: Activity Type
Type: Persistent (models.Model)
SQL table: mail_activity_type
Origin module: Discuss (mail)
Extended by: fleet, calendar, hr_holidays
Default order (_order): sequence, id
Display field (_rec_name): name

Model fields

22 own fields, 0 inherited from mixins and 5 automatic ORM fields. Click a name to get a direct link to that field.

Hide inherited fields

27 of 27 fields shown

Technical name	Label	Type	Details
active	Active	`boolean`
category	Action Actions may trigger specific behavior like opening calendar view or automatically mark as done when a document is uploaded	`selection`	Values: `default` (None), `upload_file` (Upload Document), `phonecall` (Phonecall)
chaining_type	Chaining Type	`selection`	required Values: `suggest` (Suggest Next Activity), `trigger` (Trigger Next Activity)
create_uid	Create Uid	`many2one` → res.users
decoration_type	Decoration Type Change the background color of the related activities of this type.	`selection`	Values: `warning` (Alert), `danger` (Error)
default_note	Default Note	`html`	translatable
default_user_id	Default User	`many2one` → res.users
delay_count	Schedule Number of days/week/month before executing the action. It allows to plan the action deadline.	`integer`
delay_from	Delay Type Type of delay	`selection`	required Values: `current_date` (after previous activity completion date), `previous_activity` (after previous activity deadline)
delay_label	Delay Label	`char`	computed
delay_unit	Delay units Unit of delay	`selection`	required Values: `days` (days), `weeks` (weeks), `months` (months)
icon	Icon Font awesome icon e.g. fa-tasks	`char`
initial_res_model	Initial model Technical field to keep track of the model at the start of editing to support UX related behaviour	`selection`	computed Values computed at runtime
mail_template_ids	Email templates	`many2many` → mail.template
name	Name	`char`	requiredtranslatable
previous_type_ids	Preceding Activities	`many2many` → mail.activity.type
res_model	Model Specify a model if the activity should be specific to a model and not available when managing activities for other models.	`selection`	Values computed at runtime
res_model_change	Model has change	`boolean`
sequence	Sequence	`integer`
suggested_next_type_ids	Suggest Suggest these activities once the current one is marked as done.	`many2many` → mail.activity.type	computed, stored
summary	Default Summary	`char`	translatable
triggered_next_type_id	Trigger Automatically schedule this activity once the current one is marked as done.	`many2one` → mail.activity.type	computed, stored
create_date	Created on	`datetime`	read-onlyautomatic
display_name	Display Name	`char`	read-onlycomputedautomatic
id	ID	`integer`	read-onlyautomatic
write_date	Last Updated on	`datetime`	read-onlyautomatic
write_uid	Last Updated by	`many2one` → res.users	read-onlyautomatic

Relations

Models linked from this model

mail.activity.type: previous_type_ids, suggested_next_type_ids, triggered_next_type_id
mail.template: mail_template_ids
res.users: create_uid, default_user_id

Fields of other models pointing here

account.reconcile.model: next_activity_type_id
crm.activity.report: mail_activity_type_id
hr.employee: activity_type_id
ir.actions.server: activity_type_id
mail.activity: activity_type_id, previous_activity_type_id, recommended_activity_type_id
mail.activity.mixin: activity_type_id
mail.activity.plan.template: activity_type_id, next_activity_ids
mail.activity.schedule: activity_type_id
mail.activity.type: previous_type_ids, suggested_next_type_ids, triggered_next_type_id
mail.compose.message: mail_activity_type_id
mail.message: mail_activity_type_id

Reading this model through the API

Odoo 19 JSON-2 API call reading the first five records with real fields of the model. Replace the instance, database and API key with your own.

curl

curl -X POST "https://your-instance.odoo.com/json/2/mail.activity.type/search_read" \
  -H "Authorization: bearer $ODOO_API_KEY" \
  -H "X-Odoo-Database: your-db" \
  -H "Content-Type: application/json" \
  -d '{"domain":[],"fields":["name","chaining_type","delay_from","delay_unit","create_uid"],"limit":5}'

Python (requests)

import requests

BASE_URL = "https://your-instance.odoo.com/json/2"
headers = {"Authorization": f"bearer {API_KEY}", "X-Odoo-Database": "your-db"}

res = requests.post(
    f"{BASE_URL}/mail.activity.type/search_read",
    headers=headers,
    json={"domain": [], "fields": ["name","chaining_type","delay_from","delay_unit","create_uid"], "limit": 5},
)
res.raise_for_status()
print(res.json())

External API access requires Odoo's Custom plan.
XML-RPC and JSON-RPC will be removed in Odoo 22 (fall 2028): use JSON-2.
The access rights and record rules of the key's user apply.

Cite this tool

Writing a tutorial, internal documentation or a forum answer? Copy this link to send your readers to the up-to-date reference.

<a href="https://aidoo.ai/en/outils/explorateur-modeles-odoo/mail-activity-type">mail.activity.type (Odoo 19.0)</a>

Sources

Data verified on September 23, 2026 · Odoo 19.0 Community

Have an Odoo project, or want to put your ERP to work with AI? Let's talk

Implementation, custom module development, connecting Claude or ChatGPT to your data: tell us about your context and we will reply within 24 business hours.