Webhook not firing for self-messages (fromMe: true) on same session number
Summary
When a WhatsApp user sends a message to themselves (i.e. opens their own chat and sends a message on the same number that OpenWA is running on), the webhook is not fired. The message does not appear in the webhook receiver at all — not even as a raw payload.
Environment
- OpenWA version: (latest version)
- Node.js version: (latest version)
- OS: Linux (hosted)
- Webhook transport: HTTP POST
Steps to Reproduce
- Register a WhatsApp session in OpenWA on number A
- Configure a webhook with
message.sent, message.received and * events
- From the same device running number A, open the self-chat and send a message
- Observe that the webhook endpoint receives nothing
Expected Behaviour
The webhook should fire with fromMe: true when the session owner sends a message to themselves, just as it fires for messages sent to other contacts.
Actual Behaviour
No webhook event is fired. The endpoint receives nothing. This is confirmed by raw payload logging at the very top of the webhook receiver, before any processing logic — the file is simply not written to.
What Does Work
- Webhook fires correctly for
message.received from other numbers ✅
- Webhook fires correctly for
session.status events ✅
message.sent is registered in the webhook events array ✅- The
* wildcard event is also registered ✅
None of these result in a webhook firing for self-messages.
Use Case
This is needed for owner self-service scenarios — for example, a consultant running an AI booking agent on their business WhatsApp number needs to be able to message their own number to query their schedule, check bookings, or interact with their own AI agent. Without this, the only workaround is to use a second phone number, which is impractical.
Workaround Attempted
Registering message.sent and * as webhook events — neither results in the webhook firing for self-messages on the same session number.
Request
Please either:
- Fire the webhook for self-messages with
fromMe: true so the receiving application can handle them, or
- Provide an alternative API endpoint or event that captures self-messages so they can be processed by the webhook consumer
Otherwise, thank you. This is a magnificent product.
Webhook not firing for self-messages (fromMe: true) on same session number
Summary
When a WhatsApp user sends a message to themselves (i.e. opens their own chat and sends a message on the same number that OpenWA is running on), the webhook is not fired. The message does not appear in the webhook receiver at all — not even as a raw payload.
Environment
Steps to Reproduce
message.sent,message.receivedand*eventsExpected Behaviour
The webhook should fire with
fromMe: truewhen the session owner sends a message to themselves, just as it fires for messages sent to other contacts.Actual Behaviour
No webhook event is fired. The endpoint receives nothing. This is confirmed by raw payload logging at the very top of the webhook receiver, before any processing logic — the file is simply not written to.
What Does Work
message.receivedfrom other numbers ✅session.statusevents ✅message.sentis registered in the webhook events array ✅*wildcard event is also registered ✅None of these result in a webhook firing for self-messages.
Use Case
This is needed for owner self-service scenarios — for example, a consultant running an AI booking agent on their business WhatsApp number needs to be able to message their own number to query their schedule, check bookings, or interact with their own AI agent. Without this, the only workaround is to use a second phone number, which is impractical.
Workaround Attempted
Registering
message.sentand*as webhook events — neither results in the webhook firing for self-messages on the same session number.Request
Please either:
fromMe: trueso the receiving application can handle them, orOtherwise, thank you. This is a magnificent product.