Workflows need a decision node! Currently, if you pass variables into a phone webhook, you can’t act on them at the start of the workflow—you’re forced to use a Prompt, API, or Tool node. A decision/switch node at the beginning would make dynamic workflows possible. Example: If I already have a customer’s zip code from a previous interaction, my Address Collection workflow could adapt right away: • If zip is present → say: “Please say your street address in {CITY}, {STATE_NAME}.” • If not → say: “Please say your 5-digit zip code.” Right now, I have to start with an API call to update the workflow, even though the webhook already provided the zip, city, and state—an unnecessary extra step. Also, please consider bringing back the “Say” node. Prompt nodes always expect a customer response, which creates awkward interactions when I just want to play a message and move on. Thanks for considering these requests!