Wacrm is a complete, production-ready CRM template built on Next.js and Supabase that turns WhatsApp Business into a team collaboration tool. Fork the repo, fill in your credentials, and deploy — you own every line of code, every row of data, and every dollar you save on SaaS seat fees.Documentation Index
Fetch the complete documentation index at: https://mintlify.com/ArnasDon/wacrm/llms.txt
Use this file to discover all available pages before exploring further.
Quickstart
Clone, configure, and run Wacrm locally in five minutes.
Environment Variables
Every variable Wacrm reads, with explanations and defaults.
Supabase Setup
Create your project, run migrations, and configure RLS.
WhatsApp Setup
Connect the Meta Cloud API and register your webhook.
API Reference
Drive your CRM programmatically with the public REST API.
Automations
Build no-code workflows that trigger on messages, contacts, and schedules.
What’s included
Wacrm ships as a full-stack Next.js 16 application with these modules ready to use:Shared Inbox
Multiple agents, one WhatsApp number. Assign, track status, and leave notes.
Contacts
Tags, custom fields, CSV import, and deduplication by phone number.
Pipelines
Kanban sales boards with deals linked to WhatsApp conversations.
Broadcasts
Send approved templates to thousands of contacts with delivery tracking.
Flows
Interactive WhatsApp conversations with buttons, lists, and branching.
AI Agents
BYOK assistant (OpenAI/Anthropic) with knowledge base and auto-reply.
How it works
Fork and clone
Fork ArnasDon/wacrm on GitHub, then clone your fork locally.
Configure credentials
Copy
.env.local.example to .env.local and fill in your Supabase URL, anon key, service role key, encryption key, and Meta app secret.Run migrations
Apply the 30 SQL migration files in
supabase/migrations/ against your Supabase project to create the full schema.Connect WhatsApp
Register your Meta Cloud API phone number, point the webhook at
/api/whatsapp/webhook, and paste your token into the Settings page.Wacrm is a template, not a managed service. You own the code, the database, and the data. Forking is the expected flow — customise freely.