WhatsApp personal number → HubSpot CRM activity sync (messages + call logging)
Budget: $1000.0
FIXED /
⭐ 4.67 (3)
Netherlands
web-application
I am building a multi-user SaaS tool where organisations connect their HubSpot portal and team members individually link their personal WhatsApp numbers. All WhatsApp activity — messages and calls — should sync automatically to HubSpot as CRM activity (timeline events, logged calls).
This is not a WhatsApp Business API project. The requirement is personal WhatsApp numbers, which means working at the WhatsApp Web layer.
What I have already tested
Baileys (Node.js WhatsApp Web library)
Message sync works reliably. Call event logging is partially exposed via sock.ev.on('call', ...) — inbound call events confirmed working. Outbound call mirroring to the Baileys session is unconfirmed and needs to be proven before building on it.
WAHA (WhatsApp HTTP API)
Also tested. Messages work. Call logging has the same limitations as Baileys — same underlying Web layer.
Scope of work
Must have
WhatsApp session management per user (QR code link flow, session persistence, reconnect handling)
Must have
Message sync to HubSpot timeline (inbound + outbound, matched to HubSpot contact by phone number)
Must have
Call logging to HubSpot: direction (inbound/outbound), timestamp, duration, contact matched — must handle the @lid vs @s.whatsapp.net JID resolution problem
Must have
HubSpot OAuth connect flow so each org authenticates their own portal
Nice to have
Voice note logging (flagged as voice note on the HubSpot timeline, duration captured)
Nice to have
Basic admin dashboard: connected users, sync status, last activity per session
Key technical challenges — I expect your proposal to address these
Outbound call mirroring
Does the WhatsApp Web layer reliably mirror outbound call events to a linked Baileys/WAHA session? If not, what is your proposed fallback?
JID to phone number resolution
Call events can return @lid identifiers instead of real phone JIDs. How do you handle contact matching in HubSpot when this happens?
Session stability at scale
Multiple concurrent WhatsApp sessions per deployment. How do you handle reconnects, QR expiry, and session isolation between users?
What I am looking for in a proposal
Demonstrated experience with Baileys or WAHA specifically — not just "WhatsApp integration" generically
Honest answer on whether outbound call events can be captured via the Web layer
HubSpot API experience — specifically timeline events and the calls API
Proposed tech stack and architecture overview (even rough is fine)
Do not apply if your solution relies on WhatsApp Business API — that is not suitable for this use case
Do not apply if you cannot speak to the call logging challenge specifically
Ouvrir sur Upwork