As of now, I am permamently redirected to Pipedream and can no longer access my Requestbin data. I have been able to avoid that for a year or so. Pipedream looks really cool with lots of features but one thing is missing: Simplicity.
You lost that when you moved to Pipedream.
All I want to do right now with Pipedream is recreate what I had with Requestbin which was to get a dump of all Request and client info that is available from a request to the endpoint.
I have gone through some of the docs but it is not intuitive.
Hi @brentonhouse , thanks for reaching out and for using RequestBin / Pipedream.
Did you happen to see our docs on examining incoming event data? If you want to copy the value of any data / headers sent to your HTTP endpoint, just hover over the relevant field and click the button to Copy Value:
Does that help or are you looking to do something else?
The problem is that when I console.error the incoming data in the nodejs step, it is based on the POST coming in from the previous step and not the original request. If I try to delete that first step, it tells me my nodejs step is no invalid because it requires it…
Could you tell me the broader use case you’re trying to solve? Are you trying to simply examine specific incoming data (like the body of the HTTP POST request or a specific header), or do you need to manipulate the data with Node.js code?
Great thanks. That’s what I thought based on your original post. Did you happen to see the resources I shared above re: examining the incoming event data? Does that not address your use case, and were you looking to do something different?
