A WhatsApp Form is a multi-step form that opens inside a WhatsApp chat, with text fields, date pickers, dropdowns and buttons. The customer fills it in without leaving WhatsApp, and the answers reach your server as structured data. Meta's name for the feature is WhatsApp Flows. Sautikit sends it to a customer from a KES 500 a month number with one API call and delivers the submission to your webhook.
You build the Flow in Meta's tools, send it to a customer with one call to Sautikit's POST /v1/whatsapp/messages, and receive the submission on your whatsapp.event.received webhook.
A link to a web form asks a customer on a phone to leave the conversation, wait for a page to load on mobile data, and type into fields that were designed for a desk. A WhatsApp Form opens in the app the customer is already using, on the connection that is already open, and offers taps where a web form asks for typing.
Meta hosts the form. You design the Flow (its screens, fields and validation) in WhatsApp Manager's Flow Builder or with Meta's Flows API, and publish it there. Meta gives the Flow an id. Sautikit does not build or host the form.
Sautikit sends it. You connect your own WhatsApp Business account to a Sautikit number in the console (Numbers, WhatsApp tab, Meta's Embedded Signup). You then send the Flow as an interactive message of type flow.
Your webhook receives the answers. When the customer submits, Meta's payload is relayed unchanged to your whatsapp.event.received webhook.
A garage on Thika Road wants customers to book a service slot from WhatsApp. The Flow has three screens: choose a service, pick a date, pick a time. It is published in WhatsApp Manager with the id 1234567890.
number_id is your Sautikit number's id. The interactive object is forwarded to WhatsApp unchanged, so any other parameter Meta documents for Flow messages, such as a flow_token to tag the submission, goes in parameters as Meta specifies.
The customer sees the message with a Book a slot button. Tapping it opens the form over the chat.
A free-form interactive message can be sent within 24 hours of the customer's last message. To send a form outside that window, attach the Flow to a template approved by Meta and send it with type: "template".
When the customer taps submit, your webhook receives a whatsapp.event.received event. Sautikit relays Meta's own webhook payload to you byte for byte and does not parse or reshape it, so the body is Meta's, not a Sautikit format. Route it from the X-Sautikit-Event-Kind header, because the body has no kind field.
What Sautikit documents about the body: it has messaging_product, a metadata object whose phone_number_id tells you which of your WhatsApp numbers received it, and a messages array. Each entry in messages has from, id, timestamp and a type that names the sibling object holding the contents. For a form submission, that is the interactive object, and the answers are inside it. The exact shape of a Flow submission, including how the answers are encoded, is defined by Meta: see Meta's WhatsApp Flows documentation and log one real submission from your own Flow before you write the parser. The keys of the answers are the field names you chose when you built the Flow.
import express from "express";const app = express();app.use(express.json());app.post("/webhooks/sautikit", async (req, res) => { res.sendStatus(200); if (req.get("X-Sautikit-Event-Kind") !== "whatsapp.event.received") return; for (const msg of req.body.messages ?? []) { const reply = msg.interactive?.nfm_reply; if (msg.type !== "interactive" || !reply) continue; // Delivery is at-least-once: skip a submission you have already stored. if (await bookings.exists({ messageId: msg.id })) continue; const answers = JSON.parse(reply.response_json); const booking = await bookings.create({ messageId: msg.id, phone: msg.from, service: answers.service, date: answers.date, slot: answers.slot, }); await sendWhatsApp({ to: msg.from, type: "text", text: { body: `Booked: ${booking.serviceName} on ${booking.date} at ${booking.slot}. Reply here if you need to change it.`, }, }); }});
The handler reads the answers from interactive.nfm_reply.response_json, Meta's field for Flow answers; confirm it against a real submission as above. sendWhatsApp is the same POST /v1/whatsapp/messages call as step 1 with a text message. Verify the webhook signature before trusting the body; the function is in verify webhook signatures. Sautikit does not store messages or submissions, so the booking lives only in your database.
A form submission arrives on the same webhook as your other WhatsApp messages and delivery statuses, so it fits the handler you already run. The WhatsApp messaging API covers text, templates, buttons and lists.
The confirmation can carry a tap-to-call button. A loan applicant with a question or a patient who needs to explain a symptom can then call you from the chat, on the same Sautikit number. See WhatsApp calling for your Kenyan business.
A Sautikit number is KES 500 a month with no setup fee, and Sautikit does not charge per WhatsApp message or per form submission. Any WhatsApp fees are billed by Meta to your WhatsApp Business account. Rates for calls on the same number are on /pricing.
Claim a number at sautikit.com/numbers, connect your WhatsApp Business account from the number's WhatsApp tab in the console, and send your first form with the request above.