💡 Have your say - help us improve Webhook Triggers!

[jake]

Hello community!

We’re looking at ways to improve our Webhook Triggers and would love to get your input.

• Any stories you have of Webhook Triggers being a nightmare to setup, test or run?
• Any issues you’ve had running Webhook Triggers in production that were tough to debug or never resolved?
• Any times you really wished they had some extra functionality?

We’re also looking to hear stories about your experiences with Webhook based triggers such as the Telegram trigger.

Detailed anecdotes and explanations, especially with screengrabs are much appreciated

Thanks in advance for helping us improve n8n,
Jake - Senior Product Designer, Nodes Team

[solomon]

I’ve been using n8n as the backend of a SaaS in development and using webhooks as a sort of RESTful API.

But due to limitations of the Webhook Trigger, I can’t exactly follow the recommended RESTful API structure.

More details below:

• Flexible Webhook Endpoints
• Optional Endpoint path in webhooks - is it possible?
• Scaling webhook requests