Will my existing automations stop working when the new builder rolls out in March 2026?

No, existing automations will continue using the current automation builder with no impact. Only new automations default to the new builder experience.

Why can't I see Community Cookbook automations in the new builder's action dropdown?

Third-party marketplace app automations don't appear in the new builder when creating from scratch. You must create automations directly from Community Cookbook's templates instead.

What happens to marketplace app automations after the April 30, 2026 developer deadline?

App developers must migrate their legacy automation features by this date. Community Cookbook is actively migrating to ensure continued compatibility.

Can I save automations as templates in the new builder?

No, saving automations as templates or using existing templates isn't supported in the initial release of the new builder.

How do Smart condition blocks work compared to regular automation conditions?

Smart condition blocks let you describe conditions in plain English instead of manually configuring logic. The AI interprets your description and creates the appropriate condition structure.

Is there a way to fix the Notify block issue where dynamic values show the previous status instead of current?

This is a documented bug in the new builder. The workaround is to use the legacy builder for notification automations that rely on dynamic status values until this is resolved.

The New Monday.com Automation Builder (2026): What Changed, What Broke, What You Need to Know

Monday.com's new automation builder is rolling out to all users in March 2026, bringing AI-powered features and enhanced capabilities — but also significant limitations that affect third-party marketplace apps and power users. Here's everything you need to know about what changed, what broke, and how it impacts your workflows.

What Is the New Monday.com Automation Builder?

The new automation builder represents Monday.com's biggest infrastructure change to automations since the platform launched. Built on a workflows-based foundation that unifies automations, workflows, and future automation experiences, it's currently in A/B testing with 5% of users who create automations from scratch.

The rollout began January 7, 2026, with full deployment planned for March 2026 if testing proves successful. Unlike previous updates, this isn't just a UI refresh — it's a complete rebuild of how Monday.com handles automation logic.

The new builder promises faster performance, AI-powered features, and more intuitive automation creation. However, it also introduces significant limitations that particularly affect users of marketplace automation apps like Community Cookbook.

What Changed: New Features That Actually Matter

AI-Powered Automation Creation

The most visible change is AI integration. The new builder includes two AI features:

Smart Condition Blocks: Instead of manually configuring condition logic, you can describe what you want in plain English. For example, "when the budget is over $10,000 and the status is not done" becomes a single smart condition block.

Plain-Text Automation Generation: You can now describe an entire automation workflow in natural language, and the builder will generate the complete automation structure. This addresses one of the biggest pain points in automation creation — knowing where to start.

Enhanced Date Automation Capabilities

Date-based automations received a major upgrade. The new builder supports:

Setting any date, not just specific calendar dates
Referencing other date columns as the trigger point
Multi-step date logic (adding or subtracting days from referenced dates)

This is particularly powerful for project management workflows where deadline calculations need to reference multiple date columns.

Unified Items and Subitems Support

Perhaps the most practical improvement: all triggers and actions now support both items and subitems without requiring separate automation setups. This eliminates the frustrating workflow where you'd create an automation for items, then realize you need a completely separate version for subitems.

Related automations like the All Subitems Reach a Status Trigger become even more valuable because they handle complex parent-subitem relationships that the new builder still can't address natively.

Dynamic Data Across All Pickers

The new builder makes dynamic data from triggers available across all pickers throughout the automation. This means if your trigger captures a person's name, you can use that person data in any subsequent action, not just in specific supported fields.

What Broke: Critical Limitations You Need to Know

Third-Party Marketplace Apps Won't Appear

The biggest limitation affects marketplace automation apps directly: third-party automation blocks won't appear in the action dropdown when creating new automations. This includes all Community Cookbook recipes like the OR Status Trigger and Formula Column Threshold Trigger.

Workaround: You must create automations directly from the app's templates rather than starting from the main automation builder. This creates a discovery problem — users building automations from scratch won't see these options.

Template Saving and Reuse Disabled

You cannot save automations as templates or use existing templates in the new builder. For teams that rely on standardized automation templates across boards or projects, this is a significant workflow disruption.

File Upload Limitations

The new builder cannot upload files directly from your computer or add file links using dynamic mapping. If your workflows depend on automated file handling, you'll need to use the legacy builder or find alternative approaches.

Limited Editing Capabilities

Editing automations is restricted in the new experience. The exact limitations aren't fully documented, but early beta users report difficulty making changes to existing automations once created.

The Notify Block Dynamic Value Bug

There's a documented issue with the Notify block when using dynamic values. If a status changes from "Stuck" to "Done" and triggers a notification, the notification will reference "Stuck" (the previous status) rather than "Done" (the current status). This breaks many common notification workflows.

Timeline: When This Actually Affects You

January 7, 2026: A/B test launched for 5% of users creating automations from scratch February 18, 2026: Official documentation published and support articles updated March 2026: Full rollout planned (pending successful A/B test results) April 30, 2026: Critical deadline for app developers to migrate legacy automation features

If you're in the 5% A/B test group, you're already experiencing these changes. The March rollout will affect all Monday.com users creating new automations.

Will Your Existing Automations Break?

Short answer: No. Existing automations will continue using the current automation builder with no functional changes unless you specifically choose to rebuild them in the new system.

However, there are important caveats:

Marketplace app developers must migrate legacy features by April 30, 2026, or their automations may stop working
While you can continue editing existing automations with the current builder, the migration path to the new builder isn't clearly defined
New team members or users creating fresh automations will default to the new builder and won't see third-party options

Why This Makes Community Cookbook More Important

The new builder's limitations create gaps that Community Cookbook's custom automation blocks are uniquely positioned to fill. While Monday.com focuses on AI-powered simplicity, power users still need:

OR conditions for status triggers (not available in native automations)
Formula column monitoring (still unsupported natively)
Complex subitem workflows that go beyond basic status checking
Template-like automation patterns for repeated use

The infrastructure changes also highlight the key insight from our guide on native vs. custom automations: native features optimize for common use cases, while custom blocks solve edge cases and advanced workflows.

As Monday.com streamlines the automation building experience, teams with sophisticated requirements will increasingly need purpose-built solutions that complement rather than compete with the native builder.

What You Should Do Now

If you're not in the A/B test: Continue using current workflows. Plan for the March transition by auditing which automations rely on marketplace apps and ensuring you have direct access to those apps' template libraries.

If you're in the A/B test: Test the new AI features with simple automations, but continue using the legacy builder for complex workflows involving third-party apps until the migration path becomes clearer.

For teams using Community Cookbook: The recipes will continue working through the legacy builder path. Access automations directly through Community Cookbook's interface rather than starting from Monday.com's main automation builder.

The new automation builder represents Monday.com's vision for making automation accessible to all users through AI assistance. However, the current limitations mean that power users and teams with sophisticated workflows will need a hybrid approach — leveraging both the new builder's AI capabilities and specialized tools like Community Cookbook for advanced automation requirements.