WhatsApp Automation API — Automate Messaging at Scale

Trigger automated messages, build workflows, and connect WhatsApp to your existing systems. Order confirmations, appointment reminders, notifications — all automated through our REST API.

Common Automation Use Cases

Order Confirmations and Shipping Updates

When a customer places an order on your website, your system calls our API to send a WhatsApp confirmation instantly. "Hi Ahmed, your order #4821 is confirmed. We will ship it tomorrow." When the order ships, another automated message goes out with the tracking number. When it is delivered, a final message asks for feedback.

This chain of automated messages keeps customers informed without any manual work. The customer feels taken care of, and your support team handles fewer "where is my order?" inquiries.

Appointment Reminders

Clinics, salons, consultants, and service businesses use automated reminders to reduce no-shows. Send a reminder 24 hours before the appointment, another one 2 hours before, and a follow-up after. Include a link to reschedule or cancel. This alone can reduce no-show rates by 30-40%.

Payment Notifications

Automatically notify customers when a payment is received, when an invoice is due, or when a subscription renews. "Your payment of $29.99 was received. Thank you!" These transactional messages build trust and reduce payment-related support tickets.

Lead Follow-Up Sequences

When a lead fills out a form on your website, trigger a WhatsApp welcome message immediately. Follow up with a series of messages over the next few days: a product overview on day 1, a case study on day 3, a special offer on day 7. Each message is personalized based on the lead's information.

System Alerts and Monitoring

Use WhatsApp as an alerting channel for your infrastructure. When a server goes down, a database is full, or a job fails, send an automated WhatsApp message to the on-call engineer. WhatsApp messages get read within minutes, making them more reliable than email for time-sensitive alerts.

How to Build WhatsApp Automation

Building automation with our API follows a simple pattern: trigger → process → send.

Step 1: Define Your Triggers

What events should trigger a WhatsApp message? Common triggers include:

• A new order placed in your e-commerce system
• An appointment scheduled in your booking system
• A payment processed in your payment gateway
• A status change in your database (order shipped, ticket resolved, etc.)
• A cron job running on a schedule (daily digest, weekly report, etc.)
• An incoming webhook from another service (Stripe, Shopify, WordPress, etc.)

Step 2: Build the Processing Logic

When a trigger fires, your code needs to determine what message to send and to whom. This usually involves:

• Looking up the customer's phone number from your database
• Gathering the relevant data (order details, appointment time, amount, etc.)
• Composing the message with the customer's information
• Choosing the right message format (text, image, document, etc.)

Step 3: Send via the API

Call our API to deliver the message. Here is a PHP example for an order confirmation:

<?php
// Order confirmation automation
$order = getOrderFromDatabase($orderId);
$customer = getCustomerById($order['customer_id']);

$ch = curl_init('https://api2whats.com/send-text');
curl_setopt_array($ch, [
    CURLOPT_POST => true,
    CURLOPT_HTTPHEADER => [
        'Authorization: *** ' . API_KEY,
        'Content-Type: application/json',
    ],
    CURLOPT_POSTFIELDS => json_encode([
        'to' => $customer['phone'],
        'message' => "Hi , your order # is confirmed!\n"
            . "Total: \$\n"
            . "We will ship it within 24 hours.",
    ]),
    CURLOPT_RETURNTRANSFER => true,
]);
$response = json_decode(curl_exec($ch), true);
curl_close($ch);

// Log the message ID for tracking
logOrderMessage($order['id'], $response['data']['id']);

Step 4: Handle Responses

Set up a webhook to receive replies. When a customer responds to your automated message, your webhook handler receives it. You can then route the response to the appropriate team, trigger a follow-up flow, or have a chatbot handle it.

Automation Patterns

One-Way Notifications

The simplest pattern: send a message and do not expect a reply. Use for confirmations, alerts, reminders, and status updates. Low complexity, high reliability.

Two-Way Conversations

Send a message and handle the reply. Use for customer support, order inquiries, and interactive flows. Requires webhook setup and response handling logic.

Scheduled Campaigns

Send messages to multiple recipients on a schedule. Use for marketing campaigns, weekly digests, and recurring notifications. Implement with a cron job that queries your database and sends messages in batches with rate limiting.

Event-Driven Workflows

Chain multiple messages based on customer behavior. Send a welcome message, wait 24 hours, send a follow-up, wait 3 days, send a special offer. If the customer replies at any point, branch to a different flow. This requires state management and a workflow engine.

Scaling Your Automation

When you move from testing to production, there are several things to consider:

• Rate limiting — Send messages with delays between them (2-3 seconds). Do not blast 1000 messages in 10 seconds.
• Error handling — What happens if the API returns an error? Retry with exponential backoff. Log failures for investigation.
• Deduplication — Ensure you do not send the same message twice. Use unique IDs and check before sending.
• Queue management — For high-volume automation, use a message queue (Redis, RabbitMQ, SQS) to buffer outgoing messages and process them at a controlled rate.
• Monitoring — Track delivery rates, response times, and error rates. Set up alerts for anomalies.

Integrations

Our API integrates with any system that can make HTTP requests. Popular integrations include:

• E-commerce — Shopify, WooCommerce, Magento, custom platforms
• CRM — Salesforce, HubSpot, Zoho, custom CRM systems
• Payment — Stripe, PayPal, Plisio, custom payment processors
• Scheduling — Google Calendar, Calendly, Acuity, custom booking systems
• Monitoring — UptimeRobot, Grafana, Prometheus, custom alerting
• Automation — Zapier, n8n, Make (Integromat), custom webhooks

Best Practices for WhatsApp Automation

• Personalize every message — Include the customer's name and relevant details. Generic messages get ignored.
• Provide value — Every message should help the customer. Confirmations, updates, and reminders are valuable. Spammy promotions are not.
• Respect opt-out — If a customer asks to stop receiving messages, stop immediately. Build an unsubscribe mechanism into your automation.
• Keep messages concise — WhatsApp is mobile-first. Long messages get skimmed. Get to the point in 2-3 sentences.
• Test thoroughly — Run your automation in a test environment before going live. Send test messages to your own number first.
• Monitor delivery — If delivery rates drop, something is wrong. Check your message content, sending rate, and number reputation.

Common Automation Mistakes

Here are the mistakes we see most often when businesses set up WhatsApp automation:

Sending Too Many Messages

Just because you can automate does not mean you should send messages constantly. Customers who receive too many messages will block your number or report you as spam. Aim for 2-4 messages per customer per month for promotional content. Transactional messages (order updates, reminders) are exempt from this — customers expect and want those.

Ignoring Replies

If your automation sends messages but your webhook does not handle replies, you are leaving money on the table. When a customer responds to your automated message, that is a signal of interest. Route that response to a human agent or a chatbot that can continue the conversation.

No Fallback for Errors

What happens when the API returns an error? If your automation silently fails, the customer never receives the message. Implement retry logic, error logging, and alerting. If a message fails three times, alert your team so they can investigate.

Hardcoding Phone Numbers

Never hardcode phone numbers in your automation code. Store them in your database and look them up dynamically. This makes it easy to update numbers, handle portability, and manage multiple contact points per customer.

Measuring Success

How do you know if your automation is working? Track these metrics:

• Delivery rate — Percentage of messages successfully delivered. Should be above 95%.
• Read rate — Percentage of delivered messages that were read. WhatsApp shows read receipts.
• Response rate — Percentage of customers who reply to your automated messages. Higher is better.
• Resolution time — How quickly customer issues are resolved through automation vs. manual support.
• Support ticket reduction — How many fewer tickets your team handles after implementing automation.
• Revenue impact — Sales attributed to automated follow-ups, reminders, and promotional messages.

Set up a dashboard to track these metrics over time. If any metric drops, investigate immediately. Automation that does not perform is worse than no automation at all.