Chatter & Activity Tools¶
These tools let the AI leave notes on the chatter of any mail-thread record and schedule Odoo activities (calls, meetings, to-dos…) — exactly the same things a human user would do from the chatter widget.
post_message¶
Post a chatter message (note) on a record. The model must
inherit mail.thread.
Notes:
Accepts either pure plain text (
"Friendly reminder: please follow up.") or fully-formed HTML wrapped in a single<p>/<div>.Never mix the two — the chatter widget would render the tags literally.
message_typecan becomment(visible to followers) ornotification(system notification).
Category: chatter. Risk: low.
Tip
Use post_message to keep a paper trail of what the AI
did. For example, after the AI updates a customer’s
contact details, ask it to post a chatter note with the
diff — auditors love it.
schedule_activity¶
Schedule an Odoo activity (call, to-do, meeting, etc.) on a
record. The model must inherit mail.activity.mixin.
Arguments:
model,id— target record.activity_type— the XML ID of anmail.activity.type(e.g.mail.mail_activity_data_call).summary,note,deadline(YYYY-MM-DD), and an optionaluser_idfor the assignee (defaults to the current user).
Category: chatter. Risk: low.
read_activities¶
List pending activities scheduled on a record. Useful for prompts like “What activities are pending on Acme Corp?”.
Category: chatter. Risk: low.
Typical user prompts¶
“Leave a note on quote S00012 that I called the customer.”
“Schedule a follow-up call for next Tuesday on lead 1438.”
“Remind me — what activities are open on customer Azure Interior?”
The AI translates each into a single chatter / activity tool call.
Safety rails¶
Chatter and activity writes apply the same security:
The Odoo user behind the connection must have rights to read and post on the target record.
Admins can require approval for
post_messageandschedule_activityper connection — useful when the connection is shared with external contractors.
See also