Track what happened, when, and why. Activity logs capture every significant event across your organization — from webhook deliveries to tool executions to agent configuration changes. What you’ll learn: How to search and filter activity logs, understand event types and severities, and use the API for programmatic access.Documentation Index
Fetch the complete documentation index at: https://docs.blackbox.dasha.ai/llms.txt
Use this file to discover all available pages before exploring further.
Access activity logs
- Dashboard
- API
Navigate to Activity Logs in the sidebar to view all events across your organization.
Event types
Activity logs capture events across four categories:Agent lifecycle
| Type | Description |
|---|---|
| AgentCreated | A new agent was created |
| AgentUpdated | An existing agent was updated |
| AgentDeleted | An agent was deleted |
| AgentCloned | An agent was cloned from another agent |
Conversation lifecycle
| Type | Description |
|---|---|
| CallCreated | A conversation was created via REST API or WebSocket |
| CallBulkScheduled | A bulk batch of conversations was scheduled |
| CallCanceled | A conversation was canceled |
| CallCompleted | A conversation completed successfully |
| CallFailed | A conversation failed |
| CallDeadlineExceeded | A conversation exceeded its deadline |
| CallDispatched | A conversation was dispatched to the runner for execution |
| CallReceived | An incoming call was received |
| CallRejectedByWebhook | A conversation was rejected by the start webhook |
Webhooks
| Type | Description |
|---|---|
| WebhookSuccess | A webhook was delivered successfully |
| WebhookFailed | A webhook delivery failed |
Runtime events
| Type | Description |
|---|---|
| ToolCallSuccess | A tool call executed successfully during a conversation |
| ToolCallFailed | A tool call failed during a conversation |
| McpCallExecuted | An MCP (Model Context Protocol) call was executed |
Configuration changes
| Type | Description |
|---|---|
| ConfigurationCreated | A configuration resource was created (provider, SIP, media, integration) |
| ConfigurationUpdated | A configuration resource was updated |
| ConfigurationDeleted | A configuration resource was deleted |
Severity levels
Each event has a severity level indicating its importance:| Severity | Description | Examples |
|---|---|---|
| Info | Normal operation, no action required | Successful webhook delivery, call completed |
| Warning | Something unusual happened but operation continued | Slow webhook response, retry succeeded |
| Error | An operation failed | Webhook timeout, tool call error |
| Critical | Severe failure requiring immediate attention | Authentication failure, system unavailable |
Caller types
Events track who initiated the action:| Caller | Description |
|---|---|
| User | Action initiated by a user via API, dashboard, or web interface |
| System | Action initiated by the platform (scheduler, webhooks, internal processes) |
Filter activity logs
By event type
Filter to specific event types to focus your analysis:Filter by type
Filter by type
By severity
Focus on errors and critical issues:Filter by severity
Filter by severity
By date range
Query events within a specific time window:Filter by date range
Filter by date range
By agent or call
Track events for a specific agent or call:Filter by agent
Filter by agent
Filter by call
Filter by call
Full-text search
Search across event messages and metadata:Text search
Text search
Aggregations
Search results include aggregated counts for quick analysis. These show how events break down by type, severity, and caller across all matching results — not just the current page.API response structure
Search activity logs
Request:POST /api/v1/activity-logs/search
Request body:
| Field | Type | Default | Description |
|---|---|---|---|
page | integer | 0 | Page number (0-indexed) |
size | integer | 20 | Results per page (max 100) |
types | ActivityEventType[] | — | Filter by event types |
severities | ActivityEventSeverity[] | — | Filter by severity levels |
callers | ActivityEventCaller[] | — | Filter by caller (User, System) |
userEmail | string | — | Filter by user email |
callIds | string[] | — | Filter by call IDs |
agentIds | string[] | — | Filter by agent IDs |
fromDate | DateTimeOffset | — | Start of date range |
toDate | DateTimeOffset | — | End of date range |
searchText | string | — | Full-text search query |
sortField | string | ”timestamp” | Field to sort by |
sortDirection | SortDirection | Descending | Ascending or Descending |
Response example
Response example
Common tasks
Find all failed webhooks
Find all failed webhooks
Debug a specific call
Debug a specific call
Monitor tool call failures
Monitor tool call failures
Track agent configuration changes
Track agent configuration changes
Troubleshooting with activity logs
Activity logs are your first stop when debugging issues. Here’s how to approach common problems:Webhook not triggering?
- Search for
WebhookFailedevents for your agent - Check the
metadatafield for error details (timeout, DNS failure, HTTP status) - Verify webhook URL is publicly accessible
Tool calls failing silently?
- Filter by
types: ['ToolCallFailed']and your call ID - Review error messages and response times in metadata
- Check if the tool webhook is responding within the 10-second timeout
Unexpected call behavior?
- Get the full event timeline for the call ID (sort ascending by timestamp)
- Look for warning or error severity events
- Check if
CallRejectedByWebhookorCallFailedevents explain the issue
Activity logs are retained for 90 days. For longer retention or compliance requirements, export logs periodically using the search API.
What’s next
Call History
View and search past calls
Call Inspector
Deep dive into individual calls
Webhook Events
Understand webhook payloads
Testing Webhooks
Test webhook delivery