Pipedream imposes limits on source and workflow execution, the events you send to Pipedream, and other properties. You'll receive an error if you encounter these limits. See our troubleshooting guide for more information on these specific errors.
Some of these limits apply only on the free tier. For example, Pipedream limits the daily number of credits and active workflows you can use on the free tier. On paid tiers, you can run an unlimited number of credits per day, for any amount of execution time.
Other limits apply across the free and paid tiers. Please see the details on each limit below.
These limits are subject to change at any time.
# Number of Workflows
The limit of active workflows depends on your current plan. See our pricing page (opens new window) for more details.
# Number of Event Sources
You can run an unlimited number of event sources, as long as each operates under the limits below.
# Daily Credits Limit
Free Pipedream accounts have a limit of number of free incuded credits per day. Paid plans do not have a daily credit limit. See our pricing page (opens new window) for a breakdown of Free tier limits.
You can view your credits usage in your Billing and Usage Settings (opens new window). Here you'll find your usage for the last 30 days, broken out by day, and by source / workflow.
Your included credits count is reset, daily, at 00:00 (midnight) UTC.
# Included Credits Usage Notifications
|Free tiers||You'll receive an email when you reach 100% of your daily usage.|
|Paid tiers||You'll receive an email at 80% and 100% of your included credits for your billing period.|
# HTTP Triggers
The following limits apply to HTTP triggers.
# HTTP Request Body Size
By default, the body of HTTP requests sent to a source or workflow is limited to
Your endpoint will issue a
413 Payload Too Large status code when the body of your request exceeds
Pipedream supports two different ways to bypass this limit. Both of these interfaces support uploading data up to
5TB, though you may encounter other platform limits.
- You can send large HTTP payloads by passing the
pipedream_upload_body=1query string or an
x-pd-upload-body: 1HTTP header in your HTTP request. Read more here.
- You can upload multiple large files, like images and videos, using the large file upload interface.
# QPS (Queries Per Second)
Generally the rate of HTTP requests sent to an endpoint is quantified by QPS, or queries per second. A query refers to an HTTP request.
You can send an average of 10 requests per second to your HTTP trigger. Any requests that exceed that threshold may trigger rate limiting. If you're rate limited, we'll return a
429 Too Many Requests response. If you control the application sending requests, you should retry the request with exponential backoff (opens new window) or a similar technique.
We'll also accept short bursts of traffic, as long as you remain close to an average of 10 QPS (e.g. sending a batch of 50 requests every 30 seconds should not trigger rate limiting).
This limit can be raised for Professional, Teams, and Enterprise customers. To request an increase, reach out to our Support team (opens new window) with the HTTP endpoint whose QPS you'd like to increase, with the new, desired limit.
# Email Triggers
Currently, most of the limits that apply to HTTP triggers also apply to email triggers.
The only limit that differs between email and HTTP triggers is the payload size: the total size of an email sent to a workflow - its body, headers, and attachments - is limited to
By default, workflows run with
256MB of memory. You can modify a workflow's memory in your workflow's Settings, up to
Increasing your workflow's memory gives you a proportional increase in CPU. If your workflow is limited by memory or compute, increasing your workflow's memory can reduce its overall runtime and make it more performant.
Pipedream charges credits proportional to your memory configuration. Read more here.
Your code, or a third party library, may need access to disk during the execution of your workflow or event source. You have access to
2GB of disk in the
This limit cannot be raised.
# Time per execution
Every event sent to a workflow triggers a new execution of that workflow. Workflows have a default execution limit that varies with the trigger type:
- HTTP and Email-triggered workflows default to 30 seconds per execution.
- Cron-triggered workflows default to 60 seconds per execution.
If your code exceeds your workflow-level limit, we'll throw a Timeout error and stop your workflow. Any partial logs and observability associated with code cells that ran successfully before the timeout will be attached to the event in the UI, so you can examine the state of your workflow and troubleshoot where it may have failed.
You can increase the timeout limit, up to a max value set by your plan:
|Tier||Maximum time per execution|
|Free tiers||300 seconds (5 min)|
|Paid tiers||750 seconds (12.5 min)|
Events that trigger a Timeout error will appear in red in the Inspector. You'll see the timeout error, also in red, in the cell at which the code timed out.
# Event / Execution History
The Inspector shows the execution history for a given workflow. We retain up to per workflow:
|Tier||Events retained per workflow|
|Paid tiers||View breakdown of events history per paid plan (opens new window)|
The execution details for a specific event also expires after 365 days.
# Logs, Step Exports, and other observability
The total size of
console.log() statements, step exports, and the original event data sent to the workflow cannot exceed a combined size of
6MB. If you produce logs or step exports larger than this - for example, passing around large API responses, CSVs, or other data - you may encounter a Function Payload Limit Exceeded in your workflow.
This limit cannot be raised.
# Acceptable Use
We ask that you abide by our Acceptable Use (opens new window) policy. In short this means: don't use Pipedream to break the law; don't abuse the platform; and don't use the platform to harm others.