The idea is:
Introduce execution quota management to allow instance admins to allocate and enforce execution limits at the project and workflow level.
This would include:
- Per-project quotas: Allocate a monthly execution budget to each n8n project (e.g., “R&D” gets 5,000/month, “Finance” gets 3,000/month)
- Per-workflow quotas: Set a maximum number of executions per workflow over a given period (e.g., max 500/month or max 10/hour)
- Admin dashboard: View execution consumption broken down by project and workflow to identify top consumers
- Configurable actions when quota is reached: Pause the workflow, send a notification, or both
My use case:
We run a self-hosted n8n instance shared across multiple teams (R&D, Product, Finance, Legal, etc…). Depending on the license plan, we have a finite number of executions per month.
Today there is no way to prevent a single misconfigured workflow from consuming the entire monthly quota. A schedule trigger set too aggressively or a webhook receiving unexpected traffic can burn through thousands of executions in hours, impacting all other teams.
We need to:
- Control costs - prevent unexpected overages that affect billing or force an unplanned license upgrade
- Protect against runaway workflows - a single workflow shouldn’t be able to exhaust the instance quota
- Ensure fair sharing across teams - allocate execution budgets per project so each team has a guaranteed allocation
I think it would be beneficial to add this because:
- Multi-team instances are common - as n8n adoption grows within organizations, shared instances become the norm. Without quotas, there’s no governance
- No workaround exists - maintainers confirmed there is no built-in way to limit executions (How to limit number of executions per workflow). Building custom rate limiting per workflow is fragile and doesn’t solve the project-level allocation problem
- Execution limits already exist at the plan level - the infrastructure for counting executions is already there. Extending it to project/workflow granularity is a natural evolution
- Other platforms offer this - quota management is a standard feature in enterprise automation platforms
Any resources to support this?
- How to limit number of executions per workflow - confirmed not possible
- Workflow Limitation per user [Self hosted] - closed unresolved
- Workflows executions monthly limit - users asking about limits
- Clarification on Execution Limits: Is it per execution or per node?
Are you willing to work on this?
Yes, I’m willing to contribute code to implement this feature if it can speed up the implementation. Happy to submit a PR once the approach is validated by the maintainers. 