How Can I Optimize the Initial Response Time for a Pipedream Webhook Endpoint?

21

No problem, it was my first thought too.

22

Is that the total execution, or just the time taken to respond the HTTP trigger?

23

That is time to response (Postman).

24

Ah gotcha

25

Where’s the custom response step relative to the first action step in your workflow?

26

Just response, because the triggering system things the server is down and disables the entire automation.

27

Everything else is happening async.

28

I just need to give a challenge response or a simple success, if not for the challenge I could skip this all together.

29

Gotcha

30

Can you share the workflow URL you see in your browser window?

31

I just created a test that was ONLY the trigger and a custom response, and while a bit better it is still too long (w/ 512 MB):

Cleanshot - Pipedream Verification Test Copy - My Workspace in Postman at 2024-09-16 at 10.16.13@2x.png

32

Either of the incoming webhooks here: Sign Up - Pipedream

33

Is that the first execution or have you tried more than one?

34

Yeah, that is the first, the subsequent were still >1500ms

35
36

That is the almost empty webhook. No actual workflow steps.

37

Just trigger/custom response.

38

There is no way to use a variable in the static response from the trigger step right? If I can echo back that challenge I don’t need a custom response or code step beyond that.

39

I don’t know if you are twisting dials, but I am seeing this light version being faster now. ¯_(ツ)_/¯

40

There is no way to use a variable in the static response from the trigger step right? If I can echo back that challenge I don’t need a custom response or code step beyond that.
What do you mean? Like a static path from the trigger like steps.trigger.event.body.challenge?