Odoo TRIGGER
New Record Created
- Trigger
- Polling
- API key
- Webhook delivery
IMPLEMENTATION
Deploy this event source
Connect the user's Odoo account, configure the source, and choose the webhook where your backend receives events.
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 deployed = await pd.triggers.deploy({
id: "odoo-new-record-created",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
odoo: { authProvisionId: "apn_xxxxxxx" },
timer: { "intervalSeconds": 900 },
modelName: "Model Name",
},
webhookUrl: "https://example.com/webhooks/odoo",
})
console.log(deployed.id)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "odoo-new-record-created",
"webhook_url": "https://example.com/webhooks/odoo",
"configured_props": {
"odoo": { "authProvisionId": "apn_xxxxxxx" },
"timer": { "intervalSeconds": 900 },
"modelName": "Model Name"
}
}'MCP servers expose Odoo actions as on-demand tools.
New Record Created is an event source, so your application deploys it
with the Connect SDK or API and then either receives each event at a
webhook URL or retrieves events on demand with the trigger events API.MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.
SCHEMA
Configuration
These inputs define which events the source watches. Dynamic options are loaded from the connected account.
| Property | Type | Description |
|---|---|---|
timer Timer | $.interface.timer | Required |
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 |
LIFECYCLE
Event delivery
01
Connect
Your user authorizes Odoo through Pipedream managed auth.
02
Deploy
Your backend deploys this source with that user's own configuration.
03
Webhook delivery
Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.
OR
On-demand retrieval
No webhook required. Your app or agent can fetch recent events from the trigger events API.
REFERENCE
Trigger details
- Registry key
- odoo-new-record-created
- Version
- 0.0.1
- App
- Odoo
- Authentication
- API key
- Delivery
- Polling source
- Output
- Events emitted by Odoo.
- Source
- View on GitHub ↗