Business Problem
Workflow adoption keeps growing, including heavier patterns like loops and adaptive approvals. At the same time, trigger filters still feel complex to create and hard to validate. Many teams end up either sticking with defaults, or overly broad triggers, which often means workflows fire more often than people expect. We want to make trigger filters easier to build , easier to understand, and easier to test before you turn things on, so you can be confident about when a workflow should run.
Sound Familiar?
Does any of this sound like your team?
-
You mostly rely on basic filtering because advanced options feel unclear, hard to build, or buried in JSON.
-
You have more workflow executions than you expected, or workflows seem to run when you did not intend them to.
If yes, we want your input.
Get Involved
We are conducting research sessions to learn more about your experience, ensuring we meet common use cases. Please note that these sessions will be recorded for internal product research and development purposes. During the call we will:
-
Learn how you are approaching creating trigger filters today.
-
Understand the key challenges you face when building a trigger filter
Schedule a call to provide insights and feedback for your business needs.
Thanks in advance for your input and participation and we can’t wait to hear from you!