HTTPChannel
HTTP Channel Trigger – Receive and Process Incoming HTTP Requests
Summary (SEO Meta Description):
The HTTP Channel Trigger in WeHub listens for incoming HTTP requests and starts a workflow.
Configure headers, static responses, and optional source queue settings for scalability and reliability.
Overview
The HTTP Channel Trigger allows a workflow to start whenever an incoming HTTP request is received.
It is ideal for webhooks, API integrations, or custom event ingestion pipelines.
With optional source queue support, you can buffer and scale request handling across multiple threads.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the trigger node. |
| Header(s) | String | Add one or more headers that must be present in the incoming request. |
| Static Response | String | Optional response body sent back immediately after receiving the request. |
| Source Queue (Toggle) | Boolean | Enable to route requests through an internal queue for controlled processing. |
Source Queue Options (if enabled)
| Field | Type | Description |
|---|---|---|
| Queue Buffer Size | String/Int | Defines buffer size for the queue (e.g., 64 kb). |
| Receive Timeout | Integer | Time (in ms) to wait for new messages before timeout. |
| Maximum Processing Threads | Integer | Number of worker threads allowed to process queued requests. Default: 256. |
💡 Example Use Cases
- Webhook Listener → Receive events from third-party apps like Stripe, GitHub, or Twilio.
- API Gateway → Act as an HTTP entry point for triggering downstream workflows.
- High-Volume Traffic → Enable Source Queue to buffer requests and avoid workflow overload.
- Testing & Debugging → Return a Static Response for quick acknowledgment in integration testing.
FAQ
Q: What happens if Static Response is empty?
A: The request will be acknowledged with a default 200 OK status.
Q: When should I enable Source Queue?
A: Use Source Queue when handling bursty traffic, high throughput, or when workflows may take longer to process.
Q: Can I add multiple headers?
A: Yes, you can add multiple headers. Each must be included in the incoming request for the workflow to trigger.
Keywords: WeHub HTTP Trigger, HTTP Channel, Workflow API Trigger, Webhook Listener, Source Queue, Workflow Automation