Odoo ACTION
Search and Read Records
Search and read records from Odoo. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Odoo account once, then configure and run Search and Read Records from your backend or agent.
import { PipedreamClient } from "@pipedream/sdk"
const pd = new PipedreamClient({
projectId: process.env.PIPEDREAM_PROJECT_ID!,
clientId: process.env.PIPEDREAM_CLIENT_ID!,
clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
projectEnvironment: "production",
})
const result = await pd.actions.run({
id: "odoo-search-read-records",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
odoo: { authProvisionId: "apn_xxxxxxx" },
modelName: "Model Name",
domain: "Search Domain",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "odoo-search-read-records",
"configured_props": {
"odoo": { "authProvisionId": "apn_xxxxxxx" },
"modelName": "Model Name",
"domain": "Search Domain"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "odoo",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "odoo-search-read-records",
arguments: {
modelName: "Model Name",
domain: "Search Domain",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
modelName Model Name | string | The technical name of the Odoo model to interact with (e.g. res.partner, helpdesk.ticket, sale.order, crm.lead). Use the List Models action to get the model name. Required Dynamic |
domain Search Domain | string | Odoo search domain as JSON. Single-condition examples: phone contains 555 -> ["phone", "ilike", "555"]; email contains acme.com -> ["email", "ilike", "acme.com"]; companies only -> ["is_company", "=", true]. Use a full domain array for multiple conditions. Logical operators apply to the criteria that follow them, so use ["|", ["id", "=", 7583], ["id", "=", 7584]] for a two-condition OR. See domain docs. Optional |
fields Fields | string[] | The fields to return in the results. If not provided, all fields will be returned. Required Dynamic |
limit Limit | integer | Maximum number of records to return. Optional |
offset Offset | integer | Number of records to skip before returning results. Optional |
order Order | string | Sort order (e.g. write_date desc, name asc). Optional |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- odoo-search-read-records
- Version
- 1.0.2
- App
- Odoo
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗