Pipedream 512KB body limit and Sume run webhook payloads

A Sume run webhook can be larger than Pipedream's default HTTP trigger body limit, so a full payload between 512KB and 1 MiB may not fit. Sume sends payload: null only above 1 MiB, and Pipedream's page limits trigger bodies to 512KB by default.

Sume facts are from the Run webhooks docs; the Pipedream limits were read 2026-09-30.

What does Pipedream say about the limit?

By default the body of HTTP requests sent to a source or workflow is limited to 512KB. Pipedream documents a bypass with the pipedream_upload_body=1 query string or an x-pd-upload-body: 1 header, and an average of 10 requests per second to an HTTP trigger.

Can Sume send the bypass header or query?

The Sume docs do not document custom headers on delivery, so do not count on x-pd-upload-body. They also do not say whether a query string in webhook_url is kept, so treat the query bypass as untested for a Sume delivery before you rely on it.

What is the safer design?

Receive the Sume webhook in a relay that verifies the signature, then forward event, request_id and outcome to Pipedream. The workflow fetches the full result from result_url with your API key, so its trigger body stays tiny whatever the run produced.

How do I dedupe in the workflow?

Use request_id, which equals the run_id for run events and is stable across retries. If the relay's forward to Pipedream fails, answer non-2xx: Sume retries up to 10 attempts on any non-2xx.