I’m building a WhatsApp Cloud API integration and want to log inbound and outbound WhatsApp messages against contacts in monday CRM.
I initially explored using the Emails & Activities timeline but wasn’t sure whether that’s the intended or supported approach for external messaging platforms.
At a high level, what’s considered best practice for handling WhatsApp-style conversations in monday?
Should this be done via timeline items, updates, subitems, or a dedicated board?
Just looking for guidance on the most scalable and supported architecture.
Hey there!
For WhatsApp-style conversations, the most scalable pattern I’ve seen is to treat messaging as its own data model, then link it back to Contacts (and optionally Deals).
A practical setup looks like this:
Option A (most scalable)
Use a dedicated “Conversations” board.
Each item is one WhatsApp thread (usually Contact + phone number, or Contact + Deal).
Connect it to the Contact item using a Connect Boards column.
Store high-level fields on the conversation item like channel, owner, status, last message time, last message preview.
Then store the individual messages either:
As subitems on the conversation item (one subitem per message, with direction, timestamp, sender, message type, body, attachment URL), or
Externally (database/log tool) and only write summaries + last message back to monday, if you expect very high volume.
Option B (simplest inside the CRM UI)
Log messages as Updates on the Contact item.
This keeps everything visible where reps already work, but it can get noisy fast if you’re logging every single message.
A common compromise is one update per “session” (for example, bundle messages into one update every X minutes, or one update per day per contact) and include a link to the full thread elsewhere.
Why I’d avoid relying on Email & Activities as the core store
It can work for lightweight logging, but if you’re building a full WhatsApp integration, you’ll usually want more structure than a timeline entry gives you (threading, last message, assignment, SLA, message metadata, attachments, etc.).
If you want one clear recommendation
Start with a Conversations board + subitems for messages, connected back to Contacts.
It stays organized, it scales better than dumping everything into Contact updates, and you can still mirror “last message” and “last activity date” onto the Contact for visibility.
If you share expected volume (messages per day, number of active threads), I can suggest whether subitems are fine or if you’ll be happier storing the message log externally and syncing only summaries into monday.
If you’d like hands-on help or want us to walk through this live, you can book a 1:1 paid 60-minute strategy session with our team here: Calendly
