How to Get Detailed Error Responses in Pipedream Workflow via HTTP Invocation?

Help
1

This topic was automatically generated from Slack. You can find the original thread here.

Hi @U02A06JPKEH,
I’m integrating with Pipedream workflows via direct HTTP invocation and have a question about error response formats.

When invoking a workflow via HTTP POST, I’m seeing this on failure::
• HTTP Response: 400 Bad Request
• Content-Type: text/html; charset=utf-8
• Response Body: “Error in workflow”
However, in the Pipedream UI/dashboard, I can see the detailed error:

{"error":{"code":400,"message":"Unable to parse range: undefined!A:A","status":"INVALID_ARGUMENT"}}

Questions:

  1. Is the generic "Error in workflow" body the expected behavior for HTTP endpoints, with details only visible in the UI?
  2. Is there a supported way to return structured JSON errors to HTTP clients,
    such as:
{"success": false, "error": {"code": 400, "message": "Unable to parse range: undefined!A:A"}}

We need to surface meaningful error feedback to end users, so guidance on exposing detailed errors over HTTP would be super helpful.
Thanks!

2

I believe we may return more verbose errors if you set up the HTTP trigger to “return a custom response”