TIt seems like there might be a misunderstanding in how custom actions and choice buttons are rendered in Voiceflow. Custom actions allow for integration and dynamic rendering of elements like carousels, cards, and buttons, but they need to be correctly configured to work as intended. Here are a few key points to consider:
For more detailed guidance on setting up custom actions and rendering elements dynamically, please refer to the Voiceflow documentation:
- Ensure your custom action is correctly named in the Voiceflow Creator, as this name will be used as the trace type value.
- The custom action's payload should correctly match the expected structure for rendering buttons. This includes specifying the type and payload for each button.
- Voiceflow-built chat interfaces such as the Test Tool, Prototype Tool, and Web Chat can automatically render default Voiceflow chat elements based on their traces.
- If the type field in your custom action does not match one of the path names defined in your Voiceflow project, it will act as a dead-end block, not rendering any further elements.
For more detailed guidance on setting up custom actions and rendering elements dynamically, please refer to the Voiceflow documentation:
MBased on that I can't figure out where I went wrong.