Feature: Support Filters (code) in Actions.
Description: Flows and actions are great to visualize the login flow, but trying to use existing actions sometimes lack the ability to filter certain requests.
so on one hand you have predefined Actions - which save you time writing common logic, on the other they are not flexible enough to match all use cases.
Use-case: We want to use the market Password Rotate Action, but want to limit this policy to certain requests (for example API requests should not reset their password) , or exclude certain users.
we cannot do that today , and we are forced creating our own custom Action.
this seems like a very basic staff we don’t wont to rewrite, and probably this enhancement can benefit other Actions as well. (linking accounts etc)
Thanks for creating this feedback card! Please make sure to upvote it so that it has as many votes as possible and potentially attract other people from community as well. We review those feedback cards on a monthly basis and will let you know once we have updates to share on that front. Thank you!
As this topic is related to Actions and Rules & Hooks are being deprecated soon in favor of Actions, I’m excited to let you know about our next Ask me Anything session in the Forum on Thursday, January 18 with the Rules, Hooks and Actions team on Rules & Hooks and why Actions matter! Submit your questions in the thread above and our esteemed product experts will provide written answers on January 18. Find out more about Rules & Hooks and why Actions matter! Can’t wait to see you there!
Learn more here!