HTTP
🌐 HTTP Integration Plugin – Call and Respond to HTTP Services
Summary (SEO Meta Description):
The HTTP Integration Plugin in WeHub enables workflows to interact with external HTTP services.
It provides two actions: Create HTTP Client to call APIs, and HTTP Response to send results back.
Overview
The HTTP Integration Plugin is designed for workflows that need to connect with HTTP-based systems.
It allows you to invoke external APIs and respond to HTTP-triggered workflows seamlessly.
With this integration, you can:
- Call REST endpoints using all major HTTP methods.
- Add headers, payloads, and dynamic paths.
- Send structured responses back to API clients or webhook callers.
⚙️ Available Actions
| Action | Description |
|---|---|
| Create HTTP Client | Invoke external HTTP services with configurable methods, paths, payloads, and headers. |
| HTTP Response | Send a structured response back to the caller of an HTTP-triggered workflow. |
💡 Example Use Cases
- Healthcare → Call a FHIR API to fetch patient data, then return normalized results.
- Finance → Post transaction data to a payment API, and send back a confirmation response.
- Ops → Handle incoming webhook requests, enrich them, and reply with status codes.
- ETL → Push processed workflow outputs to an API and provide feedback to the caller.
FAQ
Q: Do I need to use both actions in one workflow?
A: Not always. Use Create HTTP Client when calling external APIs, and HTTP Response only if the workflow was triggered by HTTP and must return data.
Q: Can I pass dynamic values in the request?
A: Yes. Path, headers, and payload fields support workflow context variables.
Q: What happens if no HTTP Response is defined?
A: The workflow ends silently, and the caller does not receive a response.
Keywords: WeHub HTTP Integration, HTTP Client, HTTP Response, REST API integration, webhook response