12 Nov 2026: Ripple for Flows & Translated Flows

Ricardo Updated by Ricardo

WhatsApp Flows are the forms inside WhatsApp. One message can carry several screens: multiple choice, dropdowns, date pickers, even images. They're great for onboarding, intake questions, or asking someone which symptoms they have before you route them anywhere.

The challenge was building them. A Flow is written in Flow JSON, so you either wrote the JSON yourself or built it in Meta's Playground and pasted the code back into Turn.

Two things change today. Ripple can now build and edit Flows for you, and a Flow you build once can go out in the other languages your journey supports.

Ask Ripple to build the Flow

Open a Flow from Content > Flows and you'll see Ask Ripple in the top right. It opens a chat next to the editor. You can describe the whole form, for example "a three-screen intake with name, date of birth, and a multiple choice for symptoms", and Ripple writes it. Or you can ask for small things as you go, like changing a button from Continue to Submit or adding a question to the second screen.

The preview updates as the code changes, so you see the form your contacts will see, and the code editor is still there if you want to read it or change it yourself.

Ripple also takes care of the fiddly part of dynamic Flows. If you want to pre-fill a Flow with something you already know, like the contact's name, the Flow JSON needs that data declared and passed from screen to screen. Ripple does that for you, so the Flow card in your journey can just fill it in.

All you need is an OpenAI account with API credits connected to Turn, the same as for Ripple in Journeys. Learn how to here.

Send the same Flow in another language

Until now, if you served contacts in English and Spanish, you'd end up keeping two copies of the same Flow and making sure every change happened in both.

Now, if the copy in your Flow comes from variables, you translate it on the canvas instead. Pick the language at the top of the canvas, select the Flow card and click Translate initial data. You get the same form you use to fill in the Flow's data, but this time you're writing the Spanish version (or Portuguese, or whichever language you need). Spanish-speaking contacts get the Spanish Flow, and everyone else gets the original.

Any field you leave empty goes out untranslated, so you can do it bit by bit.

One limit worth knowing about: initial data doesn't work in templates yet, so a Flow you send in a template needs hardcoded copy and can't be translated this way.

Getting started

The WhatsApp Flows guide covers creating a Flow, using it in a journey, dynamic data and translation, with an example date picker to start from.

Was this article helpful?

Action required: WhatsApp usernames and BSUIDs — what you need to know

9 Nov 2026: Telehealth Agenda and Turn Meet: run your consults on WhatsApp