Add conditions to workflow triggers

Today weโ€™re adding the ability to set workflow trigger conditions on any trigger step. Previously to stop a workflow from executing, you needed to use a branch step at the start of your workflow with no channel steps in the branch. Now using trigger step conditions, you can halt a workflow from executing before any steps run.

This is especially helpful in cases where you have a high volume event stream that youโ€™d like to point at a Knock workflow and then use a trigger condition to select when the workflow should actually run. As an example, you could have an account-balance-updated event connected to a workflow, with a trigger condition to only run the workflow when the account balance goes under five dollars.

You can access trigger step conditions by selecting any trigger step in the workflow builder or using the conditions object in your workflow definition in our management API.

Fixes and improvements

  • ๐Ÿ› We fixed an issue with our React Native SDK that incorrectly referenced document when instantiating a feed
  • ๐Ÿ› We fixed an issue with our JS client SDK where extra event listeners could be created when auto-managing sockets is enabled
  • ๐Ÿ› We fixed an issue where a deleted schedule could leave ghost schedules running