HTTP Request — Sample Workflow Walkthrough

HTTP Request node connected to Manual Trigger

HTTP Request connected from Manual Trigger, still default-labeled, showing its Success/Error ports.

HTTP Request node renamed to Get Products

Renamed to "Get Products" via Node Properties → Generic → Name.

Configuration — Request

Field	Value
`url`	`https://dummyjson.com/products?limit=2`
`method`	`GET` (default)
`headers`	none needed
`body`	none — GET request
`timeoutSeconds`	`30` (default)
`allowRedirects`	on (default)

The Initial Data Source configuration tab — matches the table above exactly.

Configuration — Output Data

This is the important part. The raw dummyjson response wraps the actual product list inside a products key — without extracting it, the entire response object would become a single output item.

Field	Value	Why
`outputDataQueryPath`	`products`	Extracts just the nested product array.
`translateOutputDataMode`	`SplitIntoArray`	Turns that array into one output item per product.

HTTP Request Output Data configuration tab

Translate Output Data Mode = "SplitIntoArray - Split wrapped items", Output Data Query Path = "products".

Result

Two items, one per product — every field from the raw API response present under each item's json:

HTTP Request live output showing full product record

Live execution output — Item 1's full json payload: Id, Title, Description, Category, Price, Discount Percentage, Rating, Stock, Tags, Brand, Sku, Weight, Dimensions, Warranty/Shipping Information, Availability Status, Reviews, and more.

Confirmed working exactly as designed The query path + split-into-array combination produced exactly two items, each with the complete, unmodified product record from the API — nothing lost, nothing merged.

← Manual Trigger Next: Filter In-Stock Items →