HTTP
HTTP Trigger – Start Workflows with HTTP Requests
Summary (SEO Meta Description):
The HTTP Trigger in WeHub starts workflows when an HTTP request is received.
Use it to build APIs, capture webhooks, and trigger workflows on demand with custom headers.
Overview
The HTTP Trigger is a standalone Trigger plugin that starts a workflow whenever an HTTP request is sent to its unique endpoint.
It is commonly used to:
- Expose workflows as APIs
- Receive data from external systems
- Trigger workflows on demand with dynamic payloads
Unlike integrations, Triggers do not have multiple actions. When you configure the HTTP Trigger, it automatically acts as the entry point for the workflow.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Label | String | Custom name for the trigger node (e.g., "Patient Intake API"). |
| Header(s) | Key/Value (String) | Define expected HTTP headers. Multiple headers can be added. |
Once published, the workflow exposes a unique HTTP endpoint that external clients can call.
💡 Example Use Cases
- API Gateway → Accept POST requests from external systems into workflows.
- Webhook Listener → Capture webhook events (e.g., Stripe, GitHub, Slack).
- Healthcare → Accept inbound FHIR or HL7 messages via HTTP.
- Data Ingestion → Receive JSON payloads and route them into databases or queues.
FAQ
Q: How is the HTTP Trigger different from the HTTP Processor?
A:
- 🌐 HTTP Trigger → Starts workflows when requests arrive.
- ⚙️ HTTP Processor → Makes outbound HTTP calls to other systems.
Q: Can I add authentication to the HTTP Trigger?
A: Yes. You can configure required headers such as API keys or JWT tokens. The workflow will only process requests that meet these requirements.
Q: Can I return a custom response?
A: Yes. By default, the HTTP Trigger confirms receipt, but you can enrich responses using downstream Processors.
Keywords: WeHub HTTP Trigger, HTTP Workflow Trigger, Webhook Listener, Start Workflow with HTTP, API Trigger Plugin