New in the workflow tab: disable actions and generate workflows with AI

Hi everyone,

I’m Lindsay, a product manager at Bubble, here with two updates to the workflow tab that give you more control over how you build and test your workflows.

1. Disable individual workflow actions

It’s been possible to disable entire workflows for a while, but sometimes you just want to skip one step while you test or iterate on the rest.

Now you can. There’s a new Execution options section in the workflow action tab that lets you toggle specific actions on or off while the rest of the workflow runs as normal. The action’s configuration, conditionals, and position in the workflow are all preserved, you’re just telling Bubble to skip that step for now.

When to use it

This is especially useful for debugging. Say you’re testing a workflow but don’t want to trigger a confirmation message every time — just disable that action, test everything else, and re-enable it when you’re ready. You can also use it to isolate issues by disabling actions one at a time, test workflow behavior with and without a specific step, or review risky actions like data modifications, emails, or deletions, before letting them run.

How to use it

Open any workflow action and look for the new Execution options section.

You’ll see two toggles:

  • [NEW] Disable Action: Skips this action when the workflow runs. All settings stay intact until you re-enable it.
  • Add a Breakpoint in Debug Mode: Pauses workflow execution at this action when debugging, so you can inspect your app’s state at that point without stepping through every prior step.

2. Generate workflows with AI

Workflows are one of Bubble’s most powerful features, but they also have one of the steepest learning curves. Even if you know exactly what you want to happen, translating that into a properly configured workflow takes familiarity with events, actions, dynamic expressions, and data types.

The new Generate with AI option lets you skip that process. Describe what you want in plain language and the Agent will build a fully configured workflow for you.

For example, you could type something like:

  • “When the signup button is clicked, create an account and send the user to the dashboard”
  • “Design a workflow for RSVPing to an event. A guest should click RSVP, save their response, notify the host, and see a confirmation message.”
  • “Build a workflow for posting in a community forum. Users should write a post, choose a topic, publish it, and show the new post in the feed.”

The Agent translates your description into a working workflow that you can review, edit, and refine, either by continuing to chat with the Agent or by switching to the visual editor.

It’s available on any app with access to the Agent, and it’s useful whether you’re a new user still learning Bubble’s workflow system or an experienced builder who’d rather skip the manual setup on complex workflows.

How to access it:

  • Open the workflow tab
  • Click New in the upper left corner
  • Select Generate with AI

Both of these updates are about giving you more flexibility in how you work with workflows, whether that means toggling actions on and off as you test, or letting the Agent handle the initial build so you can focus on the details. Give them a try and let us know what you think!

— Lindsay

Yes! Disable a single action. So glad this was done. What a nice quality of life improvement. Thanks!

Yeah, I noticed that and it is a good QoL.

No more Only When Arbitrary text “no” is “yes” or the use of a specific Option Set for these expressions to disable actions and make them traceable.

Great updates! Thank you for these QoL like the disable single action.

Would it be possible to look into folders insider folders for workflows or folders for elements

Having only 1 folder level deep for workflows is ok until you have a sizeable app or especially on the backend workflow tab. Would be great if I could make a folder “App Logs” and then inside that make more folders for different sections or data types.

Edit: Also putting all the functionality on the context menu that we have on the left nav would be so helpful for workflows.

It can be frustrating to be focused on a workflow but have to scroll through folders just to find the one to right click to disable, delete, copy, put in a folder etc.

For generating workflows with AI, is this only available on apps that were initially generated using AI? The Agent still isn’t available for existing apps, right?

Lindsay, it will sound highly experimental but you guys should try to make passing data from a reusable to a page with AI, I don’t know, a beginner user “writes pass this animal or animals to the page I couldn’t figure out they told me to use reusables now I can’t pass it, what is parameters?”

and the AI workflow downloads toolbox plugin, puts the js2bubble element to the page and the script to the workflow

Also, is there any reason Backend Workflows cannot be disabled like frontend ones? It appears we can disable individual actions in backend workflows but cant disable the entire workflow.

You can do! Right click the workflow in the workflow list and disable there. It’s weird that it’s not on the workflow event node (in the workflow builder) though.

For backend workflows, are you sure? It’s not there for me..

Oh… indeed you are right, it’s not available on backend!

Yeah haha, normally not a big deal since you and disable the trigger on the front end but for backend data triggers there is no way to disable them! Just have to add a condition or make the first step terminate which is a pain.

Hey! Yes, at the moment it’s only available for apps that have access to the agent.

Amazing additions @lindsay.esterman! Could we also get the ability to “disable on test?” There are certain workflows (e.g., Do every X seconds) that always run in the debugger even if you put a condition on them that evaluates to false. This makes it impossible to use the debugger unless you manually disable the workflows. But then you need to remember to re-enable them before you go Live. It’s really really annoying and also potentially could lead to bugs or security issues because it requires you to remember to re-enable it every time. Keep up the great work!

Hey @lindsay.esterman I’ve already mentioned that this new implementation for disabling actions in workflows was very welcome.

However, as already mentioned above, it would be interesting to have native ways (and not rely on workarounds) to disable events and actions in backend workflows.

Also, it would be useful to have a way to track all currently disabled events and actions. I thought of Buildprint, but, as you know, it would be useful for all users if this were a native feature.

@lindsay.esterman Thanks for this great update!

Right now, there is no way to tell at a glance if there are actions in a WF that are disabled. It would be really helpful to have some sort of icon/text/indicator, like disabled workflows, that indicates that an action is disabled.