The Max Submissions action prevents a Bricks Form from being submitted once a configured counter reaches (or exceeds) a defined limit. It is useful for capping sign-ups, limiting contest entries, or closing registrations when a quota is met.
Settings
After adding a Form element in Bricks, open Actions and select Max Submissions. A dedicated Max Submissions group is displayed with the following controls:
Counter
Type: Select
Purpose: Choose the counter whose current value is checked against your limit.
Notes:
If no counters exist, the panel provides a helper link to create one under Dynamic Toolbox → Counters.
The action is ignored unless a valid counter is selected.
Max submissions
Type: Number
Default:
1Minimum:
1Behavior: Submission is allowed while
current counter value < limit. When the counter value is greater than or equal to the limit, the submission is blocked.
Error message
Type: Text
Default placeholder: “Maximum number of submissions reached.”
Dynamic data: Supported. You can use Bricks dynamic tags; the message is rendered at runtime.
Behavior: When the limit is reached, this message is returned as a form validation error and the submission is not processed.
Compatibility with Other Features
Works in tandem with
Counters: Reads the current value of the chosen counter to enforce the limit.
Counter Action for Bricks Form: Commonly used together. The Max Submissions action blocks the form before actions run, so when the limit is reached the Counter action will not increment.
Ordering and execution model
Validation runs via the Bricks
bricks/form/validatefilter. This happens before any form actions execute.Therefore, when the limit is hit:
The submission is rejected with your Error message.
No subsequent actions (emails, webhooks, Counter increment, etc.) run.
Usage Summary
Create or select a counter
Go to Dynamic Toolbox → Counters and ensure you have a counter tracking the number of accepted submissions.Configure the Bricks Form
Add a Form element.
In Actions, enable Max Submissions.
In the Max Submissions group:
Select the Counter to check.
Set Max submissions to your desired cap (e.g.,
100).Optionally customize the Error message (dynamic tags allowed).
(Optional) Combine with other actions
You can still add actions like Counter, Email, or Webhook. They will execute only while the counter is below the limit.Test the flow
Submit until the counter reaches the limit. Subsequent attempts should be blocked with your error message.
Tips & Best Practices
Choose a meaningful counter: Use a counter that reflects accepted submissions, not just attempts, to accurately model your quota.
Custom error text: Include clear next steps in the error message (e.g., link to a waitlist form).
Pairing with Counter: If you want the limit to represent “total successful submissions,” keep the Counter action in the same form so it increments only when validation passes.