⚠️ Problem Statement
Currently, when a Procedure Builder configures a flow to fetch external data (e.g., retrieving a list of recent orders, linked accounts, or purchased products via an API), the experience often breaks continuity. After the data is fetched, Fin has to ask the user to manually type out the specific order number or product name into a blank text input. This manual transcription introduces friction, increases the margin for user error, and degrades the premium "app-like" messenger experience.
✅ Proposed Solution / Feature Concept
Introduce an automated, temporary messenger app experience generated dynamically from API payloads. Instead of returning raw text or forcing a manual text reply, Fin should leverage an ephemeral UI component (a "Preview App") directly inside the messenger canvas.
When an API response returns an array or an object collection, the Procedure Builder should be able to map those objects to interactive UI elements. The customer can then simply click/tap their selection from the visual response to advance the flow.
🛠️ Example Use Case / Flow
-
Step 1: Fin initiates a backend check: "Display all orders for this customer."
-
Current State: Fin lists the text or drops a blank input box: "Please type the order ID you are referring to."
-
Proposed State: Fin renders an interactive list/carousel card component showing the last 3 orders (Order #, Date, Total).
-
Step 2: The customer clicks the specific order card.
-
Step 3: Fin instantly updates the context and moves to the next interactive picker: "Which product from this order are you referring to?" (Renders clickable Product Items).