Skip to content
Proud to collaborate with Microsoft for Startups

control.http.request ​

Make a generic HTTP/REST request so integrations without a first-class workflow are reachable

Overview ​

PropertyValue
Workflow typeAtomic
LibraryApp-control
Version1.0

Input Schema ​

FieldTypeRequiredDefaultDescription
methodstringYes—HTTP method: GET/POST/PUT/PATCH/DELETE
urlstringYes—Target URL (non-empty)
headersjsonNo—Request headers (object or JSON-encoded string)
bodystringNo—Request body, sent as-is (caller encodes it)
timeout_secondsintegerNo—Request timeout in seconds (default 30; capped at 300)
fail_on_http_errorbooleanNo—Fail on 4xx/5xx responses by default; false returns them as outputs

Output Schema ​

FieldTypeRequiredDefaultDescription
methodstringNo——
urlstringNo——
headersjsonNo——
bodystringNo——
timeout_secondsintegerNo——
fail_on_http_errorbooleanNo——
response_status_codeintegerNo—HTTP status. Populated on 2xx, or on any status when fail_on_http_error=false
response_bodystringNo—Response body. Populated on 2xx, or on any status when fail_on_http_error=false
response_headersjsonNo—Allowlisted response headers. Populated on 2xx, or on any status when fail_on_http_error=false
failure_reasonstringNo——
failure_typestringNo——
failed_actionstringNo——
failed_at_statestringNo——
failed_stepstringNo——
failed_layerstringNo——
errorstringNo——
error_typestringNo——

States ​

StateInitialTerminalSuccessAuto-advanceDescription
pendingYesNo—execute—
completedNoYesYes——
failedNoYesNo——

State Diagram ​

Transitions ​

FromActionToDescription
pendingexecutecompleted—
* (any state)failfailed—

API Usage ​

bash
POST /api/workflows/start
Content-Type: application/json

{
  "workflow_type": "control.http.request",
  "initial_data": {
    "method": "value",
    "url": "value"
  }
}