Very simple HTTP API Request fail

julien-1f7b08 · June 5, 2022, 1:30am

Hello,

I am evaluating Pipedream … so far the first thing I try failed. I’ve read the help doc many time, no help for that.

Created many workflow with the same thing … didn’t work!

HTTP API Request → Return custom response = The workflow trigger is not compatible with $.respond

Thanks

netherslayer87 · June 5, 2022, 2:08pm

Make sure to click Retern a custom response from your workflow

julien-1f7b08 · June 5, 2022, 5:37pm

Thanks for the reply. This is exactly what I did…

I will create a new workflow and post picture of the steps.

All stock example code nothing custom at all!

I just want to test the response time with a custom response.

pierce · June 6, 2022, 1:54pm

Hi @julien-1f7b08

Thanks for sharing the very thorough screenshots and steps you took, I was able to reproduce the same bug. I’ve also filed a bug report on our Github tracker here:

github.com/PipedreamHQ/pipedream

[BUG] HTTP API request trigger doesn't allow custom response

opened 01:52PM - 06 Jun 22 UTC

ctrlaltdylan

bug triaged tracked internally

**Describe the bug** When creating a workflow triggered by an API endpoint, e…ven when I have the custom response option enabled, the deployed workflow claims `$.respond` is not compatible with this trigger. **To Reproduce** Steps to reproduce the behavior: 1. Create a new workflow 2. Select HTTP API Requests as the trigger ![CleanShot 2022-06-06 at 09 49 17@2x](https://user-images.githubusercontent.com/2694734/172173828-7142e8c8-4cc1-4c26-99cd-bd5381d9e3e5.png) 4. "Return a custom response from your workflow" is already selected 5. Add the default custom response prebuilt action as a step 6. Test & deploy the workflow 7. Open a test event, see that it returns the default response and shows an error: ![CleanShot 2022-06-06 at 09 51 23@2x](https://user-images.githubusercontent.com/2694734/172174140-2893f45a-f560-4f23-9e13-b915fb1fc3e8.png) **Expected behavior** I expect the prebuilt HTTP API requests trigger to allow custom responses. **Additional context** User report: https://pipedream.com/community/t/very-simple-http-api-request-fail/2542

Thanks for your patience!

pierce · June 6, 2022, 4:28pm

Hi @julien-1f7b08

Thanks for your patience. This bug should be fixed, you’ll just need to edit and resave your HTTP trigger, then and redeploy your workflow for the effect to take place.

elizavnikolaeva · June 7, 2022, 1:33pm

Hello. I also can not get the response body, everything is according to the instructions.

pierce · June 7, 2022, 1:38pm

Hi @elizavnikolaeva

First off, welcome to the Pipedream community. Happy to have you!

Please try editing your trigger, saving it, then returning it to the original setting and saving again.

This will cause your trigger to get the code update that fixes this issue.

Alternatively you can delete the trigger entirely and create a new one. The fresh HTTP source will also fix the bug.