When a component is executed, the platform evaluates whether the component contains any dynamic triggers. Dynamic triggers cause the app to pause and wait for a user action.
There are three button types that generate dynamic triggers:
component_next. From the property compatibility chart, you can see that these button types are inferred by the presence of one or more these properties:
If a component doesn’t generate any dynamic triggers, the flow will move on to the next step automatically.
Some components, such as the
askcomponent, always contain a dynamic trigger and do not continue the flow automatically.
Output-only components can have dynamic triggers added to them by defining quick replies that use the
data properties. These properties change the quick reply’s inferred type to
flow_next, which create dynamic triggers and cause the component to wait for the user’s response before continuing.
Updated 4 months ago