AsyncAPI channel · Argo · Argo Events

/webhook/{eventName}

HTTP webhook channel for receiving events from external systems such as GitHub, GitLab, Bitbucket, or custom HTTP callers. Each EventSource can define multiple named webhook endpoints on different ports.

Open source AsyncAPI → All Argo channels Argo provider profile
Provider: Argo AsyncAPI: v2.6.0 Spec: Argo Events Operations: 1 Messages: 3

Channel address

/webhook/{eventName}

Parameters

Operations

receiveWebhookEvent
Receive an HTTP webhook event

Messages

GitHubEvent
A GitHub webhook event payload
Content-Type: application/json
GitLabEvent
A GitLab webhook event payload
Content-Type: application/json
WebhookEvent
A generic HTTP webhook payload received by an EventSource
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.