Keep downstream work aligned across multi-level boards.
Multi-Level Board Dependencies adds custom monday.com automation blocks that react to Status changes across item hierarchies, find dependent items, and update Status, text, numbers, or AI-generated summaries.
Respond to configured Status changes on main items and subitems.
Update items that depend on the actual triggering item.
Generate per-item text using current fields, recent Updates, and activity history.
Purpose-built automation blocks
Multi-level Status trigger
Detect a configured Status transition at the hierarchy level where it actually occurs and pass that item into the workflow.
Dependent Status update
Find items linked through a selected Dependency column and apply a configured Status value.
Dependent text update
Write fixed values to Text, Long Text, or Numbers columns on dependent items.
AI-generated text
Use monday AI to generate a separate result for each dependent item from your instructions and relevant item context.
Updates + activity context
The AI action can use recent Updates/comments and item-specific activity history from the triggering item when building summaries.
Native usage metering
Monthly plan usage is tracked through monday's Marketplace operation counter. The App does not keep a 31-day event history.
Simple operation-based plans
One operation means one dependent item selected for processing by a Multi-Level Board Dependencies action.
| Plan | Operations / month | Monthly | Annual | AI action |
|---|---|---|---|---|
| Free | 30 | $0 | $0 | Included |
| Starter | 400 | $3/mo | $18/yr | Included |
| Standard | 1,000 | $6/mo | $36/yr | Included |
| Professional | 2,000 | $12/mo | $72/yr | Included |
| Unlimited | Unlimited | $24/mo | $144/yr | Included |
Annual pricing is 50% below paying the monthly rate for twelve months. Final billing, renewal, taxes, and checkout are handled through monday.com's Marketplace monetization flow.
Built on monday's platform
The App's backend runs on monday Code. Limited technical records such as OAuth credentials and active trigger registrations are stored in monday Code SecureStorage. The app does not use an external customer-data database.
Signed requests, bounded inputs
Runtime requests are authenticated with monday-signed tokens, secrets stay out of source control, dynamic inputs are validated, and customer content is intentionally minimized in diagnostic logs.