Understanding value of Next-gen Actions

Betty Blocks offers two versions of Actions - Next-gen Actions and the older Classic Actions. As we continue to modernize and evolve our platform, Next-gen Actions represent the future of building application logic in a faster, more modular, and scalable way. This document outlines the core value of Next-gen Actions, highlights the key differences compared to Classic and explains when and why you should start using them.

Next-gen Actions

Next-gen Actions are designed to be flexible, reusable, and future scalable. They allow you to define complex application logic through a clear visual flow, combining:

Built-in steps for common operations
Reusable steps from the Block Store
Custom steps you define yourself

Learn more in the following articles:

Next-gen vs Classic

	Next-gen Actions	Classic Actions
Current status	Actively developed, future-proof	Outdated, legacy
Customization	Build custom logic with your own steps	❌ Not supported
Block Store integration	Growing library of steps	❌ Not supported
User experience	Visual and intuitive interface	Outdated interface
Condition step	Flexible, multiple if else's	Limited, 1 if else
Scheduled actions	Supported	Supported
Debug logging	Supported with intuitive interface	Outdated interface
Call action via endpoint	Supported	Supported
Subaction	Supported	Supported
Long-running (background) actions	❌ Not yet supported (expected in Q4 2025)	Supported
Expressions	Via expressions step	Via variables
PDF creation	Available in Block Store (verified block, fully supported by Betty Blocks)	Supported
Forms in Pages	Compatible with the newest default component set, including automatic form-action synchronization	Only compatible with deprecated component set

Why use Next-gen Actions?

Modular
Next-gen Actions encourage reuse through Block Store and custom steps. This means you’re never stuck and you don’t have to rebuild the same logic repeatedly—just reuse and adapt
Future proof
Next-gen is where all innovation is happening. New features, optimizations, and integrations are being built on this foundation
Maintainability
Clearer flow, better naming, and modular logic mean teams can more easily understand and maintain complex logic

When should you still use Classic Actions?

Although Next-gen Actions are the future, there are still a few scenarios where Classic Actions may be the better fit for now:

You need long-running background processes
Your logic depends on legacy integrations not yet supported in Next-gen

We recommend using Next-gen for all new logic unless you need long running actions or it’s depending on legacy integrations.

Migrating from Classic to Next-gen

If you're currently using Classic Actions, consider starting a phased migration strategy:

Use Next-gen for all new logic
Refactor smaller Classic flows to Next-gen equivalents
Monitor the Betty Blocks roadmap for feature parity updates

Start using Block Store steps

Explore and use pre-built logic steps from the Block Store to accelerate your builds. You can also publish your own for team-wide reuse.

Next-gen Actions mark a major leap forward in building application logic with Betty Blocks. They make it easier, faster, and more reliable to create powerful applications. While some advanced features are still under development, the benefits in flexibility and maintainability make Next-gen the best choice for most new builds today.