Has anyone had any success connecting webhook triggers to n8n? It’s working fine for Make.com - but I’d much rather use the self-hosted n8n option as it’s free/unlimited. I’m able to use Postman to trigger the webhook for n8n, and it’s able to connect via typing the webhook endpoint into the browser. For some reason Glide is causing it to timeout and I can’t find out why.
So it’s a webhook URL that n8n generated, and you can’t trigger that using Glide’s Trigger Webhook action?
That’s right. I was able to trigger it using the curl method in Terminal and via the Chrome browser and Safari browser, in addition to getting it work using Postman.
For some reason, Glide will not trigger it.
That’s weird. Can you check the log in your actions on the Glide side to see what it says? Can you show us how you configure it in Glide?
@dezwatz Did you ever get this to work? For some weird reason I’m running into similar issues and it’s highly annoying.
Is it for a specific webhook or every webhook you create in n8n?
1 Like
Yes, I did! Walk me through your setup and I can explain how I set it up!
1 Like
Solution below!
So far, it seems for most webhooks I create. So I’m using Trigger Webhook in Glide, sending it to n8n.
When using the n8n TEST url, it works. However, after switching the n8n workflow to production, I immediately get a status 500 error OR (most of the time) I get a webhook request timed out in Glide.
Also, I’ve experienced this:
- On several teams, several apps
- On several different workflows, both in n8n and in Glide
However, there’s some good news. It seems I managed to fix it and it’s super simple.
SOLUTION
Okay so for anyone running into this issue as well, here’s the fix. Go to your Webhook Trigger and change the parameters below.
1st option: you must set this parameter in the n8n Webhook Trigger to Respond: Immediately
2nd option: you set the parameter to “Using Respond to Webhook Node”, BUT then make sure to add that node fairly soon after this node, so the request won’t time out after, say, one minute.
Hope this helps anyone looking for a solution 
.
1 Like
See above. Was that your solution as well? If anything else, could you share for people running into this?
1 Like
Thank you, it seems Glide always expect a response. Using solely the Webhook node won’t do that, hence your fix.
1 Like