Why monday.com's Subitem Summary Column Doesn't Work in Automations — and the Fix (2026)

Direct answer: monday.com’s subitem summary column is a mirror: a computed reference to values on the hidden subitems board. Nothing is stored on the parent item itself. That’s why automations can’t trigger on it, formula columns can’t read it, and exports often come out empty. The fix is to write the aggregate into a real parent column with a rollup app, then build your automation on that column.

What is the subitem summary column, technically?

When you right-click a subitem column header and choose Show summary on parent item, monday.com adds a summary to the parent row: a total for numbers, a distribution bar for statuses. It looks like a column value. It isn’t one.

Subitems don’t actually live on your board. They’re stored on a hidden companion board, connected to their parents through a built-in board relationship. The summary you see on the parent is a mirror column over that connection: monday.com computes the total on the fly, at display time, from values stored on the subitems board.

Nothing is ever written to the parent item. The parent has no stored value called “14” or “60% done”, just a live window onto data that lives somewhere else. That one design decision explains every limitation below.

Why can’t automations trigger on the summary?

Two consequences of the mirror design, and both matter:

1. There’s no stored value to watch. Triggers like “when column changes” fire when a stored column value on the item changes. A mirror never “changes” in that sense. It has no value of its own and gets recomputed each time something renders it.
2. The change events fire on the wrong board. When a subitem’s number is edited, that event belongs to the subitems board. Your parent board’s automation engine never receives it, so from its point of view nothing happened.

As of mid-2026, monday.com does support a small set of trigger templates on mirrored Status columns, but coverage is narrow: number, date, and timeline summaries remain outside it. If your automation needs “when the subitem total crosses X,” the native summary can’t deliver it.

Where else does the mirror wall show up?

The same root cause (a computed reference with no stored value) surfaces in three more places:

• Formula columns operate on the item’s own stored columns and can’t reliably read mirror summaries. (Formulas can’t read subitem values directly either, so there’s no formula-only workaround.)
• Exports read stored values, so the summary frequently comes out empty in Excel.
• Dashboard widgets that aggregate column values often treat the summary as blank. Some widgets handle mirrors better than others, so test yours.

What you need	Native summary (mirror)	Rollup into a real column
See the total on the parent	Yes	Yes
Trigger automations on it	No (narrow status exceptions)	Yes
Read it in a formula column	No	Yes
Export it	Often empty	Yes
Chart it in dashboards	Widget-dependent	Yes
Filter which subitems count	No	Yes (paid plans)

Hasn’t monday.com improved native rollups in 2026?

Yes. monday.com introduced multi-level boards and improved native rollup behavior during 2026, and for display purposes the native options keep getting better. If all you need is to see subitem numbers on the parent, start native; it’s free and instant. Our guide on showing subitem progress on the parent covers exactly where the native route is enough.

The durable gap is unchanged, though: native summaries still don’t produce stored values in real columns. Until they do, anything downstream of the value (automations, formulas, exports, most widgets) hits the same wall.

The fix: write the rollup into a real column

SubItems Pro computes subitem aggregates and writes them into normal parent columns, so the result behaves like a value someone typed in:

1. Add the Rollup Sync board view to your board and authorize it once.
2. Add a rule: source subitem column → function → parent target column. Example: subitem Numbers (“Est. hours”) → SUM → parent Numbers column (“Total hours”).
3. Enable auto-sync. Webhooks update the parent whenever a subitem changes; Sync now recalculates on demand. Syncs are unlimited and never consume plan actions.

Ten source column types and 25 functions are available: sums and averages, percent-done, threshold statuses, date ranges, people unions. The complete rollup guide maps them all, and summing subitem numbers to the parent walks the most common case step by step.

Example: an automation that triggers on the rolled-up total

Say each subitem carries estimated hours and the project is budgeted at 40. With the SUM rule above writing into “Total hours”:

1. Open Automate on the board and create a custom automation.
2. Trigger: when Total hours changes, add a condition on the number, for example only if it’s greater than 40. (Exact recipe wording varies; as of mid-2026 the custom automation builder supports Numbers columns in triggers and number conditions.)
3. Action: notify the project lead, or set a “Budget” status to Over.

That automation is impossible against the native summary and completely ordinary against a real column. That difference is the entire reason to bother with a rollup. The same pattern works for progress percentages driving a parent status; see setting parent status from subitem statuses.

The free plan includes one rollup rule on one board, so you can confirm the automation fires on your own data before paying anything. Setup details are in the user guide.