🇬🇧 EN
🇮🇹 IT
User Guide / Workflows / Node Reference / HTTP Request

🌍 HTTP Request

Makes any HTTP request to an external API or service and returns the response. Supports all common HTTP methods, custom headers, query parameters, and request bodies. The most flexible integration node for third-party APIs.

Category: Data Retrieval & Processing  ·  Type identifier: http_request

Overview

The HTTP Request node is the universal integration building block in Flusso. If a service exposes a REST API, webhook endpoint, or any HTTP interface, this node can communicate with it. You can fetch data from external systems, push data to third-party platforms, trigger remote actions, or call internal microservices — all from within a workflow step.

The node supports dynamic values in the URL, headers, query parameters, and request body using {{ variable }} references. This makes it straightforward to build requests that incorporate data from earlier workflow steps, trigger payloads, or user-provided input.

The response body is automatically parsed as JSON when the Content-Type is application/json. If the response is plain text or another format, the raw string is returned. The ok field gives you a quick boolean check for success without needing to inspect the status code manually.

Configuration

FieldStatusDescription
Method Required HTTP method — GET, POST, PUT, PATCH, DELETE, HEAD.
URL Required Full URL including protocol, e.g. https://api.example.com/v1/users. Supports {{ variable }} references for dynamic URLs.
Headers Optional Key-value pairs of HTTP headers, e.g. Authorization: Bearer {{ trigger.output.token }}.
Query Parameters Optional Key-value pairs appended to the URL as query string parameters.
Body Optional Request body. For JSON APIs, enter a JSON object. Supports {{ variable }} references.
Content Type Optional Content-Type header shortcut. Defaults to application/json when a body is present.
Timeout Optional Request timeout in seconds. Default: 30.
Follow Redirects Optional Toggle. Default: enabled.

Output Data

The node returns the full HTTP response, including status code, parsed body, and response headers.

FieldTypeDescription
statusnumberHTTP response status code (e.g. 200, 404)
bodyobject/stringParsed JSON response body, or raw string if the response is not JSON
headersobjectResponse headers as key-value pairs
okbooleanTrue if status code is 2xx
{{ http_step.output.status }} {{ http_step.output.body }} {{ http_step.output.body.id }} {{ http_step.output.headers.content-type }} {{ http_step.output.ok }}

Example Usage

Webhook trigger → HTTP Request to fetch order details from Shopify API → Agent processes the data.

  1. Add a Webhook Trigger node. When a new order is placed, Shopify sends the order ID to this webhook. Use the step key webhook.
  2. Add an HTTP Request node. Set Method to GET, URL to https://your-store.myshopify.com/admin/api/2024-01/orders/{{ webhook.output.order_id }}.json, and add an X-Shopify-Access-Token header. Use the step key shopify_order.
  3. Add an Agent node. Pass {{ shopify_order.output.body.order }} as context and instruct the agent to check the order for fulfilment issues.
  4. Add a Conditional node to branch: if the agent flags an issue, send a Slack message; otherwise, do nothing.

Tips & Notes

Related Nodes

← Node Reference