Issue with applications send an http request event

Technical Help
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

baserow:1.34.5

If you are self-hosting, which installation method do you use to run Baserow?

Docker version 28.3.0

What are the exact steps to reproduce this issue?

I’ve locally hosted n8n and Baserow, and I’m trying to build a Baserow application that sends an HTTP request when a button is pressed. However, the request consistently fails.
Error log:
[BACKEND][2025-07-24 07:07:51] WARNING django.request.log_response:241 – Bad Request: /api/builder/workflow_action/312/dispatch/

Accessing http://localhost/api/builder/workflow_action/312/dispatch/ returns:
{“detail”:“Method "GET" not allowed.”}

I came across a similar issue (Issue with Webhook URL Check) and added BASEROW_WEBHOOKS_ALLOW_PRIVATE_ADDRESS=true to my Docker Compose file, but the problem still persists.
Interestingly, webhook actions triggered from the Database module or using curl within the container are able to successfully reach the n8n trigger.

Attach screenshots, videos, or logs that demonstrate the issue.

螢幕擷取畫面 2025-07-24 150642.png
螢幕擷取畫面 2025-07-24 150642.png429×266 13.9 KB

2

Hey @Jim.pau not sure about your setup but I think you try to send a request to a n8n endpoint. The variable BASEROW_WEBHOOKS_ALLOW_PRIVATE_ADDRESS only works for calling a private address with a webhook but it doesn’t work for the “Send HTTP request” action so it might be the reason. We need to add a variable for that. In the meantime may be you can use a tunnel to expose your n8n to Baserow?

Yeah you can’t simply visit a dispatch URL it needs a POST method and a proper payload but it doesn’t mean there is an error.

3

Thank you so much for the reply. But unfortunately, my project needs to be working totally offline. I can’t set up a tunnel. So, my workaround is: I make a button to update a row in the DB, and I make a webhook for the row to post to n8n when it is updated.

4

FYI the variable should be part of the next release.

5

Hi! Is there any update, because the Http Request action always return an error 400 (ERROR_SERVICE_UNEXPECTED_DISPATCH_ERROR)
It seems to be working with main domain, but not with subdomains. For the example :

Do you have any ideas ?

Thanks !

6

Some extra information, not really useful…

[BACKEND][2025-08-20 20:13:34] DEBUG 2025-08-20 20:13:34,796 urllib3.connectionpool._new_conn:1022- Starting new HTTPS connection (1): n8n.subdomain.com:443  (B 
[BACKEND][2025-08-20 20:13:34] Bad Request: /api/builder/workflow_action/21515/dispatch/ (B 
[BACKEND][2025-08-20 20:13:34] WARNING 2025-08-20 20:13:34,910 django.request.log_response:241- Bad Request: /api/builder/workflow_action/21515/dispatch/  (B
7

Hi @Nassim, could you share some information on where you’re running Baserow? If you’re a self-hoster, which version of Baserow do you have installed?

Cheers,
Peter Evans

8

Hi @picklepete,

I was running a self-host instance on 1.34.5.

Finally, I fixed my problem using INTEGRATIONS_ALLOW_PRIVATE_ADDRESS variable.
My subdomains are resolved locally by my router, so my Baserow instance consider every service as a local service.

Thanks !

1 Like