What you'll build
By the end of this guide, you'll be able to add a Record count condition to your form's advanced logic, so a rule can check how many existing submissions already match a filter before deciding what happens to a new or updated one. Instead of just accepting or rejecting a submission, your logic can classify it, Approved vs. Pending, Confirmed vs. Waitlisted, based on a live number that updates with every submission.
This is different from Formaloo's existing capacity tools. A reservation or availability limit hides or rejects a full option outright, and a max responses limit closes the whole form once it hits a number. Neither one can put a submission into a second state, because neither one can actually count anything, they just gate the door. Record count gives your logic the missing operand, a live, filtered number it can compare against.
When to use this
You're capping how many submissions can reach a certain status, like Approved or Confirmed, before the rest get held back automatically
You're selling a small number of tickets or seats and want a new request approved only while the number already approved is still under your limit
You want a logic rule to react to how many rows already exist in a different, connected form, not just the current one
You're tracking capacity by a fixed category, like a specific ticket tier or status, instead of one flat limit for the whole form
You want this to work without building and maintaining a second form just to hold overflow
Adding a Record count condition to your logic
Record count is a condition type inside your form's advanced logic. It's only available in On Submit and On Update rules, not in field logic, since it needs a full submission to evaluate against rather than a single in-progress answer.
Open your form, then click the settings icon in the panel on the right side
Click Advanced logic
Open either the On Submit or On Update tab
Next to If, open the condition type dropdown and select Record count
Choose a comparison operator (for example, is less than or equal to) and enter the number you're comparing against
💡 Want your form to show, hide, skip, or require fields based on what someone just answered? What is logic in Formaloo is the foundational guide to logic in Formaloo.
Choosing what to count
Underneath the condition, a Counting records in panel expands so you can tell Formaloo exactly which rows to count.
Count records in: a dropdown where you pick the target form. It defaults to the current form, the primary use case, since most capacity checks are against the form's own submissions, but you can also search for and select any other form you're allowed to use in this form's logic, as long as it's in the same workspace.
Which records: a toggle between All records (a straight total) and Records matching filters (a filtered count).
Where: when you choose Records matching filters, this section holds your filter rows, each comparing a field to a fixed condition, like Status is equal to Approved. Add more filters with the + button, they combine with AND, so a row has to match every filter to count.
The field you filter on doesn't have to be one you're already using on your current form, the target form is counted using its own fields and values, whether that target is the current form or a different one entirely.
What this looks like in plain English
Put together, a Record count condition reads like one of these:
"If this form has fewer than 100 submissions..."
"If this form has fewer than 100 submissions where status is equal to Confirmed..."
"If the Contacts form has zero rows where status is equal to Active..."
The comparison is always a straightforward number check. Formaloo counts the matching rows and compares that number to your threshold, it doesn't ask an AI to interpret anything, so the same input always produces the same result.
A worked example: only approve a ticket while there's still room
Say a Cinema Ticket form sells 2 tickets for a screening, and a ticket should only be marked Approved while fewer than 2 are already Approved.
On submit: a Record count rule checks whether the count is less than or equal to 2, counting records in the Cinema Ticket form itself, filtered to Status is equal to Approved. If that's true, the rule assigns the new ticket's Status to Approved. If not, it assigns Status to Pending instead. That's the whole classification, the first 2 approved tickets get Approved, everyone after that lands in Pending automatically, with no one reviewing submissions one by one.
On update: pair the same condition with the Update record action, so that when an approved ticket's status changes away from Approved, a cancellation, Formaloo finds the oldest Pending ticket and promotes it to Approved, freeing the seat the moment it opens up instead of waiting for someone to notice.
What you now have
Your logic can now check a live, filtered count before deciding what happens to a submission, instead of only accepting or rejecting it outright. That's a real second status you control, driven by a number that's always accurate, not a flat cutoff that closes the whole form. The same condition works whether you're counting rows on the current form or a completely different one in your workspace.
What's next
Route different emails to each outcome Once Record count is setting a status like Approved or Pending, pair it with conditional email notifications so each outcome gets its own message. → How to send and receive conditional email notifications
Update a different row once your count fires Record count tells your logic how many rows match. This article covers the action you pair it with to then change a different row, like promoting a held-back submission. → How to update records across forms using logic in Formaloo
Keep track of every rule once your logic grows Between a Record count condition, an update action, and your status-based emails, a form can end up with several interacting rules. This article gives you a bird's-eye view of how they connect. → What is the logic map?
Ready-to-use templates
Don't build this from scratch, we've already put it together for you.
Event registration and ticketing system — Handles capacity limits, PDF tickets, and an admin portal out of the box. Add a Record count condition on top of it to turn its flat capacity limit into a real per-status waitlist.
Job applicant tracking workflow — Tracks applicants across hiring stages. Add a Record count condition to cap how many candidates can reach a stage like Interviewing before the rest hold at Screening.
Employee request workflow — Routes internal requests by type with status tracking. Useful if you're capping something internal, like limited training seats or equipment loans, with the same count-and-classify pattern.
Don't have a form yet? Create one in seconds with Magic Create, describe what you need and Formaloo builds the form for you.
Learn more how-tos
See the flat-limit version of capacity, if you don't need a second status This article covers Formaloo's existing reservation and submission-limit tools, the simpler option when a straightforward accept-or-reject cutoff is really all you need. → How to collect event registrations, manage capacity, and send automated confirmations
Cap the whole form instead of a filtered count This article covers Max responses, the simpler existing tool for a hard stop on total submissions rather than a filtered, per-status count. → How to limit the total number of submissions your form accepts (Max responses)
Go deeper on the advanced logic panel itself This article covers everything else the advanced logic panel can do beyond Record count, cross-field conditions, calculations, and every other action type. → How to add advanced logic to your form
Ready to build this?
🚀 Use this template Start in minutes with a pre-built version of this workflow.
💬 Get help from our concierge team Our team will help you set this up for your specific use case.
📅 Book a demo for Team/Enterprise setup See how teams use Formaloo at scale with advanced permissions and integrations.