WhatsApp V2 Action in Sparkforge Workflows

By Sparkforge Support Team ·Last reviewed May 3, 2026

WhatsApp V2 Action automates WhatsApp messages inside Sparkforge workflows with smart branching from button replies, timeout fallbacks, wait-for-reply pauses, and on-the-fly media URL changes.

WhatsApp V2 Action is the workflow component for sending WhatsApp messages with branching, timeout, and reply logic baked in. Replaces the older V1 step for new builds.

What V2 adds over V1

  • Smart branching — auto-generates branches per quick-reply button
  • Media flexibility — swap PDF, video, or image URLs in the action without rebuilding the template
  • Message types — free-form, template, or WhatsApp Flows
  • Branch toggle — disable reply branching when not needed
  • Timeout actions — define what fires if the user goes silent
  • Wait-for-reply — pause the workflow until the contact replies (post-delivery)
  • Auto delivery handling — no manual If conditions for delivery tracking

Build a WhatsApp V2 workflow

  1. Create or pick a template under Messaging → Templates. Add buttons, media, or Meta Flows.
  2. In the workflow builder, add the WhatsApp V2 action.
  3. Choose the message type: template, free-form, or Flow.
  4. If using reply buttons, branches are generated automatically.
  5. Set a timeout duration and fallback path.
  6. Toggle wait-for-reply on or off based on flow design.
  7. Save and run a test contact through the workflow.

Smart branching

When the template includes reply buttons, V2 reads the buttons and creates a workflow branch per button. No manual If/Else conditions to maintain.

Timeout vs wait-for-reply

  • Timeout — trigger a follow-up if no response inside the window. Workflow keeps running.
  • Wait-for-reply — workflow pauses entirely until the contact replies. Useful for high-engagement nurtures.

Editing media on the fly

Change the URL for images, PDFs, or videos directly in the V2 action config, even on approved templates. Skips the re-approval cycle when swapping creative.

FAQ

Frequently Asked Questions

What happens if the message isn't delivered?
V2 tracks delivery and routes the contact down the appropriate branch automatically. No manual delivery condition needed.
Can I run V1 and V2 in the same workflow?
Technically yes, but use V2 exclusively in new builds. Mixing them gets confusing fast and you lose V2's branching benefits.
Do I need Meta Flow setup to use templates?
Only if your template includes a Flow component. Basic templates and free-form messages work without Flow setup.
How do I disable smart branching?
Turn off the <em>Branch Replies</em> toggle in the action settings. V2 will then behave like a simple notifier.
Where do I see which branch a contact took?
Open the workflow execution logs. Each contact shows delivered, replied, or timeout status with the branch they followed.

Was this article helpful?

Related Articles