AsyncAPI channel · Honeybadger · Honeybadger Outbound Webhook Notifications

microsoftTeams

Microsoft Teams integration. Honeybadger posts to a Teams Incoming Webhook URL created via Connectors. The documentation confirms the transport (Incoming Webhook URL) but does not enumerate event types or publish a payload schema, so only the connectivity-level message is described.

Open source AsyncAPI → All Honeybadger channels Honeybadger provider profile
Provider: Honeybadger AsyncAPI: v2.6.0 Spec: Honeybadger Outbound Webhook Notifications Operations: 1 Messages: 1

Channel address

microsoftTeams

Operations

deliverHoneybadgerTeamsNotification
Deliver Honeybadger notifications to a Microsoft Teams Incoming Webhook.

Messages

teams.notification
Notification delivered to a Microsoft Teams Incoming Webhook URL. Honeybadger's documentation confirms the integration uses the Teams Connectors Incoming Webhook transport but does not publish a paylo
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 Naftiko capability, Agent Skill, and MCP server surfaces of the same providers.