HTTP Request
Use this action when you need to call an external API or webhook from a workflow or agent action.
Best for
- Sending data to external systems
- Fetching information before later steps continue
- Fetching small payloads (responses are capped at 5 MB — for larger downloads to storage use the Download to Storage action,
actions/network/http/download-to-storage, which streams files up to 500 MB)
Main fields
| Field | What it does |
|---|---|
| HTTP method | Chooses the HTTP method, such as GET or POST |
| HTTP URL | The target endpoint |
| Purpose | Optional label for what the request does, shown in logs |
| HTTP headers | Adds custom request headers |
| HTTP body | Sends data for methods like POST or PATCH (hidden for GET) |
| Return as buffer | Returns raw file data instead of text or JSON |
| Enable cache | Reuses identical responses (same method, URL, headers, and body). The cache is shared across separate runs for the same company + assistant, and entries live for about 10 minutes — an identical request in a later run may return a cached response |
URL restrictions
Only public http:// and https:// URLs are allowed. Requests to localhost, private or internal network addresses, and cloud metadata endpoints are blocked, so the action cannot reach services on an intranet or VPN. Requests time out after 2 minutes.
What later steps can use
Request results are available at:
step(N).statusstep(N).datastep(N).headers
Tips
- Store API keys and other sensitive header values as secrets instead of plain text.
- Use buffer mode when the response is a small (up to 5 MB) file, image, or PDF; for larger downloads to storage use the Download to Storage action (
actions/network/http/download-to-storage, up to 500 MB). - Check the status code before assuming the request succeeded.