React to a submitted WhatsApp Flow with a workflow in Omnifox

A WhatsApp Flow is that native form that opens right inside the WhatsApp chat: the customer picks options, types data and submits everything at once. The classic problem is that this valuable information stays buried in a single message. With the WhatsApp Flow responded trigger in Omnifox workflows you can capture every form answer and act in seconds: update the contact record, create a CRM deal and send an automatic confirmation. In this guide we build that flow node by node.

What fires the workflow

Every workflow has a single trigger. Here we use WhatsApp Flow responded, which fires the instant the customer taps "Submit" inside the form. You can filter it by channel if you have several WhatsApp numbers connected, so only the relevant one reacts.

The form answers arrive as variables you can drop into any downstream node. Together with contact and message data, you have everything you need to populate your CRM without writing code.

Step 1: store the data with Update contact

The first node after the trigger is Update contact. Here you map each Flow field to a contact field: name, email, company, city, whatever you asked in the form. Use variables like {{$contact.first_name}} for what already exists and the form variables for what is new. That keeps the record complete and clean before any other action.

A good habit is to add an Add tag node too (for example flow-completed or qualified-lead) so you can segment later and so other workflows know this contact already went through the form.

Step 2: branch on the answer

Not every submission is the same. This is where a Condition comes in. With the If (single rule) node you can ask, for instance, whether the declared budget crosses a threshold; or with Switch (multiple branches) you can open one branch per interest the customer selected (sales, support, demo).

So far the flow looks like this:

1. WhatsApp Flow responded (trigger)
2. Update contact (stores the data)
3. Add tag (marks the lead)
4. Switch (branches by interest)

Step 3: create the CRM deal

On the sales branch, the star node is Create deal. You feed it the title (for example customer name + product), the amount declared in the Flow and the initial pipeline stage. You can chain an Assign deal owner node with round-robin or least-load routing so it lands automatically on an available rep.

If you want a trail, add Log activity/note with a summary of what the customer answered; the rep opens the deal and understands the context without re-reading the chat.

Step 4: confirm with a template

Courtesy closes the deal. Because the conversation may be outside the 24-hour window, the right move is to use Send WhatsApp template instead of a free message. Pick an approved template like "We received your request" and inject variables: {{$contact.first_name}}, the reference number or the assigned rep name.

If the form was answered inside the 24-hour window and you want something more conversational, you can use a plain Send message. A handy variant: a Ask a question node that waits for the customer reply ("Would you rather we call today or tomorrow?") and branches based on the answer.

Step 5: alert the team

So nobody leaves a hot lead cold, add Notify team by email or Transfer to an agent (Handoff) on the high-value branch. You can also Add internal note on the conversation so whoever picks it up sees at a glance that it came from a Flow.

Full example flow

WhatsApp Flow responded -> Update contact -> Add tag -> Switch -> (sales branch) Create deal -> Assign deal owner -> Send WhatsApp template -> Notify team by email

Common mistakes

• Using Send message outside the 24-hour window. Meta blocks it; always use Send WhatsApp template when unsure.
• Poor field mapping. Check that each Flow field points to the right field in Update contact; an empty field resolves to an empty string and does not break the flow, but you lose the data.
• Creating the deal before branching. If you create a deal for everyone, you pollute the pipeline with tire-kickers. Branch first with Switch or If.

Variants worth trying

• Book directly with the Book appointment node if the Flow asked for a preferred date.
• Push the answer to Google Sheets (append row) for quick reporting, so revenue ops has a live sheet of every submission.
• If you integrate an external system, use HTTP request to push the lead into your ERP or marketing automation tool.
• Chain Change lifecycle stage to move the contact from lead to opportunity the moment they qualify, keeping your funnel reports accurate.

Capturing a WhatsApp Flow and turning it into an updated contact, a deal and an automatic confirmation is one of the highest-ROI automations around. Build it in minutes with the visual editor in Omnifox and let every form work for you.