This topic was automatically generated from Slack. You can find the original thread here.
I am running into an issue with triggers. Given that the payload only contains the raw body of the original source payload, I have no way of knowing which specific trigger sent me the payload. How do I get around this? It is not an option for me to deploy every single trigger with a unique webhook address.
That is the guidance right now since as you mentioned, we don’t currently decorate that data at all, but we do plan to in the future, so you could use a single webhook and handle the routing on your end.
Ok, I figured out a workaround. I’ve created a separate workflow in Pipedream with an https trigger. I then point my trigger deployment to that https endpoint and append the url with a ?app_id=[app_id]&component=[component-key] querystring.
In my workflow I then forward the trigger body to my own webhook and add the app_id and component as separate parameters. 