Advanced Configuration for Keyword Trigger
Migrated from Canny.
Canny Post ID: 66e6da2aeb4f669982c64137
Canny URL: https://spur.canny.io/admin/board/feature-requests/p/advanced-configuration-for-keyword-trigger
Category: Improvement
Original status: open
Original votes: 3
Original comments: 0
Original author: Divyansh Balchandani
Created at: 2024-09-15T12:59:22.029Z
Original request details:
Keyword trigger should allow advanced configuration.
Currently, if the message contains a keyword, a flow is triggered.
This causes conflicts if the message contains two keywords, triggering two flows instead of one.
Adding advanced configuration would not only prevent it, but would also allow brands to create flows for more complex use cases.
Advanced configuration would include all the options in the attached screenshot, plus:
- Message match (on a scale of 1 to 3)
Think of it as %age match. At 1, if 25% of the message matches the keyword, a flow will trigger.
At 3, a flow will trigger if the message contents match 75% of the keyword.
This option is just to deal with conflicts, if they arise. A higher match %age would be prioritized if there is a conflict like the one shared in the above example.
1 Comment
Sign in to comment
REQUEST_SUMMARY_V2 Problem - Keyword trigger should allow advanced configuration. Currently, if the message contains a keyword, a flow is triggered. This causes conflicts if the message contains two keywords, triggering two flows instead of one. Adding advanced configuration would not only prevent it, but would also allow brands to create flows for more complex use cases. Advanced configuration would include all the options in the attached screenshot, plus: - Message match (on a scale of 1 to 3) Think of it as %age match. At 1, if 25% of the message matches the keyword, a flow will trigger. At 3, a flow will trigger if the message contents match 75% of the keyword. This option is just to deal with conflicts, if Expected behavior - Allow this condition/action directly in workflow builder - Support testing with real sample events before publishing - Provide clear logs for why a workflow did or did not run Business impact - Reduces manual operational effort for teams - Improves consistency and customer experience - Helps teams move faster with fewer support escalations Legacy category: Improvement
Sign in to comment