WhatsApp Activity Logs

See What Happened to Your WhatsApp Messages

For support teams, integration owners, and developers responsible for WhatsApp messaging.

Review incoming messages, recorded delivery and failure statuses, message events from campaigns, and webhook activity in Robofy. Filter the Activity Log and open individual event details to understand exactly what was recorded.

  • Message events
  • Failure details
  • Webhook responses
  • 24-hour capture
24-hour event captureIncoming + outgoing API eventsFilter by webhook & phone numberInspect event details
Activity Visibility

What Are WhatsApp Activity Logs?

WhatsApp Activity Logs are records of events that occur while WhatsApp messaging activity is being processed. In Robofy, they can include incoming messages, message status updates, failed-message information, message events from campaigns, and API or webhook activity.

Instead of relying only on summary metrics, you can inspect an individual recorded event to understand what happened at a particular time.

See It Work

See Activity Logs in Robofy

Scroll through a recorded event - from the feed, into the failure, then the payload and webhook response.

  1. 1MessageWhatsApp activity happens
  2. 2EventRobofy records it in the feed
  3. 3EvidenceOpen it for payload + webhook detail
  1. 10:41:53IncomingCustomer message received+91 •••• 1048
  2. 10:42:18DeliveredCampaign message+91 •••• 3921
  3. 10:39:12FailedMessage failedFailure details available
  4. 10:36:44WebhookPOST /whatsapp/status200 OK

Scene 01

The Activity Feed

Incoming messages, delivery statuses, failures, and webhook activity land in one chronological feed.

10:39:12FailedMessage failedOpen the record

Recorded failure information

Status
Failed
Timestamp
2026-09-10T10:39:12Z
Failure reason
Illustrative example: recipient unreachable

Scene 02

A Failed Message

Open the recorded event and review the failure information available for that message.

Incoming event · payload
{
  "event": "incoming_message",
  "from": "+91 •••• 1048",
  "timestamp": "2026-09-10T10:41:53Z",
  "message_id": "wamid.example",
  "type": "text"
}

Scene 03

Incoming Event Payload

Review the captured payload behind an incoming event when you need technical context.

Destination
https://example.com/webhook
HTTP response
200 OK
Delivery status
Delivered
Response body
{ "received": true }

Scene 04

Webhook Delivery

Inspect the destination and available response details associated with the recorded delivery attempt.

All events, IDs, and payloads shown are illustrative demo data.

Recorded Activity

One Feed for the Events Behind Your WhatsApp Messages

A message can generate several kinds of records. Each one appears in the feed when it is captured - not every message produces every state.

  1. IncomingCustomer message received
  2. SentMessage sent
  3. DeliveredMessage delivered
  4. ReadMessage read
  5. FailedFailure information recorded

Message events from campaigns

Review recorded status events associated with messages sent through Robofy campaigns.

Webhook & API events

Inspect supported API and webhook activity when you need additional technical context.

Find the Right Event

Narrow the Feed to What You’re Investigating

Filters apply one at a time so unmatched events fall away until the matching records remain.

6 events in range

  1. 10:42:18DeliveredCampaign message+91 •••• 3921
  2. 10:41:53IncomingCustomer message received+91 •••• 1048
  3. 10:39:12FailedMessage failedDetails available
  4. 10:36:44WebhookPOST /whatsapp/status200 OK
  5. 10:22:05SentCampaign message+91 •••• 7740
  6. 10:18:40ReadMessage read+91 •••• 5568

Apply filters to narrow the feed to the records that match your investigation.

Illustration with synthetic demo data - not customer records.

Event Capture

Turn On Logging When You Need It

23h 42mremaining
Logging enabledCapturing incoming and outgoing API events

Enable Activity Log capture when you want to record events for an investigation. Each enabled capture window lasts 24 hours and logging automatically switches off when the window expires.

You can switch logging off earlier or enable another capture window when needed.

Enable logging before reproducing an issue so the relevant events can be recorded.

How It Works

From an Issue to the Event Behind It

  1. 1

    Enable logging

    Turn on Activity Log capture for a 24-hour window.

  2. 2

    Let the event occur

    Send a test message, receive a message, trigger a campaign message, or reproduce the workflow you are investigating.

  3. 3

    Find the record

    Filter the Activity Feed by date, webhook, phone number, or event category.

  4. 4

    Inspect the details

    Review the status, failure information, payload, and webhook response details available for that recorded event.

Common Investigations

Start With the Question You Need Answered

Technical Detail

Need the Technical Record? Open the Event.

Activity Logs can expose the underlying event data when a high-level status isn’t enough. Inspect the captured payload and available webhook delivery details for further investigation.

Summary

What was recorded

Event
message_status
Status
failed
Timestamp
2026-09-10T10:42:18Z
Phone Number ID
1234567890

Payload

Captured event data

{
  "event": "message_status",
  "status": "failed",
  "message_id": "wamid.example",
  "timestamp": "2026-09-10T10:42:18Z"
}

Webhook response

Delivery details

Destination
https://example.com/webhook
HTTP response
400 Bad Request
Delivery status
Failed
Response body
{ "error": "Illustrative response" }

Illustrative example structure only - not real customer data.

Activity Logs and Analytics Answer Different Questions

Activity Logs

  • Individual recorded events
  • Message statuses
  • Failure information
  • API and webhook evidence
  • Event-level investigation

Analytics & Reporting

  • Aggregated message performance
  • Campaign reporting
  • Totals and rates
  • Trends over time
  • Performance evaluation

Use Activity Logs when you need to understand a specific event. Use reporting when you need to evaluate performance across many messages.

FAQ

Frequently Asked Questions

Straightforward answers about WhatsApp Activity Logs, capture windows, filters, and event inspection.

What does Robofy Activity Log show?

Robofy Activity Log shows supported WhatsApp messaging, API, and webhook events captured while logging is active. This can include incoming messages, message status updates, failed-message details, message events from campaigns, payloads, and webhook delivery information where available.

Can I see why a WhatsApp message failed?

When failure information is included in the recorded event, open the failed-message record to review the available failure reason or details.

Can I see message events from campaigns?

Yes. Activity Logs can show recorded events associated with messages sent through Robofy campaigns, such as message-status updates. Activity Logs are not a history of campaign creation, scheduling, or campaign configuration.

Can I filter Activity Logs by WhatsApp phone number or webhook?

Yes. Use the Webhook and Phone Number ID filters together with the date range and event-category controls to narrow the Activity Feed.

How does the 24-hour logging window work?

When activity logging is enabled, Robofy captures supported incoming and outgoing API events for 24 hours. Logging switches off when that capture window expires, and it can also be turned off earlier.

Can I inspect webhook responses and event payloads?

Yes. Recorded event details can include the payload and available webhook delivery information such as the destination, HTTP response code, delivery status, and response body.

Does the 24-hour capture window mean logs are deleted after 24 hours?

No conclusion about retention should be drawn from the capture setting alone. The 24-hour setting controls the period during which new events are captured. Log retention is separate.

Are Activity Logs the same as analytics or campaign reporting?

No. Activity Logs show individual recorded events. Analytics and campaign reporting summarize performance across many messages over time.

Does Activity Log retry or modify a failed message?

No. Activity Log records and displays event information. It does not resend, retry, or modify the message.

Know What Happened Before You Decide What to Fix

Capture WhatsApp activity, find the relevant event, and inspect the details your team needs to investigate it.