Beyond the Notification: Building Real-Time Shopify Admin Updates via WhatsApp Webhooks

Azam Sajid — Tue, 17 Mar 2026 14:28:47 +0000

Standard SMS is a black hole for data. When you send a verification text for a Shopify COD order, you’re just shouting into the void and hoping for a reply.

At Waaibot, we decided to treat WhatsApp not just as a messaging app, but as a remote UI for Shopify. By leveraging the Official WhatsApp Business API and Shopify Webhooks, we built an interactive flow where a customer’s button click triggers a millisecond-fast state change in the merchant's Admin Panel.

The Logic Flow:

Order Created: Shopify fires a orders/create webhook to our Next.js backend.
Interactive Dispatch: We send a template message with "Confirm" and "Cancel" buttons via Meta Cloud API.
The Interaction: User taps "Confirm." WhatsApp sends a webhook to us.
The Update: We hit the Shopify Admin API to flip the order status, update tags, and adjust inventory.

We even built an interactive simulator in our latest technical deep-dive to show how this state management works in real-time.

Read the full technical breakdown and play with the simulator here: https://waaibot.com/blogs/shopify-cod-whatsapp

How to Send Automated WhatsApp Messages from Oracle APEX (The Modern Way)

Azam Sajid — Mon, 16 Mar 2026 20:41:32 +0000

The Challenge: Beyond Standard Emails

In modern ERP and CRM systems built on Oracle APEX, email notifications are no longer enough. Customers want real-time updates—order confirmations, shipping alerts, and OTPs—delivered directly to WhatsApp.

While you can use UTL_HTTP, the modern standard for APEX developers is APEX_WEB_SERVICE. It’s cleaner, handles CLOBs better, and simplifies the REST call.

Method 1: Using `APEX_WEB_SERVICE.MAKE_REST_REQUEST` (Recommended)

This is the most efficient way. It integrates directly with the APEX engine and makes handling JSON payloads a breeze.

DECLARE
  l_response CLOB;
  l_url      VARCHAR2(400) := 'https://api.waaibot.com/api/v1/send';
  l_api_key  VARCHAR2(100) := 'YOUR_API_KEY';
  l_body     CLOB;
BEGIN
  -- Constructing the JSON Payload
  l_body := '{"number": "923001234567", "message": "Your Order #1029 is ready for dispatch!"}';

  -- Setting headers and making the request
  apex_web_service.g_request_headers(1).name  := 'Content-Type';
  apex_web_service.g_request_headers(1).value := 'application/json';
  apex_web_service.g_request_headers(2).name  := 'Authorization';
  apex_web_service.g_request_headers(2).value := 'Bearer ' || l_api_key;

  l_response := apex_web_service.make_rest_request(
    p_url         => l_url,
    p_http_method => 'POST',
    p_body        => l_body
  );

  -- Output response for debugging
  DBMS_OUTPUT.put_line('Response: ' || l_response);
END;

Method 2: The Legacy `UTL_HTTP` Approach

If you are working in a pure PL/SQL environment outside of an APEX session (like a background DBMS_JOB), you’ll need UTL_HTTP. This requires your Oracle Wallet to be configured for SSL.

Note: Waaibot uses a hybrid socket connection, which means you don't need to worry about complex Meta Business verification just to send a notification to your own customers.

Why this Architecture Wins for Oracle Developers:

Zero Infrastructure: No need to set up a Node.js middleware. Your database talks directly to the WhatsApp gateway.
Cost Efficiency: Unlike the official Cloud API that charges per message, using a socket-based API at waaibot.com allows for high-volume notifications without the "Meta tax."
Security: By using APEX_WEB_SERVICE, you can store your API keys in APEX Web Credentials for maximum security.

Pro-Tip: Handling the Response

Always wrap your call in a JSON_TABLE query to log the message_id. This allows you to track delivery statuses directly inside your APEX dashboard.

Want to try this in your dev environment? Grab a free API key at waaibot.com and start sending messages in under 5 minutes.

DEV Community: Azam Sajid