Webhook -> Path variable -> randomly generated webhook URL path

Questions
1

Hello,

As mentioned in the documentation Webhook node documentation | n8n Docs when we have a dynamic path by specifying the variable i.e :variable we have a webhook url as below

https://internalurl/webhook-test/9b2c5f3f-1479-474c-a61a-3144c6a075be/servicecloud/:variable

The URL internally generates this value → 9b2c5f3f-1479-474c-a61a-3144c6a075be

Is it possible to bypass this above value by some settings to have a different literal name for this so that the url is as below.

https://internalurl/webhook-test/servicecloud/:variable

N8N Version → 1.71.3

Thank You

1 Like
2

It looks like your topic is missing some important information. Could you provide the following if applicable.

  • n8n version:
  • Database (default: SQLite):
  • n8n EXECUTIONS_PROCESS setting (default: own, main):
  • Running n8n via (Docker, npm, n8n cloud, desktop app):
  • Operating system:
3

hi, i have the same issue on ver 1.80.3 at n8n cloud

4

Hello,
this looks like UUID so it is not very likely we will ever be able to just remove it. Probably a lot of things rely on in on the background.

The only way I can think of achieving cleaner public URLs is using a reverse proxy with URL rewriting to mask n8n’s internal webhook URL.

First make sure to add unique variables to each webhook, because you will rely on them for the routing.
Then in the reverse proxy configuration rewrite
external/servicecloud/:var to internal/UUID/servicecloud/:var.

Here is example configuration for
Nginx:

location /servicecloud/ { rewrite ^/servicecloud/(.*)$ /webhook-test/YOUR_UUID/servicecloud/$1 break; proxy_pass http://n8n:5678; }

Caddy:

yourdomain.com { reverse_proxy n8n:5678 rewrite /servicecloud/* /webhook-test/YOUR_UUID/servicecloud/{path} }}

Downsides: You have to update this config when adding new hooks, AND incorrect rules can break routing.

5

I just want to add that if a path variable is not added, then the expected result is achieved:

https://internalurl/webhook-test/servicecloud/ → works with no UUID added to url

https://internalurl/webhook-test/servicecloud/:variable → UUID is added to url ( https://internalurl/webhook-test/uuid/servicecloud/:variable )

6

Hey! It’s not possible to bypass if you are willing to use a dynamic path in the webhook. But here’s the catch: Once you have built the first webhook with the UUID-generated URL, subsequent ones can just be copied and pasted to maintain the same UUID.

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.