Shared Inbox
Real-time WhatsApp threads with templates, reactions, quote-replies and internal notes.
The open-source WhatsApp CRM template — shared inbox, contact hub, sales pipelines, broadcasts, and no-code automations. Fork it, brand it, self-host it on your own infrastructure.
Stop stitching together an inbox, a spreadsheet, and a broadcast tool. Zappix brings them together — and talks to WhatsApp natively.
Real-time WhatsApp threads with templates, reactions, quote-replies and internal notes.
Address book with manual add, CSV import, tags, and rich contact detail views.
Multi-board Kanban deals with drag-drop stages and win-rate analytics.
Build, submit and edit WhatsApp templates in-app — with live Meta approval status.
Bulk-send approved templates with a 4-step wizard and per-recipient delivery tracking.
Event-driven step chains — auto-replies, lead routing, tag reactions, webhook fan-out.
Branching, button-driven WhatsApp chatbots — no-code, with human handoff.
Bring-your-own-key AI: drafted replies, auto-reply bot, knowledge base from your docs.
Invite teammates, role-based access, ownership transfer — turn solo CRM into a team.
No proprietary black box, no monthly per-seat rugpull. Just a working template you own.
Clone the open-source repo from GitHub. Full source, MIT-licensed, yours to brand.
Point it at your Supabase project, register your WhatsApp Business number with Meta.
Ship to Hostinger Managed Node.js in about 30 seconds. Or anywhere Node runs.
Zappix is a template — not a SaaS. You clone the repo, connect your own Supabase project, plug in your Meta app credentials, and deploy it wherever Node.js runs.
$ git clone <your-repo>.git zappix $ cd zappix && bun install $ cp .env.example .env # → Supabase URL, keys # → Meta WhatsApp token, phone_number_id $ bun run db:push ✔ 12 migrations applied $ bun run deploy ✔ built ✔ deployed to crm.yourdomain.com ✔ webhook verified $ ▮
From a fresh fork to a production deploy — pages walk you through every step.
Fork, install, run the template locally in 15 minutes.
ReadCreate the database, apply migrations, grab the keys.
ReadMeta app, access token, webhook verification.
ReadShip the template on Hostinger Managed Node.js.
ReadSchedule the drain so Wait steps resume on time.
ReadREST endpoints, scoped API keys, outbound webhooks.
ReadStill curious? Our team replies on WhatsApp — obviously.
Yes — the whole template is MIT-licensed. Fork it, brand it, extend it, and self-host it on your own infrastructure. No lock-in.
Yes. Zappix is built on Meta's official WhatsApp Business Cloud API. You bring your own WhatsApp Business number and connect it via a standard Meta app.
In your own Supabase project. Zappix never proxies your customer data through our servers — the template talks directly to your database and to Meta's API.
Roughly 30 seconds on Hostinger's Managed Node.js hosting, or however long a git-push takes on any other Node host. Full walkthrough in the docs.
Yes. The Members feature supports invitations and role-based access, and the template is easy to fork per client for a fully white-labelled deployment.
No. Bring your own OpenAI (or compatible) key, drop in your FAQs and product docs, and the assistant drafts replies or runs an auto-reply bot with human handoff.
Clone the repo, wire up Supabase and Meta, deploy. That's the whole setup.