Automatically notify another system when an export finishes successfully.
Overview
Webhook Notifications let Advanced Export Pro inform another system when an export finishes. In simple terms, Odoo sends a short message to a web address (URL) so the next step can happen automatically.
Teams use this to trigger actions such as: starting an import in another tool, refreshing dashboards, or creating a ticket/alert when a critical export completes. It reduces manual follow-up work and makes processes more reliable.
Note: Webhooks are usually set up with help from your IT/admin team, because they involve URLs and secure tokens.
Example: After the “Daily Inventory Export” succeeds, a webhook notifies a warehouse system to pull the latest data.
How It Works
- Turn on Send Webhook Notification.
- Enter the Webhook URL provided by your IT/system.
- Choose the authentication method (if required).
- After a successful export, the system sends a request and stores the response.
Step-by-Step Guide
- Open your export configuration.
- Enable Send Webhook Notification.
- Paste the Webhook URL.
- Select Webhook Authentication Type (None, Basic, Bearer Token, API Key).
- Fill the required credentials (username/password or token).
- Run a test export (small dataset).
- Check Webhook Response and Webhook Sent to confirm it worked.
Fields Table
| Field Name | Description | Example |
|---|---|---|
Send Webhook Notification |
Turns webhook notifications on/off. |
On |
Webhook URL |
Where the notification is sent. |
https://api.company.com/exports/hook |
Authentication Type |
How the receiving system verifies Odoo. |
Bearer Token |
Webhook Token / API Key |
Secret used for authentication. |
(hidden) |
Custom Headers |
Extra request headers (advanced). |
{“X-App”:”odoo”} |
Retry Attempts |
How many times to retry if the webhook fails. |
3 |
Webhook Sent |
Whether the webhook was sent successfully. |
Yes |
Webhook Response |
Last response message returned by the receiving system. |
200 OK |
Field Explanations
Send Webhook Notification
Enable this only when you have a valid target URL and approval to notify it.
Webhook URL
The address that receives the “export completed” message.
Authentication Type
Choose the method required by your receiving system (ask IT).
Webhook Token / API Key
A secret credential; store and share it safely.
Custom Headers
Optional extra information some systems require.
Retry Attempts
Helps recover from temporary network issues.
Webhook Sent
Quick confirmation that the notification was sent.
Webhook Response
Useful for troubleshooting; share with IT if it shows an error.
Tips
- Test webhooks with a small export before scheduling.
- Use clear export names so downstream systems can identify the event.
- When a webhook fails, check network access and authentication first.
Common Mistakes
- Using the wrong URL (test vs production).
- Copying tokens with extra spaces or missing characters.
- Assuming webhook success means the file was delivered — verify delivery separately if needed.