WatsBerry

    Guide

    Slack alerts for WhatsApp carts, campaigns, and wallet

    Paste a Slack Incoming Webhook so WatsBerry posts recovered carts, campaign orders, catalogue payments, finished campaigns, template status, and low wallet, without watching the dashboard.

    By WatsBerry7 min read

    Slack alerts for WhatsApp carts, campaigns, and wallet

    Quick answers

    Is this a full Slack App with inbound chat?
    No. WatsBerry posts outbound ops alerts to a channel via Slack Incoming Webhooks. You do not install a reviewed Slack App or chat with WatsBerry inside Slack.
    Which events can post to Slack?
    Template approved/rejected/disabled; new WhatsApp Catalogue order; Catalogue payment received (Review & Pay); abandoned cart recovered after a WhatsApp recovery send; campaign-attributed order (not cart recovery); campaign finished sending; low wallet; optional copy of a new WatsBerry support ticket.
    Does Slack send WhatsApp messages?
    No. Slack is inbound to your team. Customers still receive official Cloud API messages from the WABA.

    Connect Slack Incoming Webhook alerts to WatsBerry

    1. 1

      Create an Incoming Webhook in Slack

      Open api.slack.com/messaging/webhooks, click Add to Slack, pick the channel (for example #alerts), and Allow. No Slack App review is required for this path.

    2. 2

      Paste the webhook in WatsBerry

      From Integrations → Store & apps → Slack, paste the https://hooks.slack.com/services/… URL, set a channel label, and choose which alerts you want.

    3. 3

      Send a test message

      Use Send test message and confirm a WatsBerry confirmation appears in Slack before you rely on production events.

    4. 4

      Turn on the events your team will act on

      Defaults include recovered carts, campaign orders, finished campaigns, low wallet, catalogue orders/payments, and template status. New support-ticket copies are off unless you need them.

    5. 5

      Keep WhatsApp funded so the events are real

      Low-wallet alerts exist so sends do not stop silently. Meta still bills usage separately from the WatsBerry plan.

    Why Slack sits next to the WhatsApp desk

    WhatsApp work dies when the only person watching the dashboard is on a call. Slack WhatsApp alerts on WatsBerry are outbound posts to your channel when an ops event already happened in the workspace, not a second inbox and not unofficial WhatsApp.

    Connect is Incoming Webhooks (Slack’s docs): about two minutes, no Slack App review. Each organisation pastes its own hooks.slack.com/services/… URL.

    This is official Cloud API ops. Grey “bulk WhatsApp” tools that ask you to scan a QR are a ban-risk path, not this product.

    More integrations: WhatsApp integrations hub. Join the waitlist if you do not have a workspace yet.

    Alert types that actually ship

    You toggle each event on or off after connect.

    Alert When it posts Typical next action
    Template status Meta approves, rejects, or disables a template Open Templates or start a campaign
    Catalogue new order Customer places a WhatsApp Catalogue order Fulfil from WhatsApp Orders
    Catalogue payment received Customer pays a Meta Review & Pay invoice (India: UPI apps such as GPay/PhonePe, or card) Mark fulfilment; this rail is India WhatsApp Payments, not a UAE default
    Abandoned cart recovered Buyer purchases after a WhatsApp recovery message was sent See cart recovery
    Campaign order Purchase attributed to a WhatsApp campaign (not cart recovery) Finance / retarget
    Campaign finished Broadcast completes sending Stop watching the progress bar
    Low wallet Messaging credits run low Top up so sends do not fail mid-campaign, 0% markup
    New support ticket Optional copy when your team opens a WatsBerry support ticket Off by default

    We will not invent a “5× faster ops” metric. The job is: the channel that already has the team sees the event.

    Shopify connect is documented on Shopify WhatsApp integration. Catalogue Pay now detail: payment gateways.

    Connect checklist

    1. Open Integrations → Store & apps → Slack → Connect Slack.
    2. In another tab, Add to Slack, pick #alerts (or similar), Allow.
    3. Paste the webhook, set a channel label (your reference only), choose events, Send test message, then Save & connect.
    4. Disconnect or change alerts anytime from Configure.

    Do not paste the webhook into a public ticket. If all toggles are off, Slack stays connected but nothing posts.

    Ready for official WhatsApp ops alerts? Join the beta waitlist. Then features, solutions, and the integrations hub.

    Frequently asked questions

    Is this a full Slack App with inbound chat?

    No. WatsBerry posts outbound ops alerts to a channel via Slack Incoming Webhooks. You do not install a reviewed Slack App or chat with WatsBerry inside Slack.

    Which events can post to Slack?

    Template approved/rejected/disabled; new WhatsApp Catalogue order; Catalogue payment received (Review & Pay); abandoned cart recovered after a WhatsApp recovery send; campaign-attributed order (not cart recovery); campaign finished sending; low wallet; optional copy of a new WatsBerry support ticket.

    Does Slack send WhatsApp messages?

    No. Slack is inbound to your team. Customers still receive official Cloud API messages from the WABA.

    How do I get this?

    Join /waitlist for invite-only beta, then connect Slack from Integrations. Each organisation uses its own webhook and channel.

    Start 14-day free plan · Pricing · Features

    Related guides

    Ready to grow revenue on WhatsApp?

    Start a 14-day free plan. Join the waitlist for invite-only access. Broadcast, automate, recover carts, and support customers on official WhatsApp Business API.