HTTP Request
Call any HTTP or HTTPS endpoint as part of a workflow.
What it does
Makes one HTTP request to a URL with a method of your choice (GET, POST, PUT, DELETE, PATCH), optionally sends a body, and writes the response back to memory. This is the universal glue for integrating with any system that has a web API.
What you configure
| Field | What it controls | Required | Notes |
|---|---|---|---|
| URL | The address to call. | required | Must be a valid HTTP or HTTPS URL. |
| Method | The HTTP method. | required | GET, POST, PUT, DELETE, or PATCH. |
| Body (memory input) | The request body. | optional | Used for POST, PUT, PATCH. Pull from memory; typically a JSON string assembled in a prior step. |
| Results (memory output) | Where the response body is stored. | required | A later step can parse or forward it. |
📷 SCREENSHOT: The HTTP Request step with URL, method dropdown, body memory selector, and result memory output.
Example scenario
Trigger an external system after an AI decision. A workflow uses an LLM Prompt to decide whether an issue is urgent. If yes, a follow-up HTTP Request step calls your incident-management API to create a ticket. If no, the workflow ends quietly.
Recommendations
- ✅ Always use HTTPS for any non-internal address.
- ✅ Capture the response in memory even if you don't think you need it. The Jobs view will show it, which helps debug failed runs.
- ✅ If the endpoint requires authentication, prefer the Database Query or vendor-specific integrations when available — they handle credentials more cleanly. For headers (Authorization, custom keys), embed them directly in the URL only if the API supports query-string authentication; otherwise consider building a wrapper service.
- ⚠️ The integration uses a sensible default timeout. Endpoints that take longer than that will fail the step. Consider an async pattern (fire-and-forget plus a webhook trigger for the result) for long-running operations.
- ❌ Do not put secrets directly into the URL where they would end up in logs. Use environment-level URLs and authenticate via a header-injecting proxy if necessary.
What to do next
- For incoming HTTP calls: HTTP-Webhook Trigger.
- For database operations: Database Query.