TTo resolve the "Unsupported trace found!" error when trying to display choices buttons through a Custom Action component, it's crucial to ensure that the Custom Action's configuration aligns with Voiceflow's expected trace types and structures. Here are some key points to consider:
Relevant documentation:
- Custom Actions in Voiceflow allow for dynamic rendering of chat elements like Buttons, Carousels, and Cards. However, the action's name and payload must match expected trace types for these elements to render correctly in Voiceflow-built chat interfaces.
- The action type specified in your Custom Action must correspond to one of the predefined paths or trace types recognized by Voiceflow. If the type field does not match, the action will be treated as a dead-end, leading to errors like the one you're encountering.
- For rendering standard Voiceflow steps (e.g., Buttons) through a Custom Action, the action's name value should explicitly match the desired trace type (e.g., "choice" for buttons). The payload must then correctly structure the data according to the expected format for that trace type.
- Ensure that the JSON structure you're generating for the buttons matches the required format closely. Any deviation in the expected structure could lead to rendering issues or errors.
Relevant documentation: