New Run Settings in Agent Hub's workflows builder
Monday, November 9, 2026
What it is
Adds two trigger run settings to the new workflows builder. Exclusion Criteria (like unenrollment and suppression lists) stops a run from starting or ends one in progress, on all object-based triggers. Merge settings decide whether a record runs when it meets criteria after a merge, on "Records match criteria > Custom criteria" triggers. Find it under Agents > Agent Hub > Workflows.
Why it matters
Gives more control over which records a workflow runs on, matching the legacy tool. Merge settings used to be contact-only and now work for every object that supports merging.
The Take
But last I did, there were some more significant gaps that I wasn't comfortable building in until they were resolved or making it my first place to build and exclusion criteria is among them.
Per the panel, the new workflow builder in Agent Hub gets two run settings on triggers: exclusion criteria and merge settings. It is in public beta for Marketing, Sales, Service and Data Hub, and Smart CRM, on Professional and Enterprise. I will note the panel said it was scheduled for release today and still said public beta, so read that however you like. The merge setting is also wider than it was: it used to be contact workflows only and now covers object-based workflows that support merging.
Exclusion criteria is the one that matters to me, and it comes up on a regular basis. At UNBOUND, Kyle said in one of his sessions that from now on you should be building workflows in the new builder, not the old one. I was sitting next to a friend when he said it, and I told my friend that they had dropped some changes while we were there, that I had not played with all of them, but that last I did there were some more significant gaps I was not comfortable building in. Exclusion criteria was one of those gaps, and it is the reason I had not made the new builder my first place to build.
Oakes agrees with Kyle if you insert the word “try”: you should try building there. He keeps hitting places where the new and old builders are not at parity. He also wants the new builder’s extra capability, like not being bound to objects, so he is waiting on parity before he moves things over. Exclusion criteria is a real step toward it, and we are both glad it landed.
The merge setting is the part neither of us can answer. Even in the old builder, when you are pre-flighting a workflow and it asks whether you want to enroll records if they merge, we both understand why it is asked, but we cannot work out the ramifications, so we cannot say no. Chasing the dependencies is close to impossible. It must be scenarios we do not deal with.
What to do: if you build workflows on Professional or Enterprise, open Agent Hub, then Workflow, and try the exclusion criteria on a low-stakes workflow this week. Check it against how your legacy unenrollment and suppression lists behave before you move anything that matters. If you are happy in the legacy builder, you can wait; parity is not here yet.
Watch Us Discuss This
The full segment from the show, us working through this update start to finish.
FAQ
What shipped?
Per the panel, two new run settings on triggers in Agent Hub's workflows builder: exclusion criteria, which can prevent a run from starting or end one in progress, and merge settings, which determine whether a record runs in a workflow when it meets the criteria upon merging with another record.
Where do I find the new workflow builder?
Per the panel, go to Agents in the nav, then Agent Hub, then Workflows. On air, Casey noted you can also use More, which represents the old menu, to find it the old way.
Should I build in the new builder now?
The show landed on try. Casey said Kyle told the UNBOUND room to build in the new builder now, and exclusion criteria was one of the gaps that kept her from it. Oakes agreed if you insert the word try: he still hits places where there is no parity between the new and old builders.
What should I do about the merge setting?
The show could not settle it. Both hosts said they understand why the question is asked, but neither can work out the ramifications of enrolling records on merge, so neither usually says no.
Produced by Value-First Media