Event Types
The 8bit-ai platform fires webhook events for a variety of actions across conversations, agents, sessions, and account management. Each event has a unique type identifier and a structured JSON payload.
Event Naming Convention
resource.action — for example,conversation.created or message.received. All event names use lowercase dot notation.Available Event Types
Here are all the webhook event types you can subscribe to:
Conversation Events
| Event Type | Description |
|---|---|
| conversation.created | A new conversation has been initiated with an agent |
| conversation.updated | Conversation metadata (tags, custom fields, status) has changed |
| conversation.ended | A conversation has been closed or resolved |
| conversation.rating | A user has submitted a rating or feedback for a conversation |
| conversation.escalated | Conversation was escalated to a human agent |
Message Events
| Event Type | Description |
|---|---|
| message.received | A new message has been received from a user |
| message.sent | The AI agent has sent a response message |
| message.failed | Message processing failed due to an error |
Agent Events
| Event Type | Description |
|---|---|
| agent.deployed | An agent has been deployed to production |
| agent.updated | Agent configuration has been modified |
| agent.undeployed | Agent has been taken down from production |
| agent.error | Agent encountered a critical error requiring attention |
Session Events
| Event Type | Description |
|---|---|
| session.started | A new user session has been created |
| session.ended | A user session has expired or ended |
Account Events
| Event Type | Description |
|---|---|
| account.usage_threshold | Account usage has crossed a defined threshold (e.g., 80% of credit limit) |
| account.billing_updated | Billing plan or payment method has changed |
Event Payloads
All webhook events share a common envelope structure with event-specific data in thedata field.
Common Envelope
conversation.created
message.received
agent.deployed
Event Filtering
Configure which events your webhook endpoint should receive by selecting specific event types during webhook setup. This reduces unnecessary traffic and simplifies event processing.
- Selective subscription — Choose individual event types or subscribe to all events in a category using wildcards like
conversation.*. - Environment filtering — Receive events from production, staging, or development environments independently.
- Multiple endpoints — Configure different endpoints for different event categories (e.g., one endpoint for conversations, another for agent events).
Wildcard Subscriptions
* to subscribe to all events, or conversation.* to subscribe to all conversation-related events. This is useful for catch-all logging endpoints.Testing Events
The webhook dashboard provides a built-in testing interface. You can send test events to your endpoint without triggering real platform actions.
Test Event Endpoint
Test Event Request
Test events are signed and delivered exactly like real events, allowing you to validate your signature verification and event handling logic before going live.
Webhook Delivery Logs