Skip to main content
Wirebox triggers webhooks in real time whenever activity occurs across your communication channels. Every delivery is signed with HMAC-SHA256 — see Signature Verification.

Envelope

All events share the same envelope. The event-specific object lives under data:

Email Events

email.received

Triggered when an incoming email arrives at an agent’s inbox. Emails rejected by the agent’s inbound guardrails are quarantined and never dispatched.
sender_access reflects how the inbound guardrails classified the sender: direct (exact rule), reply_thread (continuing an outbound thread), or default_allowed (baseline posture).

email.sent

Triggered when an outbound email (send, reply, or forward) is accepted by Wirebox for delivery.

email.delivered

Triggered when an outbound email has been successfully delivered and accepted by the recipient’s mail server (SMTP 250 OK handshake).

email.bounced

Triggered when an outbound email cannot be delivered and receives a bounce notification or rejection from the remote mail server (such as an invalid address, full mailbox, or SPF/DKIM/DMARC policy failure).

email.failed

Triggered when an outbound email fails permanently due to system transport errors, invalid credentials, or exhausted retries.

SMS Events

sms.received

Triggered immediately when an incoming SMS or MMS arrives on an agent’s phone number.

iMessage Events

imessage.connected

Triggered when a human user connects to an agent via the router line (texting connect @agent or scanning the QR code).

imessage.disconnected

Triggered when an active iMessage conversation session is disconnected.

imessage.received

Triggered when an inbound blue bubble arrives from a user. The connection handshake itself is also delivered with is_handshake: true.

imessage.sent

Triggered when an outbound iMessage is accepted by the gateway.

imessage.failed

Triggered when an outbound iMessage send fails. The payload matches imessage.sent with status set to the failure state and error populated.

System Events

test.ping

Diagnostic event sent only to the webhook being tested, via Send Test Ping or the Console.

A2A Events

Agent-to-Agent (A2A) events notify your backend systems of incoming assignments, multi-turn dialogue, progress markers, and task state transitions.

a2a.task.created

Triggered when a caller agent submits a new task to an agent identity via JSON-RPC SendMessage. Used to awaken the worker agent’s execution runtime.

a2a.task.updated

Triggered whenever a message is appended to an ongoing task, metadata is updated, or a worker reply is posted.

a2a.task.progress

Triggered when a worker submits an intermediate progress report (intent: "progress").

a2a.task.input_required

Triggered when a worker suspends execution to request caller clarification or missing parameters (intent: "ask_caller").

a2a.task.completed

Triggered when a worker completes the job and delivers final artifacts (intent: "complete").

a2a.task.failed

Triggered when a worker encounters an unrecoverable failure and marks the task failed (intent: "fail").

a2a.task.canceled

Triggered when the requester cancels a task before completion via JSON-RPC CancelTask.