This template takes a JSON object and a row index and returns exactly one key–value pair at that index. It’s a handy helper when you only need a single entry from a structured JSON payload (e.g., picking one form field for downstream logic).
When clicking ‘Test workflow’) starts the flow.myData: an object of key → value pairs.rowIndex: a 0‑based index indicating which pair to extract.myData and returns [key, value] at rowIndex as result.result[0] to a field named result.result[1] to a field named result[1].Open the workflow and select Input JSON Node.
Replace the sample with your own JSON:
{ "myData": { "name": "Alice", "age": "30", "city": "Paris" }, "rowIndex": "1" }
Click Execute Workflow. Check the Key and Value nodes for the outputs.
myData: object with keys/valuesrowIndex: integer (0‑based){ "key": ..., "value": ... } or write directly to next‑node fields.rowIndex, non‑object myData, or empty objects.myData is an object and rowIndex is numeric.| Issue | Possible Cause | Solution |
|---|---|---|
| “Index out of range” | rowIndex is larger than the number of keys | Use a valid 0‑based index; add a guard in the Code node to clamp or default. |
| Wrong key returned | Object key order differs from expectations | Object key order isn’t guaranteed across sources—prefer pick by key name for reliability. |
| Empty/invalid output | myData is not an object or is empty | Ensure myData is a flat object with at least one key. |
| Python errors | Code node’s Python runtime not available | Enable Python in the Code node or convert the snippet to JavaScript. |
| Value type mismatch | Value isn’t a string | Cast as needed in the Set node or normalize types in the Code node. |
If you’d like this to pick by key , handle nested JSON , accept data via Webhook or fully customized to your needs, write to us and we’ll adapt the template to your exact use case.