Automation Logs gives you detailed insight into your Webhook activity—specifically focused on tracking messages sent through external systems like HubSpot using webhook API calls.
Now when you send messages, you can check the automation logs to confirm delivery, identify failures, or analyze performance within Salesmsg.
Note: This feature currently supports HubSpot “Send Message” Webhook Actions only.
How It Works
When a webhook triggers an SMS from an external system (like a HubSpot workflow), that request is logged in the Automation Logs.
Each webhook call is recorded as an individual row with a unique ID, so you can see exactly what was sent, when, and whether it succeeded.
Webhook Stats Dashboard
A centralized dashboard showing all webhook-based activity with 30-day data retention. you can deep dive into any detailed action views where you can click on any row to view full payload and response data. Ideal for developers troubleshooting API issues.
As well as Keep yourself on track with Real-Time Status Updates as statuses are updated live where you can check for waiting, executed, or failed messages instantly.
Individual Webhook Request Tracking
with Contact Handling imbedded in the request tracking you can Identify which contact the webhook message was sent to. Opted-out or blocked contacts are marked accordingly.
Each webhook appears as its own row with a unique callback/request ID, so you can trace the exact status of every call.
Full Execution Details
You can customize you search columns to choose which columns to display.
Within the details you can view the Automation logs:
Source
Contact info (or anonymized if opted-out)
URL & Entity ID
Execution Status
Timestamp
Failure reasons (if any)
Result (Success, Failed, Waiting)
Advanced Search & Filtering
Find webhook requests by:
Contact name
Request ID
Source system
Status (Waiting, Executed, Failed)
Date range
Frequently Asked Questions
What exactly are "webhook stats"?
These are statistics for messages sent to Salesmsg via webhook API calls from external systems, not messages sent directly through Salesmsg's interface.
How is this different from regular broadcast stats?
Broadcast stats are for messages sent directly from Salesmsg's interface, while webhook stats show results from external systems calling our API.
How is this different from HubSpot workflow stats?
This is the webhook stats dashboard—it shows API call results. HubSpot workflow stats are a separate dashboard for tracking workflow performance.
Why was this feature needed?
Previously, users had no way to see SMS statistics for messages sent through webhook API calls, making it impossible to track delivery, failures, or performance.
How far back does the data go?
Logs are available for the last 30 days only.
What happens with multiple webhook calls?
Each webhook API call appears as a separate row with its own unique identifier, so you can see exactly what happened with each request.
Can I see why webhook calls failed?
Yes, the Result column shows detailed failure reasons, and you can click any row to see the full webhook payload.
What if contact names are missing?
For opted out or blocked contacts, the system may not display contact names, showing a dash instead.
Does this work with all webhook actions?
Currently focused on "Send Message" actions via webhook, with potential expansion to other action types in the future.
Can I export this data?
CSV export is currently out of scope but may be added in future iterations.
How do I access this feature?
Go to Settings > App Marketplace > Automation Logs tab (must have feature flag enabled).
What if I see "Waiting" status?
This means the webhook request was received but hasn't been processed yet; check back later or contact support if it remains stuck.
Related Articles
Need Help? ✋🏻
Contact us on live chat or send an email to us at [email protected].