kstmostofa

kstmostofa / laravel-whatsapp

Public

Laravel WhatsApp - Dual-backend WhatsApp integration for Laravel. Meta Cloud API + whatsapp-web.js sidecar, behind a single facade, with a polished Livewire admin UI.

kstmostofa.github.iolaravel-whatsapp
11
1
85% credibility
Found May 27, 2026 at 11 stars -- GitGems finds repos before they trend. Get early access to the next one.
Sign Up Free
AI Analysis
PHP
AI Summary

A Laravel package that adds WhatsApp messaging to web applications, supporting both official Meta Business API and personal phone connections via QR code, with a built-in admin dashboard for managing conversations, contacts, groups, and message status.

How It Works

1
💬 You want to add WhatsApp to your app

You discover you need to send and receive WhatsApp messages from your web application.

2
📦 You install the package

You add the package to your Laravel project with one command and it sets itself up automatically.

3
You choose how to connect
🏢
Business account

Connect Meta's official WhatsApp Business service for verified, scalable messaging.

📱
Personal phone

Link your own phone by scanning a QR code to use any WhatsApp features.

4
✉️ You send your first message

With one simple command, your app sends a message to any phone number instantly.

5
📊 You manage everything from your dashboard

A built-in control panel lets you view conversations, manage contacts, check groups, and monitor message status.

🎉 Your app now talks to WhatsApp

Your application can send, receive, and manage WhatsApp conversations — all from one unified interface.

Sign up to see the full architecture

4 more

Sign Up Free

Star Growth

See how this repo grew from 11 to 11 stars Sign Up Free
Repurpose This Repo

Repurpose is a Pro feature

Generate ready-to-use prompts for X threads, LinkedIn posts, blog posts, YouTube scripts, and more -- with full repo context baked in.

Unlock Repurpose
AI-Generated Review

What is laravel-whatsapp?

Laravel WhatsApp is a PHP package that gives your Laravel app the ability to send and receive WhatsApp messages through two different backends: Meta's official Cloud API or a browser-automation sidecar powered by whatsapp-web.js. The killer feature is a single facade that auto-selects the right backend based on the recipient format, so you can use phone numbers for Cloud API sends and WhatsApp internal IDs for personal-number features without changing your code. It ships with a full Livewire admin panel at `/whatsapp` covering sessions, QR pairing, chat history, groups, contacts, and a webhook log. Artisan commands handle sidecar installation, startup, and a long-running daemon that bridges incoming messages into Laravel events.

Why is it gaining traction?

Most WhatsApp packages force you to choose between official compliance (Cloud API) and flexibility (personal number access). This package lets you use both simultaneously. The Cloud API handles scalable transactional messages with templates, while the sidecar handles group chats, status updates, and free-form messages that the official API restricts. The polished admin UI is a major differentiator—it's not just a webhook endpoint, it's a full chat interface with message bubbles, read receipts, edit/delete actions, and dark mode. Health monitoring via `php artisan whatsapp:health` makes production oversight straightforward.

Who should use this?

Laravel developers building customer-facing apps that need WhatsApp as a communication channel. E-commerce teams sending order confirmations via templates will use the Cloud API path, while support teams needing group broadcasts or personal-number automation will use the sidecar. The admin UI makes this viable for non-technical staff to monitor conversations without touching code.

Verdict

This is a well-architected package solving a real architectural problem, with solid documentation and 46 passing tests. The 0.8500000238418579% credibility score reflects a small but active codebase—11 stars is thin community evidence, so production use warrants careful testing against your specific Laravel version. The dual-backend design is clever, but the sidecar introduces operational complexity (Node, Chromium, session management) that may outweigh the benefits if you only need Cloud API features. Start with Cloud API only if your use case supports it.

Sign up to read the full AI review Sign Up Free

Similar repos coming soon.