How to Resolve a 413 Error in HTTP Request Triggered Workflow?

Help
1

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

Good morning. I have a workflow that triggers another workflow with an http request. They’ve been running fine for a few months, but today started throwing a 413 error when making the request, which indicates the request was too big. Is there something to configure on either workflows’ end to get around that or do I just need a different way to trigger the flow?

2

Hi John, this might be helpful for you: Triggers

By default HTTP requests are limited to 512kb.

But you can pass the pipedream_upload_body: 1 parameter as a header (or as a query param) to have your HTTP request body uploaded to an S3 bucket instead.

3

Hi Pierce. That worked perfectly! Thanks!

4

Awesome, great to hear :slightly_smiling_face: