HTTP Client¶
HTTP Client calls an external HTTP API from a workflow. Use it to fetch data or send results to another service, then inspect the response status and content in downstream nodes.
- Category: Tool
- Purpose: Sends HTTP requests to any endpoint
- Inputs:
method,url,headers,params,body,auth_type,auth_token,timeout,template_context - Outputs:
response,status_code,content,headers,success,documents - Configuration — Basic:
- URL: Target address (required)
- HTTP Method:
GET(read),POST(create),PUT(full update),PATCH(partial update),DELETE(remove). DefaultGET - Content Type:
application/json,application/x-www-form-urlencoded,text/plain. Default JSON - Configuration — Auth:
- Authentication:
none,bearer,basic,api_key. Defaultnone - Token/Key: Value for Bearer or API Key authentication
- Username / Password: Values for Basic authentication
- Configuration — Advanced:
- Timeout: 1–300 seconds, default 30
- Max Retries: 0–10, default 3. Retrying is safe for GET; set to 0 for POST and DELETE to avoid duplicate operations
- Retry Delay: 1–1000 seconds, default 1
- Verify SSL: Default on
- Enable Templates: Default on. Allows
${{ }}expressions in the URL, headers, and body - Configuration — Data:
- Custom Headers: Additional headers as JSON
- URL Parameters: Query parameters as JSON
- Request Body: Payload for POST, PUT, and PATCH
- Usage: Unlike other tool nodes, this one is a processor — it runs on its own and does not need an agent.