N8n on AWS HTTP Request node to Activate Webhook Trigger

Questions
1

Ok, so I am hosting community n8n on AWS and I am trying to use a Webhook trigger and HTTP request nodes to kick off 10 workflows simultaneously (Can’t use execute sub because each one takes over an hour and I don’t have the time to wait for each to execute in order).
I can not get the Webhook node to work to save my life. I have both set to post, I am using the correct test url, it is listening for the test event, and I am not using auth.
Is it an issue of trying to call a webhook from an http request node on the same instance?
I’m not going to show the nodes bc I do not want my instance ip to be posted to the public.
There is no error code, the HTTP request just times out.
Any help will be greatly appreciated. Thank you in advance!

Describe the problem/error/question

What is the error message (if any)?

Please share your workflow

(Select the nodes on your canvas and use the keyboard shortcuts CMD+C/CTRL+C and CMD+V/CTRL+V to copy and paste the workflow.)

Share the output returned by the last node

Information on your n8n setup

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

Hi, @Will_Roske !

Based on the information provided, the most likely issue is that you’re using the test webhook URL for production execution.

Try this first:

  1. Activate your workflows to get the Production Webhook URL
  2. Use the production URL format: https://your-aws-instance/webhook/your-path
  3. Replace the test URLs in your HTTP Request nodes with these production URLs

If that doesn’t resolve it, check these settings in your n8n environment variables:

  • N8N_CONCURRENCY_PRODUCTION_LIMIT - if set to 1, increase it to at least 10
  • EXECUTIONS_MODE - check if you’re using regular or queue mode

To test if it’s a self-call issue:

  • Try calling one of your webhooks from outside your AWS instance (from your local machine using curl or Postman)
  • If it works externally but not internally, it’s likely an AWS Security Group or network configuration blocking self-requests
3

I hadn’t thought about it being a security group issue. Do you know what I would have to change to fix it if it is the issue? I am still using the test url and I have not activated the workflow. I haven’t started using multiple of them, I need to get the first one working before moving on, but I’ll make sure to up the concurrency limit. Also, Which Executions_Mode should I be using? Thank you for the assistance!!

4

Perfect! Now I understand your situation better.

you’re using the test URL and haven’t activated the workflow.

Here’s what you need to do (in order):

Step 1: Activate your workflow

  1. Open the workflow with the Webhook trigger
  2. Click the toggle switch at the top right to activate it (it will turn from grey to active/green)
  3. Once activated, the Webhook node will display a Production URL (this is different from the test URL)
  4. Copy this production URL

Step 2: Update your HTTP Request node

  1. Open the workflow that has the HTTP Request node
  2. Replace the test URL with the production URL you just copied
  3. Make sure it’s still set to POST method

Step 3: Test it

  • Run the workflow with the HTTP Request node
  • It should now successfully trigger the webhook workflow

About your other questions:

Security Group: Only worry about this IF:

  • The webhook works when you test it externally (like from your local computer using curl/Postman)
  • BUT it times out when called from within the same n8n instance

For now, keep whatever you’re currently using. You only need to consider queue mode later when you’re running all 10 workflows in parallel. Focus on getting one working first :slight_smile:

The test URL has limitations - production URL is what you need for this to work.