Aug 2026Browser ExtensionsIn production1 min read

WhatsApp Web CRM Sidecar

Sales reps' WhatsApp Web conversations never reached the CRM, and WhatsApp has no API for it. I built a Manifest V3 Chrome extension that finds WhatsApp's internal stores at runtime, syncs chats and call history in the background, and never changes the chat a rep is looking at.

Capturing WhatsApp Web conversations into a CRM with no official API

JavaScript / Chrome Extensions (MV3) / Web Reverse Engineering

Official API used
None: WhatsApp Business API does not cover reading a live personal Web session
Store discovery
Named module lookup first, structural matching as fallback
UI impact during sync
None: active chat verified unchanged across a full history page

Milestone Timeline

  • Runtime store discovery

    Located WhatsApp Web's Chat/Msg/Contact/Conn stores inside a minified webpack bundle by structural shape matching.

  • Two-tier rewrite

    Switched to exact module-id lookup after a structural-typing false positive, keeping shape matching as a degradation path.

  • Background catch-up

    Replaced UI-driven chat switching with direct history paging against the store.

What it does

A sales rep opens WhatsApp Web, and the conversation they are already having becomes a CRM lead: messages, contact identity, and call history synced in the background, without leaving WhatsApp and without the rep clicking anything per chat.

The constraints, design decisions and outcomes are in the full case study.

What it demonstrates

Reverse-engineering a moving target and then designing for the fact that it moves, including disproving my own first hypothesis rather than shipping around it. The reusable part was extracted into a standalone package with its own reverse-engineering notes, so the findings outlive the extension.

Scope: this is a read-path CRM sync tool. It never sends WhatsApp messages and is deliberately not a bulk-messaging or anti-ban automation product.