If you live inside WhatsApp Web for sales conversations and rely on Zoho Bigin to keep your pipeline organised, you have probably felt the constant friction of tab switching. You read a message, flip to Bigin to pull up the contact, scan their deal history, jot a note, add a tag, and then return to the chat to reply. It is a small tax per conversation, but it compounds hard across every conversation in a full sales day.
WaBigin is a free, open-source Chrome extension that removes that friction entirely. It embeds a Zoho Bigin CRM sidebar directly inside WhatsApp Web, so your CRM is already open the moment you start a chat. No tab switching. No copy-pasting phone numbers. No lost context. The project lives on GitHub at github.com/RaghooBokam/WaBigin — try it and share what you want to see next.
Get it from Github
What WaBigin Actually Does
The moment you open an individual WhatsApp Web chat, WaBigin injects a sidebar on the right side of the screen and looks up the contact in Bigin using their phone number or name. If the contact already exists, you instantly see their tags, open deals, notes, and core details. If they do not exist yet, the extension creates the contact automatically so you never lose a lead because someone forgot to add them.
From inside that sidebar you can manage tags with a searchable dropdown that lets you create new ones on the fly, view all open deals, and create new deals with pipeline, stage, amount, and close date filled in — without leaving the conversation. The Notes tab lets you type a fresh note or, in one click, capture the last 30 messages of the WhatsApp chat as a clean formatted note on the Bigin record. The Details tab gives you inline editing for name, phone, email, company, and pipeline stage, plus a sync button that pulls the WhatsApp profile photo into Bigin so the contact record actually looks like a person.
Why WaBigin Matters for Sales Teams
Most CRM hygiene problems are not caused by lazy salespeople — they are caused by friction. The more steps it takes to log a conversation, the less often it gets logged. By collapsing the gap between a WhatsApp conversation and the Bigin CRM record to zero clicks, WaBigin makes the right thing the easy thing. Tags get added in the moment, notes get captured while context is fresh, and deals get created the second a buying signal appears.
WaBigin is also genuinely privacy-friendly. There is no middleman server. The extension talks directly from your browser to Zoho APIs, and OAuth tokens are stored locally. It supports all major Zoho data centres including India, US, EU, Australia, and Japan, so your data stays in your region of choice.
How to Install WaBigin in Five Minutes
Because WaBigin is not yet on the Chrome Web Store, you install it manually in Developer Mode. Clone or download the repo, load the unpacked folder at chrome://extensions, create a Server-based OAuth client in your regional Zoho API Console, paste the Client ID and Client Secret into the extension popup, click Connect to Bigin, and approve the Zoho login prompt. Once connected, open web.whatsapp.com, start any chat, and the Bigin sidebar appears. The README on GitHub walks through every step, including the exact Redirect URI the extension expects.
Under the Hood: How WaBigin Works
WaBigin is a Manifest V3 Chrome extension. A service worker handles the OAuth flow and Bigin API calls, a content script injects the sidebar UI into WhatsApp Web, and a small page-context script reads the active chat from WhatsApp’s internal webpack store so the sidebar always knows which conversation you are in. The permission set is intentionally minimal: storage for tokens and settings, identity for OAuth, alarms to keep the service worker alive for background token refresh, tabs to detect WhatsApp Web, and host permissions limited to Zoho APIs and whatsapp.com.
Help Shape What Comes Next
WaBigin is an early-stage project and the most useful thing you can do right now is try it and share what is missing, what is broken, and what would make it indispensable for your workflow. A few questions worth community input: Would group chat support be valuable, or is one-to-one enough? Should the sidebar surface closed-won and lost deals as historical context? Is 30 messages the right default for capturing a chat as a note, or should it be configurable? Would you want to push WhatsApp media attachments into Bigin records? And which custom field types need inline editing most urgently?
If you spot a bug, have a feature request, or want to contribute code, head to the WaBigin repository on GitHub and open an issue or a pull request. Stars are appreciated, but a description of your real WhatsApp-plus-Bigin workflow is worth far more.
