Cannot make POST request with Webhook

Questions
,
1

Description

I am trying to use the Webhook widget to connect to Telegram. This is what I do:

image
image1106×1276 65 KB

:warning: Important:: insteald of localhost I actually use ngrok URL!

However when I test this I get the folloiwng error:

{
"code": 404,
"message": "This webhook is not registered for GET requests. Did you mean to make a POST request?"
}

However when I use the Telegram widget to basically do the same, I am able to connect and everything works perfectly.

Searching online I saw that several people faced the same issue as it can be seen here: Webhook interprets all sent requests as GET · Issue #12751 · n8n-io/n8n
I tried to follow the suggestions from this thread but without success.

Question

Do you know what I may be doing wrong? Any possible suggestion on how to avoid this error?

Information on your n8n setup

  • **n8n version:v2
  • **Database (default: SQLite):Sqlite
  • **n8n EXECUTIONS_PROCESS setting (default: own, main):main
  • **Running n8n via (Docker, npm, n8n cloud, desktop app):docker
  • **Operating system:Linux Mint
2

@Federico_Gentile that 404 means a GET actually reached the node even though it’s set to POST, so something is changing the method, not the node config.

Two usual causes with ngrok:

  1. Testing by opening the URL in a browser. The address bar always sends GET. A POST has to come from curl/Postman or Telegram.
  2. A redirect downgrading the method. If you call the http:// ngrok URL (or hit a trailing-slash redirect), the 301/302 to https turns your POST into a GET. Use the https ngrok URL directly, and set WEBHOOK_URL=https://your-ngrok-domain so n8n emits https.

How are you sending the failing request: browser, curl, or Telegram setWebhook?

3

Thank you so much for the reply. So far I am sending the request via the search bar of the browser, so that could be a reason. If I want to test it correctly, what would you recommend to use then?

4

@Federico_Gentile yep, that’s it, the search bar sends a GET so it’ll always hit that error.

To test, send a real POST. Quickest is curl:

curl -X POST -H "Content-Type: application/json" -d '{"hello":"world"}' https://your-ngrok-domain/webhook-test/9390c7f6-894b-4948-9579-8d9ec556dc7b

One catch with the Test URL: click “Listen for test event” first, it only captures a single request while it’s actively listening. Postman works too, just set the method to POST.

For the real Telegram setup, switch to the Production URL, activate the workflow, then point Telegram’s setWebhook at that https URL. Telegram sends updates as POST, so it’ll behave like your Telegram Trigger already does.

5

The error is happening because Telegram is trying to access your webhook URL with a GET request, while your n8n Webhook node is configured to accept only POST requests.

A few things to check:

  1. Make sure you’re using the Production URL (or the active Test URL while listening) from n8n and not opening the URL directly in a browser. Browsers send GET requests by default.
  2. Verify that the Telegram webhook is registered correctly:


https://api.telegram.org/bot<BOT_TOKEN>/setWebhook?url=<YOUR_NGROK_URL>/webhook/<path>
  1. After setting the webhook, check it with:


https://api.telegram.org/bot<BOT_TOKEN>/getWebhookInfo
  1. In n8n, click “Listen for test event” if using the Test URL. Test webhooks only work while the workflow is actively listening.
  2. Confirm that the Telegram Bot Trigger/Webhook path exactly matches the path configured in n8n and that ngrok is forwarding requests to the correct n8n port.
  3. If you manually visit the webhook URL in a browser and see:


{
  "code": 404,
  "message": "This webhook is not registered for GET requests. Did you mean to make a POST request?"
}

that’s actually expected behavior because the endpoint only accepts POST requests.

6

Thank you so much @achamm ! This was the right answer!

7

you are welcome and i am open to answer any question for you