Connect Pabbly Connect to WhatsApp

This is Pabbly's standout advantage. Filters, path routers, text and number formatters, date formatters, iterators, and schedulers do not count as tasks. Only the trigger and external action steps consume tasks. You can build complex multi-step logic without inflating your task usage, unlike Zapier and Make.

There is no dedicated WA.Expert app in Pabbly Connect. Use the API by Pabbly action module to send an HTTP request to the WA.Expert API. This is available on all Pabbly plans including the free tier.

Pabbly's flat pricing and free internal apps make it attractive for complex, high-volume workflows. Zapier has the largest app library.

Action Event: Execute API Request

Method:  POST
Endpoint URL: https://api.wa.expert/v1/send

Headers:
  API-KEY: YOUR_WAEXPERT_API_KEY
  Content-Type: application/json

Payload Type: JSON

Body:
{{
  "to":       "[phone from trigger]",
  "type":     "template",
  "template": {{
    "name":     "order_confirmation",
    "language": {{"code": "en"}},
    "components": [
      {{
        "type": "body",
        "parameters": [
          {{"type": "text", "text": "[name from trigger]"}},
          {{"type": "text", "text": "[order_id from trigger]"}}
        ]
      }}
    ]
  }}
}}

Map [phone from trigger] etc. by clicking the field and selecting
the mapped value from the trigger step's data.

In the API by Pabbly body, click into any value field and Pabbly shows a dropdown of all fields captured from the trigger step. Select the phone number field for the to value and the relevant fields for each template variable. Pabbly inserts the mapping automatically.

POST https://connect.pabbly.com/workflow/sendwebhookdata/YOUR_HOOK_ID
Content-Type: application/json

Body:
{{
  "customer_name":    "{{customer_name}}",
  "customer_phone":   "{{customer_phone}}",
  "customer_message": "{{customer_message}}"
}}

Pabbly receives this and routes through the workflow:
  Webhook -> Filter (free) -> Google Sheets (counts as task)
                           -> Router (free) -> HubSpot (counts as task)

1. Trigger: Facebook Lead Ads — New Lead (1 task)
   Captured: name, phone, city, budget

2. Filter: only continue if budget > 50000 (FREE — no task)

3. Router: split by city (FREE — no task)
   Route A (Mumbai) -> API by Pabbly -> WA.Expert (1 task)
     Template: mumbai_welcome
   Route B (other)  -> API by Pabbly -> WA.Expert (1 task)
     Template: general_welcome

4. API by Pabbly -> WA.Expert send:
   POST https://api.wa.expert/v1/send
   Header: API-KEY: YOUR_KEY
   Body: {{to: [phone], template: {{name: 'mumbai_welcome', ...}}}}

Total tasks used per qualifying lead: 2 (trigger + 1 send)
Filter and router: free. Complex logic at no extra task cost.