Comflowy Http Request

Not every node in the Comflowy pack is about closed-source models. This one is the plumbing node: it lets a ComfyUI workflow make an arbitrary HTTP request and get a JSON response back. You feed it a URL and a method, optionally a header and body, and it returns whatever the server sends as a JSON value that other nodes in the pack - and in ComfyUI generally - can consume.

Why would you want this? Because workflows that touch the real world end up needing it. Pull a job spec from an API, check a queue status, POST your final image metadata somewhere, or call any service that speaks JSON. Combined with the pack's JSON handling nodes, it turns ComfyUI into something that can participate in a larger pipeline instead of being a closed image-making box. It's the same genre as other HTTP nodes in the ecosystem, but it's here, native to a pack you may already have installed, and its JSON output type plugs straight into Comflowy Preview JSON and Comflowy Extract JSON.

How it works and the inputs

The node is a thin wrapper over Python's requests library. It picks the method from a dropdown, parses headers_json and body_json if you gave them, fires the request with a 10-second timeout, and returns response.json(). One wrinkle to note: for GET and DELETE it doesn't send a body; for POST, PUT, and PATCH it sends body_json as JSON.

• url (required) - the endpoint.
• method (required) - GET, POST, PUT, DELETE, or PATCH.
• headers_json (optional, multiline) - a JSON object like {"Authorization": "Bearer ..."}. Must be valid JSON or the node throws.
• body_json (optional, multiline) - the request body as a JSON object.

Output: JSON (a parsed object/list, not a string - that's why the node is marked as an output node that also shows a text preview). If the request fails at the HTTP level, the node returns the error string instead of crashing the graph, so check your console when something looks off.

Installing and the gotchas

Install Comflowy's Custom Nodes via ComfyUI Manager (search "Comflowy") or git clone https://github.com/6174/comflowy-nodes into custom_nodes, restart. Dependency: requests. Note that unlike the rest of the pack, this node doesn't need a Comflowy API key - it's plain HTTP from your machine, which is both simpler and a mild security note.

Where people get burned:

• 10-second timeout. The node is strict about it, and slow endpoints (LLM APIs under load, cold serverless functions) will time out. That's a hard wall in the code, not a setting you can fix.
• The response must be JSON. response.json() will throw on an HTML or empty response, and you'll get the error string back instead of data.
• It runs on your machine, not Comflowy's. Your IP, your network, your firewall. If you're using this to reach a local service, it works - but any API that's blocked from your network will fail here even though the cloud nodes are fine.
• The console is your friend. The node prints the request URL, headers, body, and result to your console. When a request looks wrong, the answer is usually visible in the terminal.

It's a quiet, unglamorous node - but if you've ever wanted to feed live data into a generation or push results out of one, it's the piece that makes it possible.