AsyncAPI channel · Celigo · Celigo integrator.io Webhook Listeners

/

A single integrator.io webhook listener endpoint. The same URL accepts any payload the configured source application sends; integrator.io passes the request body and headers into the bound real-time flow. Provider-specific listener templates documented by Celigo include Shopify, HubSpot, and Slack, along with a generic "Webhook" application type for any other source that can deliver HTTP POST or

Provider: Celigo AsyncAPI: v2.6.0 Spec: Celigo integrator.io Webhook Listeners Operations: 1 Messages: 4

Channel address

/

Operations

publish
receiveWebhookEvent
Source application delivers a webhook event to integrator.io.

Messages

GenericWebhookEvent
Any HTTP POST/PUT body delivered to a generic webhook listener.
Content-Type: application/json
ShopifyWebhookEvent
Real-time event delivered by Shopify to a Shopify-typed listener.
Content-Type: application/json
HubSpotWebhookEvent
Event batch delivered by HubSpot to a HubSpot-typed listener.
Content-Type: application/json
SlackWebhookEvent
Event delivered by Slack to a Slack-typed listener.
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.