It would help if there was a node for:
webhook trigger
My use case:
I’d like to request that the webhook trigger node be more RESTful, e.g. be able to have outgoing nodes for GET/POST/PATCH/PUT/DELETE etc. It should also be able to parse URL routes and variables, for example https://[host].app.n8n.cloud/webhook-test/70605a77-0a90-49a4-9831-393fee34dd42/:id?filter=xyz (e.g. follow RESTful standards). This would make it easier to have workflows on the same page that behave more like standard APIs, rather then having multiple triggers and separate workflows for the same endpoint. It should also be able to respond with a custom HTTP response code (200, 201 (Created), etc). I’m thinking the exit nodes would reflect the supported methods (GET/POST/etc)
Any resources to support this?
Standards: Web API Design Best Practices - Azure Architecture Center | Microsoft Learn
Are you willing to work on this?
Seems like a core node, but I’m happy to help test it!