Google Drive (Developer) – Custom API Request (Beta) returns HTTP 500 only during live execution

Status: Closed · Asked by Yazan B on · 0 views

Yazan B — Question ·

I'm experiencing inconsistent behavior with Google Drive (Developer) → Custom API Request (Beta).


Save & Send Test Request inside the step works correctly.

It returns the expected response

When the workflow executes normally from the trigger, the Data In shows the exact same URL:

But the response is always:

HTTP Status Code: 500

The application processed the request but returned a blank response.

Things we've already verified

  • The URL in Data In is correct.
  • The folder exists.
  • Hardcoded value works in the step tester.
  • Dynamic value resolves to the exact same text.
  • Same Google Drive connection.
  • Same endpoint.

    Why would Save & Send Test Request succeed, but the live workflow execution return HTTP 500

    The application processed the request but returned a blank response.

Pabbly Support — Reply ·

Hello,

Could you please share the Workflow URL where you have this concern?

Thanks & Regards,
Arshil Ahmad
🌐 Pabbly.com
Pabbly Support — Reply ·

Thank you for sharing the Workflow URL and Task History ID. We have forwarded your concern to our technical team. We will get back to you as soon as we receive any updates from their end.

Thanks & Regards,
Arshil Ahmad
🌐 Pabbly.com
Pabbly Support — Reply ·

Hi Yazan,

Thank you for your patience while our technical team looks into this issue.

To help us investigate and debug the HTTP 500 error effectively on live execution, could you please grant us your consent to test and make temporary necessary adjustments directly within your workflow?

Once we have your permission, we will proceed with the troubleshooting and update you as soon as possible.

Thanks & Regards,
Hrishabh
Customer Support Associate
🌐 Pabbly.com
👉 Rate your support

Yazan Bassam — Reply ·
Yes you have full consent 


Yazan Bassam
Chief Executive Officer

Default

ADWEEK Award

instagramlinkedintwitterfacebook

Agency of the Year

The content of this electronic communication is intended solely for the use of the individual or entity to whom it is addressed and any others who are specifically authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or otherwise placing reliance on the contents of this information is prohibited and may be unlawful in certain legal jurisdictions. If you have received this communication in error please notify the sender immediately by responding to this email and then delete it from your system.


On Fri, Jul 31, 2026 at 15:08 Pabbly Support <support@pabbly.com> wrote:

Hi Yazan,

Thank you for your patience while our technical team looks into this issue.

To help us investigate and debug the HTTP 500 error effectively on live execution, could you please grant us your consent to test and make temporary necessary adjustments directly within your workflow?

Once we have your permission, we will proceed with the troubleshooting and update you as soon as possible.

Thanks & Regards,
Hrishabh
Customer Support Associate
🌐 Pabbly.com
👉 Rate your support
Pabbly Support — Reply ·

Our technical team has made some changes to the backend. You should no longer encounter this issue during automation.

Thanks & Regards,
Arshil Ahmad
🌐 Pabbly.com
Yazan Bassam — Reply ·
Please note it has been resolved, however the same issue apparently is happening with JSON Pabbly

even if Data out is empty it should continue as we have a router with status "error" and that is expected 
 
image.png
in the same workflow 

Hello Yazan B,

This email is to notify you that for the workflow "Clickup - Creating Google Drive Folders" , a recent task was not executed due to following error -

Task History ID: IjU3NjYwNTZjMDYzMDA0M2M1MjZjNTUzNTUxMzU1MTY0NTQzMjBmMzAi_pc
Step Name: JSON for Year > Extract JSON Data
Connection Name: No Auth Connection
Task Error Detail:

{
    "status": "error",
    "message": "Empty data"
Pabbly Support — Reply ·

Thank you for confirming that the previous issue has been resolved.

For this issue, we suggest enabling the Ignore Error feature in the JSON Extractor (Pabbly) action step. This will ensure that the subsequent steps are executed even if the JSON Extractor action encounters an error.
image.png

Thanks & Regards,
Arshil Ahmad
🌐 Pabbly.com
Yazan Bassam — Reply ·
Thanks for your support.


Yazan Bassam
Chief Executive Officer

Default

ADWEEK Award

instagramlinkedintwitterfacebook

Agency of the Year

The content of this electronic communication is intended solely for the use of the individual or entity to whom it is addressed and any others who are specifically authorized to receive it. It may contain confidential or legally privileged information. If you are not the intended recipient you are hereby notified that any disclosure, copying, distribution or otherwise placing reliance on the contents of this information is prohibited and may be unlawful in certain legal jurisdictions. If you have received this communication in error please notify the sender immediately by responding to this email and then delete it from your system.


On Fri, Jul 31, 2026 at 22:19 Pabbly Support <support@pabbly.com> wrote:

Thank you for confirming that the previous issue has been resolved.

For this issue, we suggest enabling the Ignore Error feature in the JSON Extractor (Pabbly) action step. This will ensure that the subsequent steps are executed even if the JSON Extractor action encounters an error.
image.png

Thanks & Regards,
Arshil Ahmad
🌐 Pabbly.com
Pabbly Support — Reply ·

Glad we were able to help.

Thanks & Regards,
Arshil Ahmad
🌐 Pabbly.com

Back to all forum threads · Log in to reply