Incoming webhook trigger

This would be really helpful

I’m 100% on board with triggering a task via HTTP POST!

This would be great… even more so if we can make it do authentication so that we can use it for services like Shopify.

(You have to return 401 errors etc if they call it with permission etc)

It would be great if we have:

1. A way to manually input multiple test payloads that we can “favourite”, re-name, and re-use
ex: (payment_approved, payment_refunded, payment_chargedback)

2. An accessible request raw body

3. One task for each HTTP method over a single endpoint (some webhook integrations simply won’t work without this, like whatsapp)

4. A flexible middleware/authentication function that does not count towards tasks executions, as webhooks can be called by anyone

I assumed this was part of Trigger already, spent a few hours going through doc and doing a first task until I figured out it wasn’t possible. Now I need to look for an alternative because it makes no sense to setup a serverless function that calls a trigger, as per the doc.

Is the benefit of this vs using the API that it’s limited to one task only?

Very much needed, would open the doorway to integrating with alot more third party services, especially ones where we cannot control the shape of the payload. Once this is implement it would make, as a developer, using services like zapier and others obselete for the most part.

Would love to see this implemented. Having webhooks be able to trigger tasks would probably make me switch from n8n to trigger.dev for many workflows.

Please also consider allow triggering functions by consuming a message queue - using MQTT or similar widely supported standard