Hola! Unfortunately, the quick answer is no, not directly. (Your 192.1.x.x cannot connect directly with the Cloud, you need a middle man who does the handshake between your intranet & the internet)
Since your n8n workflow is in the n8n Cloud (a public/external network) and your Odoo is hosted in your Intranet (a private network), the n8n cloud server cannot see or reach your Odoo server’s IP address.
The Two Best Workarounds
To make this connection, you have two main options:
Expose Odoo (Less Secure): Put your Odoo instance on the public internet, perhaps using a reverse proxy and firewall rules. However, this is generally discouraged for security reasons.
Use a Self-Hosted Tunnel/Bridge (Recommended): The better solution is to set up a secure bridge or tunnel (like a reverse proxy, VPN, or tool like Ngrok or Cloudflare Tunnel) on your intranet. This bridge securely exposes only the required Odoo port to the public internet, allowing the n8n Cloud to connect to the tunnel’s public address, which then forwards the request privately to Odoo.
Bottom line: n8n Cloud needs a public-facing address to connect, and an Intranet address is inherently private. I’m happy to help.
Important NOTE If you decide to expose your Odoo instance make sure to secure your server as you’ll be opening a Port to the World. Don’t just expose the IP:Port 10.x.x.x:1234 use the revese proxy.