Sign inStart your trial

WhatsAppWhatsApp
01Integration field card

WhatsApp Automation, Approvals & Workflow

Run WhatsApp on autopilot. Keep the veto.

17 actions1 trigger

A message fires to 200 customers before you noticed the template had the wrong order number. Rills proposes every WhatsApp send; you approve before it goes out.

Try the approval demo

Interactive. No signup. 14 days free · approvals always free.

Powered by Composio
02. The trust layer

Most automation fires first, asks later. Rills shows you the change before it ships.

Every consequential communication action from WhatsApp arrives on your phone first. Approve in seconds. Decline without explaining yourself. Workflows wait, paused at zero cost, until you decide.

Queue 3

WHATSAPP · CAMPAIGN SEND
82

Send template message to 340 post-purchase contacts?

340 contacts · order fulfilled >= 3d, no follow-up sent

Template: order_followup_v3 · last used 6d ago, 0 complaints

Same segment size as previous Tuesday send

SWIPE → APPROVE
Illustrative. Your real proposals match your data and your approval history.
  1. Free to wait. Free to think.

    Approvals and logic don't cost a credit. Pause a workflow for three hours or three weeks. The price is the same: zero. You only pay when something real happens: an AI call, an outbound action.

  2. Approve from your phone in five seconds.

    Swipe right when you're sure. Decline when you're not. Between meetings, mid-coffee, on the train. No dashboard to babysit, no inbox triage, no 3am stomach-drop wondering what shipped while you slept.

  3. Routine cases graduate themselves.

    Every approval feeds a confidence score for that exact workflow shape. The obvious cases (the ones you've green-lit fifty times) start running on their own. The judgment calls still come to you.

03. Overview

About WhatsApp automation

Customer messages queue up fast: order confirmations, support follow-ups, broadcast campaigns. The ones that go out wrong, with a broken template or the wrong recipient list, are the ones customers screenshot and share.

When WhatsApp runs unsupervised

An unchecked WhatsApp automation doesn't pause to ask if this is the right moment. It sends.

  • Send template message fires a promotional blast to a stale segment before you've confirmed the offer is still valid.
  • Create message template goes live with a placeholder variable still in the body copy, and the first customer to receive it sees "Hi {{1}}".
  • Send interactive buttons ships a call-to-action pointing to a URL you've since retired.
  • Send media sends a product image from a previous campaign to the wrong audience cohort.
  • Delete message template removes an active template mid-campaign, breaking every queued message that references it.

What Rills does inside WhatsApp

Rills watches for the conditions you've defined, then surfaces a proposed action: send this template to this list, or create this new message template, before anything reaches a customer. You review the recipient count, the template body, and the send timing, then decide.

The message still sends; you just see it first.

When WhatsApp events should and shouldn't act on their own

The WHATSAPP_MESSAGE_STATUS_UPDATED_TRIGGER fires on every delivery, read, and failure event. Some status changes are routine enough to handle without a second look; others carry enough risk that you want to be the one who decides what happens next.

  • Message delivered status: routine confirmation with no customer-facing consequence; a safe candidate for autonomous logging or CRM updates.
  • Message read status: signals engagement, but acting on it automatically (sending a follow-up via send message) risks coming across as surveillance-level responsiveness.
  • Message failed status: always needs a human call. Whether you retry with send template message, escalate to a support channel, or let it sit depends on context no model should decide alone.
  • Bulk status sweep across a campaign: when dozens of failures surface at once, the right response isn't an automated re-send; it's a review of what went wrong before anything fires again.
04. Triggers

What wakes Rills up in WhatsApp

When these events fire, Rills proposes the next move and waits for your call.

  • webhook

    WHATSAPP MESSAGE STATUS UPDATED

    Fires when a WhatsApp message delivery status changes (such as sent, delivered, or read). This trigger requires you to configure a webhook endpoint to receive real-time status notifications from WhatsApp, as the system cannot directly poll for status updates.

05. Actions

What Rills can do in WhatsApp

4 of 17 actions across reads, writes, and updates.

  1. 01

    Send media

    Send images, videos, or documents to WhatsApp contacts who have messaged you first, enabling you to share visual content and files directly through WhatsApp conversations.

  2. 02

    Send message

    Send text messages directly to WhatsApp users who have recently engaged with your business, enabling direct communication without email or phone calls.

  3. 03

    Send template message

    Send pre-approved WhatsApp message templates to customers, enabling you to deliver consistent, branded communications at scale without building messages from scratch.

  4. 04

    Create message template

    Set up reusable message templates for your WhatsApp Business Account that comply with WhatsApp's policies, enabling you to send marketing messages and messages outside the standard conversation window once approved.

06. FAQ

Common questions about WhatsApp automation

07. NEXT MOVE

Approve every WhatsApp change before it ships.

14 days free. No credit card. About 90 seconds to your first proposal.