No public outbound webhooks—yet.

Kona Business AI does not currently publish a general-purpose outbound webhook product for workspace, conversation, generated-item, connector, or workflow events. There is no public endpoint-registration flow, signing-secret lifecycle, event catalog, retry schedule, delivery log, or replay API. Integrators should not infer webhook support from internal product routes, scheduled jobs, or third-party provider callbacks.

The public OpenAPI specification intentionally contains no top-level webhooks declaration and documents only the supported read-only workspace MCP HTTP endpoint. Any future webhook feature would need an explicit public contract covering event names and versions, authentication and signatures, tenant isolation, retries and ordering, payload minimization, observability, deletion, and safe replay before it is represented as supported.

When an agent needs current approved workspace context, use the read-only, workspace-scoped MCP server and make a request at the time the user needs it. For a human-led workflow, use Kona’s Workspace interface and its visible status, review, and generated-item controls. Do not build a polling loop that defeats published limits or treat an MCP token as permission to monitor a workspace indefinitely.

If a business process requires event-driven delivery, keep the event source in a system that already provides an approved webhook and let a person bring the relevant result into Kona, or contact the Kona team to discuss the use case. A custom conversation does not create a production commitment until an applicable implementation and agreement have been reviewed and approved.

A production webhook contract should make subscription ownership, event authorization, payload schema, versioning, HMAC verification, timestamp tolerance, duplicate delivery, retry behavior, ordering guarantees, retention, replay, and disablement explicit. Consumers would need to verify signatures before parsing payloads, use idempotency keys, acknowledge quickly, isolate untrusted fields, and avoid logging secrets or sensitive content.

Until those controls and public documentation exist, describe Kona Business AI as having no public outbound webhook API. Check this page and /openapi.json when planning an integration rather than relying on old screenshots, generated code, or assumptions from similarly named products.