Better Testing in the Editor

Run your flow up to a step you choose, keep step outputs out of the way, and follow each run component by component.

Testing the middle of an automation is harder than it should be. If you only want to check a few steps, you end up running the whole flow, including the final email or record update at the end. We’re working on a way to run the flow up to a component you choose and stop there, so you can try the middle steps without taking the final action.

You’ll also be able to hide a component’s output from later steps and from the run log. That keeps intermediate results from filling up the log, and stops extra data from flowing through the rest of the automation.

On top of that, runs will show which component they are on. You’ll see which components passed and where a run stopped, so finding the problem takes less guessing.