Incoming webhook trigger
In the dashboard you each task would have a URL for each of your environments.
Then you can use this URL in 3rd party products. Any data in the body of the request to that URL would come through to the task as the payload.
In the dashboard you each task would have a URL for each of your environments.
Then you can use this URL in 3rd party products. Any data in the body of the request to that URL would come through to the task as the payload.
Comments34
Oct 27
PinnedInbound webhooks are now in public beta in Trigger.dev for both cloud and open source from 4.8.0.
Thanks for all your votes, feedback and comments that shaped how we built this.
You can read the full announcement here. Or go straight to the feature page or docs.
Anonymous User
Sep 18, 2024
This would be really helpful
Jack
Oct 27
Thanks, it’s now live!
An Anonymous User
Oct 3, 2024
So the idea is you can trigger a specific task via an HTTP POST request? Heck yeah!
An Anonymous User
Oct 7, 2024
Yes, and would be really cool to transform the incoming webhook json to the function payload
Jack
Oct 27
Yes and it’s now live. Let us know what you think!
Ashley Williams
Aug 15, 2025
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)
Jack
Oct 27
Thanks, it’s now live! And we support Shopify!
Aaron J. Spurlock
Oct 3, 2024
I’m 100% on board with triggering a task via HTTP POST!
Jack
Oct 27
woo it’s now live!
David Gonsalves
Apr 22, 2025
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.
Jack
Oct 27
Thanks, it’s now live. Would love to know what you think.
An Anonymous User
Nov 21, 2024
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
Jack
Oct 27
Thanks, it’s now live! On your list: requests are verified before anything runs, so bad or unauthenticated calls never start a run. The built-in WhatsApp source answers Meta’s GET verification for you. You can send test events from the endpoint’s Test tab and replay any past delivery.
Saved test payloads and raw-body access aren’t in yet, so let us know if you need them.
An Anonymous User
Dec 9, 2024
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.
Jack
Oct 27
Yes appreciate this feedback. In case you’re still interested, webhooks are now live!
An Anonymous User
Feb 25, 2025
Is the benefit of this vs using the API that it’s limited to one task only?
Jack
Oct 27
It’s mostly that some services only support webhooks and so before, people would have to write an intermediary to receive the webhook before calling Trigger. But webhooks are now live!
Matthieu Mordrel
Jul 8, 2025
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.
Jack
Oct 27
Thanks, it’s now live! I hope this is still true