Encountering a 413 error (payload too large) uploading JSON payloads

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

Steve Juth : Hi Everyone, I’m sending JSON payloads from Phantombuster to Pipedream, resulting in occasional 413 errors (payload too big) on Pipedream’s end. Is this something that can be fixed by increasing my Workflow’s memory (under Settings), or is there some other way to work around this issue (other than sending smaller, more frequent payloads)?

Dylan Sather (Pipedream) : Hi , could you add ?pipedream_upload_body=1 to the end of the Pipedream URL? That’ll allow you to upload larger HTTP payloads that you can download and parse in your workflow. See Triggers

Dylan Sather (Pipedream) : Let me know if that works!

Steve Juth : Thanks, Dylan! I’ll give that a try soon. Right now I have to work on analyzing a large batch of data that I was able to download as a .csv file.