Incrementing & Decrementing Numbers in Automations: Auto-Update Counters, Scores & Progress Tracking

Monday.com's increment and decrement automation actions let you automatically add or subtract values from number columns when specific triggers fire. Whether you're building tally counters, tracking scores, or counting status changes, these actions provide a foundation for automated counting systems — though with some important limitations you need to know about.

The native increment/decrement actions work with whole numbers only and can't trigger based on threshold values, leaving gaps that require creative workarounds or custom solutions for decimal tracking and conditional logic.

What Are Increment & Decrement Automation Actions?

Monday.com's increment and decrement actions were introduced in May 2022 as native automation building blocks. They let you:

• Increment: Add a specified value to a number column
• Decrement: Subtract a specified value from a number column
• Trigger on any event: Status changes, date arrivals, button clicks, form submissions

These actions work with any trigger in monday.com's automation system and count toward your monthly automation action quota like all other automation actions.

The most common use case is button-triggered tally counters — click a button to add 1 to a running total. But you can also increment counters when items reach specific statuses, dates arrive, or any other automation trigger fires.

Native Increment/Decrement Capabilities

Monday.com's built-in increment and decrement actions handle straightforward counting scenarios effectively:

Button-Triggered Counters: Create a button column that adds or subtracts values when clicked. Perfect for attendance tracking, vote counting, or manual score adjustments.

Status Change Counting: Track how many times items reach specific statuses. Set up "When status changes to 'Complete', increment counter by 1" to count finished tasks automatically.

Date-Based Incrementing: Increment counters when due dates arrive or specific calendar events occur. Useful for tracking overdue items or recurring event participation.

Form Submission Tallies: Count form submissions, survey responses, or customer requests by incrementing when new items are created from forms.

Each increment or decrement action consumes one automation action from your monthly quota, making them efficient for simple counting compared to complex workaround solutions.

Critical Limitations You Need to Know

While native increment/decrement actions cover basic counting needs, they have significant limitations that force workarounds in many scenarios:

Only Whole Numbers Supported

The biggest limitation is decimal restriction. You cannot increment by 0.5, 1.2, or any fractional value. This blocks use cases like:

• Rating systems with half-star increments
• Financial calculations requiring cents
• Percentage tracking with decimal precision
• Score systems using fractional points

No Threshold-Based Triggers

You cannot trigger automations when number columns cross specific values. Monday.com lacks native support for conditions like "when Number Column > 60" or "when Column A >= Column B". This prevents:

• Inventory alerts when stock falls below reorder points
• Budget warnings when spending exceeds thresholds
• Performance triggers when scores reach target levels

For threshold logic, you must use formula columns with status column workarounds, as covered in our guide on dynamic automation logic using formula columns.

Progress Tracking Column Limitations

The Progress Tracking column cannot trigger automations, even when reaching 100% completion. You cannot automate actions based on progress percentages, limiting project completion workflows.

Cross-Board Increment Challenges

Incrementing counters across connected boards requires custom solutions. Native actions don't sync number changes bidirectionally, creating gaps in multi-board tracking scenarios.

Real-World Use Cases & Implementation

Here are practical scenarios where increment/decrement automations excel and where they fall short:

Tally Counters & Manual Tracking

Use Case: Event attendance, inventory counts, or voting systems where team members manually update numbers.

Setup: Create a button column with "When button is clicked, increment [Counter] by 1" automation. Each click adds to the running total.

Action Cost: One action per button click — efficient for manual updates.

Status Change Tracking

Use Case: Count how many times items reach specific workflow stages for process analysis.

Setup: "When status changes to 'Review Complete', increment [Review Counter] by 1" tracks completed reviews automatically.

Limitation: Cannot track cumulative totals across multiple items without additional setup.

Score & Points Systems

Use Case: Customer satisfaction scores, employee performance points, or gamification systems.

Setup: Multiple automations increment the same score column based on different achievements. "Complete task on time" adds 5 points, "Customer feedback > 4 stars" adds 3 points.

Limitation: Whole numbers only — cannot award 2.5 points or fractional scores.

Cross-Board Counting Limitations

Challenge: Incrementing a master counter when items are created across multiple project boards.

Native Gap: Monday.com cannot directly sync increment actions between boards.

Solution: Community Cookbook's cross-board sync actions can push counter updates to connected boards, enabling multi-board tallying without API complexity.

When Native Actions Aren't Enough

Several scenarios require enhanced solutions beyond monday.com's native capabilities:

Decimal Precision Requirements

For financial tracking, ratings with half-points, or percentage-based scoring, Community Cookbook's enhanced increment actions support decimal values. Instead of whole-number limitations, you can increment by 0.25, 1.5, or any fractional value.

Threshold-Based Incrementing

When you need conditional incrementing based on other column values, Community Cookbook's Number vs Column Trigger enables "increment only when Value A exceeds Value B" logic that native automations cannot handle.

Progress-Triggered Actions

Since Progress Tracking columns cannot trigger native automations, enhanced triggers let you increment counters when progress reaches specific percentages — like adding bonus points when project completion hits 75%.

Complex Cumulative Calculations

Building running totals that update automatically when new items are added requires sophisticated logic beyond simple increment actions. Enhanced actions can calculate cumulative sums, moving averages, and conditional totals that adapt to changing data.

Action Quota & Cost Considerations

Increment and decrement actions count toward your monthly automation action limits:

• Standard Plan: 250 actions/month
• Pro Plan: 25,000 actions/month
• Enterprise: Custom limits

For high-volume counting (hundreds of increments daily), monitor your action consumption carefully. Each button click, status change, or trigger event that fires an increment automation consumes one action.

Consider consolidation strategies for efficiency. Instead of creating separate counters for each team member's individual scores, use group-level counters that increment less frequently but provide equivalent tracking insight.

Our guide on automation rate limits and action quotas provides detailed calculation methods for estimating your counting automation costs.

Best Practices for Counter Automations

Start Simple: Begin with basic button-triggered counters before building complex multi-trigger scoring systems. Test action consumption patterns with small-scale implementations.

Use Clear Column Names: Name counter columns descriptively — "Tasks Completed This Month" instead of "Counter 1" — for team clarity and maintenance ease.

Consider Reset Mechanisms: Build monthly or quarterly counter resets using automation scheduling or manual processes. Continuously growing numbers become harder to interpret over time.

Document Counter Logic: Maintain clear documentation of what increments each counter and when. Complex scoring systems with multiple triggers require team understanding for effective use.

Plan for Scale: If your counting needs exceed native whole-number limitations or require cross-board synchronization, investigate Community Cookbook's enhanced actions before building complex workarounds.

Increment and decrement automations provide solid foundations for automated counting in monday.com, handling most basic tallying and scoring scenarios efficiently. When you hit the decimal, threshold, or cross-board synchronization limitations, enhanced actions fill those gaps without forcing complex API integrations or manual workarounds.

Frequently Asked Questions

Can I create a tally counter that adds 1 to a number column when a button is clicked?+

Why can't I use decimal values like 0.5 or 1.2 in increment automations?+

How do I track how many times a status has changed to a specific value?+

Can I trigger automations when a number column reaches a specific threshold?+

How do I increment a counter across multiple boards when items are connected?+

Can I automate actions when Progress Tracking reaches 100% completion?+