Odoo n8n integrationAutomate Odoo with n8n.

Schedules an activity on an existing Odoo record, the way a salesperson plans a call or a task from the record itself.

• Linked Document Model: the Odoo model the activity attaches to, picked from the list or given as an expression such as {{ $json.model }}.
• Linked Document: the record inside that model.
• Activity Type: the kind of activity to schedule, taken from the types defined in Odoo.
• Additional Fields: the mapper where the remaining fields of the activity are filled.

Removes a planned activity. The record it was attached to stays untouched, only the scheduled task disappears.

• Activity: the activity to remove, selected from the list or passed as an expression, most often an id collected by an earlier listing step.

Reads a single activity and returns its fields, which is what a later branch needs before it decides anything.

• Activity: the one to retrieve.
• Fields to Include: under Options, keeps the response to the fields you name instead of the whole record.

Lists activities in batches, with filters that narrow the result to one model or one record.

• Return All: switched on, n8n walks every page of the API; switched off, Limit caps how many activities come back.
• Linked Document Model: in Filters, keeps only the activities attached to one model, for example res.partner.
• Linked Document ID: narrows further, down to a single record.
• Fields to Include: trims the fields returned.

Changes an activity already in the schedule, instead of deleting it and creating a replacement.

• Activity: which one to modify.
• Fields to Update: the mapper listing the fields to overwrite; whatever is left out keeps its current value.

Adds a contact to Odoo and returns it, id included, so the next node can attach a deal or an activity to it.

• Fields to Send: required, the mapper where each Odoo field receives its value, typed by hand or taken from the incoming item with an expression like {{ $json.email }}.

Erases a contact from the database. Nothing on the n8n side brings it back, so the branch that calls this operation usually sits behind a condition.

• Contact: the record to erase, selected in the list or resolved from an expression.

Fetches one contact and hands its fields to the rest of the workflow.

• Contact: which record to read.
• Fields to Include: under Options, restricts the response to the fields you pick, which keeps a crowded contact record readable downstream.

Returns contacts in bulk, filtered with the operator list Odoo itself uses.

• Return All: on, every page is collected; off, Limit stops the run at a fixed number of contacts.
• Field Name or ID, Operator and Value: the filter itself, with operators such as like, in or childOf.
• Fields to Include: the fields you actually want in the output.

Writes new values onto an existing contact, field by field, leaving the rest of the record as it was.

• Contact: the record to modify.
• Fields to Update: the mapper; only the fields listed there are overwritten.

Creates a row in any Odoo model, not only in the three resources the node exposes by name.

• Resource Name or ID: required, the Odoo model to operate on.
• Fields to Send: required, the values for that model, mapped one by one.

Deletes one row from the model you name. Two parameters, both required, because the node has to know the model before it can find the row inside it.

• Resource Name or ID: the model to operate on.
• Record: the row to delete.

Reads one row from an arbitrary model and returns its fields.

• Resource Name or ID: the model to read from.
• Record: which row to retrieve.
• Fields to Include: here it is a comma separated list of field names, such as name,email,phone, and not a picker.

Lists rows from a model you name, which is where most reporting workflows on Odoo begin.

• Resource Name or ID: required, the model to read.
• Return All: on, n8n pages through the whole model; off, Limit caps the batch.
• Fields to Include: a comma separated list of field names.

Updates a row in any model. Same logic as the contact update, with the model chosen by hand.

• Resource Name or ID: the model.
• Record: the row to modify.
• Fields to Update: the mapper carrying the new values.

Opens a deal in the pipeline and returns it, ready to be linked to a contact or picked up by an activity.

• Fields to Send: required, the mapper carrying the fields of the deal, filled by hand or from the incoming item with an expression.

Drops a deal from the pipeline for good. The operation takes a single parameter, which makes it easy to wire by mistake, so a condition in front of it is a reasonable habit.

• Opportunity: the deal to remove, chosen in the list or resolved from an expression such as {{ $json.id }}, usually an id read by an earlier step rather than typed.

Pulls a single deal with its fields, so the workflow can branch on what it finds there.

• Opportunity: which deal to read.
• Fields to Include: under Options, limits the response to the fields you name.

Returns deals in batches, filtered with the same operator list as contacts.

• Return All: on, every page comes back; off, Limit fixes the size of the batch.
• Field Name or ID, Operator and Value: the filter, with greaterThen or notEqual among the operators available.
• Fields to Include: the fields kept in the output.

Moves a deal forward without touching the rest of the record.

• Opportunity: the deal to modify.
• Fields to Update: the fields to overwrite; everything else keeps the value it already had.