Dynamic triggers

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: action, flow_next, and 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: action, result, and data.

If a component doesn’t generate any dynamic triggers, the flow will move on to the next step automatically.

Mandatory dynamic triggers

🚧

Some components, such as the ask component, always contain a dynamic trigger and do not continue the flow automatically.

Output-only components

The normal behaviour of some components is to continue the flow since they are “output-only”. The say and image components are two examples.

Output-only components can have dynamic triggers added to them by defining quick replies that use the action, result, or data properties. These properties change the quick reply’s inferred type to action or flow_next, which create dynamic triggers and cause the component to wait for the user’s response before continuing.