HTTP request
Call an external endpoint and bring the response into the flow.
The HTTP request node is a full API client inside the canvas. It is for fetching real-time data or sending information to an external system.
It is the way out for systems that have neither an MCP nor a ready-made integration.
Method and URL
The available methods are GET, POST, PUT, DELETE and PATCH.
The URL accepts variables, which lets you build the address from the flow:
https://api.store.com/orders/{{ entrada.numero_pedido }}Headers
Key-value pairs, used mostly for authentication:
| Key | Value |
|---|---|
Authorization | Bearer {{ entrada.token_api }} |
A token typed directly into the value is saved in the flow definition, visible to anyone who opens the canvas. Prefer passing it through a workspace Variable, or using an Integration, which keeps the access outside the design.
Body
For POST and PUT, the body is the JSON sent, built with variables from earlier nodes:
{
"customer": "{{ extrator_cpf.cpfs[0] }}",
"reason": "{{ llm.classificacao }}"
}Advanced settings
- Timeout: the maximum time to wait for the response, in seconds, with a default of 360.
- Content-Type and Accept: the data format, usually
application/json.
A slow endpoint that exceeds the timeout fails the whole run. For services known to be slow, raise the value before publishing.
Next steps
- Keep credentials out of the design in Variables.
- For well-known services, compare with Integration.