The Ultimate WhatsApp Automation Blueprint: 9 Triggers, 12 Actions & Triple-Layer Wait Resumption

High-Availability Workflow Pipeline: Trigger → Condition Filtering → Action Dispatch → Wait Step → Triple-Layer Resumption → CRM Deal Pipeline.

1. Workflow Engine Architecture Overview

The Ai Botflow Automation Engine is an event-driven workflow orchestrator specifically architected for Meta's WhatsApp Cloud API and omnichannel pipelines.

Unlike rigid, linear auto-responders, the engine operates on a state-machine execution model:

1. Inbound Event Capture: An incoming message, webhook payload, or contact tag change triggers engine evaluation.
2. Pessimistic Execution Logging: Before executing any action, the engine creates an execution log row in the database with status running to guarantee auditability and idempotency.
3. Sequential Step Loop: Steps execute in order. When branching conditions (If / Else) are evaluated, the execution pointer follows either the YES or NO branch.
4. State Suspension on Delays: When a wait step is encountered, the execution state, current variable map, and target resumption timestamp (run_at) are committed to the automation_pending_executions table.

2. Deep Dive: The 9 Supported Triggers

A trigger is the starting catalyst that launches a workflow. Ai Botflow supports 9 native triggers:

3. Deep Dive: The 12 Action Nodes

Once triggered, the engine executes customized steps:

1. send_message (Plain Text): Instant WhatsApp text with dynamic templating tags (e.g., Namaste {{name}}).
2. send_buttons (Interactive Quick Replies): Sends up to 3 clickable buttons per Meta policy for friction-free responses.
3. send_list (Interactive Menu): Sends an interactive menu card with organized sections and up to 10 selectable items.
4. send_template (Meta-Approved Cloud API Template): The 24-Hour Window Bypass. After 24 hours of customer inactivity, only approved templates can be delivered. Supports image/PDF headers and positional params {{1}}, {{2}}.
5. wait (Resilient Delay): Suspends workflow execution for specified minutes, hours, or days. Resumed by the Triple-Layer Engine.
6. condition (If / Else Decision Node): Branches workflow based on Contact Tags (e.g., has tag "VIP"?), Contact Field values (e.g., city == "Mumbai"), or message regex.
7. add_tag & remove_tag: Dynamic customer segmentation. Protected with 5-level infinite loop recursion limits.
8. create_deal (CRM Pipeline Integration): Automatically inserts a deal into a designated Kanban stage, auto-merging with active deals if already present.
9. assign_conversation: Assigns conversation to a specific sales rep or distributes evenly via Round-Robin across the sales team.
10. update_contact_field: Modifies standard attributes (name, email, company) or workspace Custom Attributes.
11. send_webhook: Dispatches real-time HTTP POST JSON to third-party endpoints (Zapier, Make, custom ERP) with strict SSRF private-IP blocking.
12. close_conversation: Marks the WhatsApp thread as resolved in the Shared Inbox once the workflow reaches its conclusion.

4. How the Triple-Layer Wait Resumption Works

The true test of an enterprise automation engine is how it handles delays. In basic CRMs, if an application restarts during a 3-day drip wait, the process dies.

Ai Botflow implements a Triple-Layer Resumption Architecture:

5. Dynamic Variables & Templating Syntax

You can personalize WhatsApp messages and webhook payloads dynamically:

6. Three Real-World Automation Recipes

Recipe A: Welcome Flow + 2-Hour Drip

• Trigger: first_inbound_message
• Step 1: send_message → "Namaste {{name}}! Welcome to Ai Botflow. How can our team help you today?"
• Step 2: add_tag → Tag: New Inbound Lead
• Step 3: create_deal → Stage: Discovery Stage
• Step 4: wait → 2 hours
• Step 5: send_message → "Hi {{name}}, just following up! Did you have a chance to check out our demo video?"

Recipe B: Interactive Keyword Menu with Quick Reply Buttons

• Trigger: keyword_match (Keywords: "PRICE", "MENU", "SERVICES", Match: contains)
• Step 1: send_buttons with Header: "Ai Botflow Solutions" and Buttons:
  • btn_pricing: 💰 Pricing Plans
  • btn_demo: 🎥 Book Live Demo
  • btn_support: 📞 Call Support

Recipe C: Facebook Ads / Website Lead to CRM Pipeline

• Trigger: incoming_webhook (Mapped from Facebook Instant Forms or Shopify)
• Step 1: send_template → Dispatches pre-approved welcome WhatsApp template immediately.
• Step 2: add_tag → Tag: Paid Social Lead
• Step 3: create_deal → Deal Title: {{name}} - {{vars.service}}
• Step 4: assign_conversation → Mode: Round-Robin across active sales reps.

7. Monitoring, Execution Logs & Meta 24h Policy

A mission-critical aspect of production automation is continuous observability:

• Granular Logs: Navigate to /automations/[id]/logs to inspect each execution. Statuses include: 🟢 Success (Delivered), 🟡 Partial (Sleeping in wait step), and 🔴 Failed (Meta error code or invalid number).
• 24-Hour Policy Compliance: Meta enforces a 24-hour customer service window. Plain text messages sent after 24 hours of inactivity fail with error code #131047. Always use approved templates (send_template) for delays exceeding 24 hours.
• Infinite Loop Protection: Tag-triggered automations are enforced with a strict 5-level execution depth limit to prevent infinite cascading loops.

8. Frequently Asked Questions