AsyncAPI channel · 6sense · 6sense AI Email Webhooks

/

The single endpoint all AI Email events are delivered to.

Open source AsyncAPI → All 6sense channels 6sense provider profile
Provider: 6sense AsyncAPI: v3.0.0 Spec: 6sense AI Email Webhooks Operations: 3 Messages: 3

Channel address

/

Operations

receive
receiveConversationEnded
Conversation reached a terminal state.
receive
receiveEmailSent
The AI email agent sent an email to a lead.
receive
receiveLeadMarkedDoNotContact
A lead was marked Do Not Contact.

Messages

conversation.ended
Triggered whenever a conversation status changes to a terminal status. May fire more than once for the same conversation.
Content-Type: application/json
email.sent
Triggered whenever an email is sent by the AI email agent.
Content-Type: application/json
lead.marked_do_not_contact
Triggered whenever a lead is marked Do Not Contact. This cannot be reverted; treat as an authoritative suppression signal.
Content-Type: application/json

About AsyncAPI

The AsyncAPI specification describes event-driven APIs the way OpenAPI describes request/response APIs. A channel is the named pipe — a webhook URL, a Kafka topic, a WebSocket route, an MQTT subject — that producers and consumers publish or subscribe to. Each channel carries one or more messages with structured payloads, and an operation declares whether a given party sends or receives on that channel.

Browse every event-driven channel on the APIs.io network or compare with the broader Agent Skill and MCP server surfaces of the same providers.