Create-HTTP-Client
🌐 HTTP Integration Plugin – Create HTTP Client
Summary (SEO Meta Description):
The HTTP Integration Plugin’s Create HTTP Client action in WeHub allows workflows to call external HTTP services.
Configure connection, path, method, headers, and payload to integrate with REST APIs.
Overview
The Create HTTP Client action lets you invoke external HTTP endpoints directly from a workflow.
It supports common HTTP methods (GET, POST, PUT, PATCH, DELETE) and allows customization of paths, payloads, and headers.
This action is essential for integrating third-party APIs, sending requests to internal services, or triggering webhooks.
⚙️ Configuration Options
| Field | Type | Description |
|---|---|---|
| Select Connection | Connection | Choose or create an HTTP connection (base URL, authentication). |
| Label | String | Custom name for the node (e.g., "Call FHIR API"). |
| Path | String | Relative path appended to the base URL (e.g., /Patient). |
| Method | Enum | HTTP method: GET, POST, PUT, PATCH, DELETE. |
| Override Path | Boolean (Toggle) | If enabled, dynamically override the configured path at runtime. |
| Static Payload | Boolean (Toggle) | Use a fixed payload instead of workflow context variables. |
| Payload | JSON / String | Request body payload (applies to non-GET methods). |
| Headers | Key/Value (String) | Custom request headers (e.g., Authorization, Content-Type). |
💡 Example Use Cases
- Healthcare → Call FHIR endpoints (
GET /Patient) to fetch clinical data. - Finance → Post transaction records to payment APIs.
- Ops → Trigger a webhook in Slack, Teams, or monitoring services.
- ETL → Push processed workflow results into external systems via API.
FAQ
Q: Can I use dynamic values in path and payload?
A: Yes. Both fields support variable substitution from workflow context.
Q: What happens if the endpoint is unavailable?
A: The action will fail, and error handling/retry policies can be applied.
Q: Is authentication supported?
A: Yes. Authentication is handled via the connection configuration (e.g., API keys, Bearer tokens).
Keywords: WeHub HTTP Integration, HTTP Client, API call, REST integration, webhook