n8n workflow stops capturing user follow-up messages on Meta WhatsApp API. Only the initial reply triggers a webhook. How can subsequent responses be captured? See sample:
[
{
"app": "whatsapp",
"contacts": [
{ "identifier": "", "phoneNum": "" }
],
"message": [
{ "msg_id": "unique-001" }
]
}
]
The issue appears to stem from the way the webhook is being set up in n8n. In my experience, the initial webhook captures the first incoming message properly, but subsequent messages might not be recognized if the conversation context isn’t managed dynamically. I resolved a similar issue by ensuring that the workflow maintains session state through proper context settings in the Meta WhatsApp API. It could be essential to include a persistent identifier or session token that allows n8n to continuously trigger the webhook for new messages.
The observed issue appears to arise from the webhook trigger not recognizing continuation messages as distinct events. In my experience with similar integrations, ensuring that every new message is treated as an independent event rather than just a context extension to an initial session often helps. Adjusting the webhook configuration and session management settings within n8n is critical. It also helps to verify that the Meta WhatsApp API subscription settings are correctly configured to continuously listen for user responses. In-depth logging also provided valuable insights into when and why messages failed to be captured.