JSONPath
Category: Transform
Node id: jsonpath
Extracts values from JSON data using dot-notation path expressions with array index support
What it does
- Dot-notation path expressions for nested JSON access
- Array index support (e.g., items[0].name)
- Input-driven path override from upstream nodes
- Found/not-found detection for optional fields
Use cases
- Extract patient name from a nested FHIR Patient resource
- Access specific array elements in FHIR Bundle entries
- Pull deeply nested values from complex API responses
Runtime
- Performance tier:
fast
Input ports
| Name | Type | Required | Description |
|---|---|---|---|
data | json | Yes | JSON data to extract from |
path | text | No | Optional path override from input (takes precedence over config) |
Output ports
| Name | Type | Required | Description |
|---|---|---|---|
value | any | No | Extracted value |
path | text | No | Path that was used for extraction |
found | boolean | No | Whether the path resolved to a value |
Settings
Basic
| Setting | Name | Type | Required | Default | Allowed values | Description |
|---|---|---|---|---|---|---|
| Path | path | string | Yes | Dot-notation path to extract (e.g. user.profile.name, items[0].id) |
Errors
| Code | Description |
|---|---|
MISSING_PATH | Path configuration is required but not provided |
PATH_NOT_FOUND | The specified path does not exist in the input data |
Runtime notes
- value is nil and found=false when the path does not exist — the node does NOT error on missing paths
- Use dot notation for objects and [N] for arrays: e.g., entry[0].resource.id
- Path from input port overrides the config path — useful for dynamic extraction in loops
- Path '.' returns the entire input data object unchanged
See Build any workflow for how to put nodes together and Ports, types and data flow for how port types connect.
¿Algo no está claro? Envíe sus comentarios sobre la documentación por correo electrónico..