Send Odoo timesheets, expenses and vendor bills to Equity Matrix as contributions.
Odoo can send a record to Equity Matrix whenever it’s saved or deleted. Its built-in webhooks can’t add the Authorization header the API needs, though, so the connection goes through Make or Zapier. The webhook action arrived in Odoo 17, so this needs Odoo 17 or later, and it works on Odoo Online too.
What gets sent
| Odoo record | Contribution type | value |
|---|---|---|
Timesheet line (account.analytic.line) | TIME | Hours spent |
Expense (hr.expense) | CASH | Total amount |
Vendor bill (account.move) | CASH | Total amount |
Map the other fields like this:
- the employee’s work email →
memberEmail - the record’s date →
date - the record’s description or name →
description odoo:{model}:{id}→externalId, for exampleodoo:account.analytic.line:4821
1. Create a webhook in Make or Zapier
- Make: start a scenario with Webhooks → Custom webhook and copy its URL.
- Zapier: start a Zap with Webhooks by Zapier → Catch Hook and copy its URL.
2. Add automation rules in Odoo
Open automation rules in Odoo: in Studio, under Automations, or with developer mode on, under Settings → Technical. For each record type you want to send:
- Create a rule on the model, like Analytic Line for timesheets.
- Under Apply on, add a filter so the rule only runs for this organization’s records, for example timesheets on a particular project or analytic account, or records for one company if your Odoo database has several.
- Set the trigger to On save, and under When updating field, pick the fields that should trigger a send: the date, the hours or amount, the employee and the description.
- Add the action Send Webhook Notification, paste the URL from step 1, and pick the fields to send: the employee’s work email, the date, the hours or amount, and the description.
For deletions, add a second rule with the trigger On deletion that sends the record’s ID to the same webhook. Test that this rule fires on your Odoo version before relying on it.
More than one Equity Matrix organization
Each API key sends to one Equity Matrix organization. If you’re in several, create a key in each organization, and set up one Make scenario or Zap per organization, each with its own webhook URL and key. Then give each organization its own automation rules in Odoo, filtered with Apply on to that organization’s projects, analytic accounts or company, and pointing at that organization’s webhook.
3. Send it to Equity Matrix
In Make or Zapier, add an HTTP step after the webhook, as in Connect any tool with Zapier or Make:
- For creates and edits,
POSTthe mapped contribution tohttps://api.equitymatrix.io/v1/contributions. - For deletions, send
DELETEtohttps://api.equitymatrix.io/v1/contributions/external/odoo:{model}:{id}, and treat a404as done.
Sending records you already have
Automation Rules only fire on changes from now on. To send existing timesheets or expenses, export them from Odoo and send them through Create or update in a batch, using the same externalId format. Because the IDs match, any record that changes later updates its contribution instead of duplicating it.
Odoo.sh and self-hosted
If you run Odoo.sh or host Odoo yourself, a developer can call the API straight from Odoo instead. Odoo doesn’t allow outside requests from an Automation Rule’s code, so they’d add a small custom module that sends the request, and have the rules call it. Make sure that code never blocks saving the record in Odoo when Equity Matrix can’t be reached. Log the error instead.
If something doesn’t show up
- A timesheet for an employee with no hourly rate in Equity Matrix fails with a
422. - An employee whose work email doesn’t match their Equity Matrix email fails with a
422.
Both show as the key’s last error on the API Keys page.