Parse commands enable you to extract and parse data from various formats including JSON, HTML, XML, and other structured data formats. These commands are essential for transforming raw data into usable structured formats.Documentation Index
Fetch the complete documentation index at: https://docs.bringits.com/llms.txt
Use this file to discover all available pages before exploring further.
Overview
Parse commands provide functionality for:- Extracting data using JSONPath queries
- Parsing JSON structures
- Transforming data formats
- Extracting specific fields from complex data structures
- Mapping data between different structures
Available Commands
JSON Parse
Parse JSON data into structured objects
Json Path
Extract data using JSONPath expressions
Common Use Cases
- API Response Parsing: Extract specific fields from API responses
- Data Transformation: Transform data structures for downstream processing
- Field Extraction: Extract specific values from nested JSON structures
- Data Mapping: Map data between different formats
- Response Processing: Process and structure HTTP response data
JSONPath Syntax
JSONPath commands use JSONPath expressions to query JSON data. Common patterns include:| Pattern | Description | Example |
|---|---|---|
$ | Root element | $ |
$.field | Access field at root | $.data |
$[*] | All array elements | $.items[*] |
$[0] | First array element | $.items[0] |
$[-1] | Last array element | $.items[-1] |
$.field[*].subfield | Nested array access | $.data.items[*].id |
$..field | Recursive search for field | $..name |
Common JSONPath Patterns
Extract all IDs:Command Parameters
Parse commands typically support the following parameters:| Parameter | Type | Description | Required |
|---|---|---|---|
| source | string | Source data to parse | Yes |
| jsonPath | string | JSONPath expression for extraction | Yes (for Json Path) |
| key | string | Key name for extracted data | Yes |
| input | string | Input data reference | Yes |
Variable Support
Parse commands support variable interpolation in source data and JSONPath expressions:Best Practices
- Test JSONPath Queries: Use the Test panel to validate JSONPath syntax
- Verify Source Data Structure: Check actual data structure before writing queries
- Use Descriptive Keys: Use clear, descriptive key names for extracted data
- Handle Missing Data: Account for missing fields or null values
- Start Simple: Begin with simple queries and build complexity gradually
Troubleshooting
JSONPath Queries Not Working
If JSONPath queries return no results:- Verify Source Data: Check the actual structure of source data using the Test panel
- Test Syntax: Validate JSONPath syntax matches the data structure
- Check Source Selection: Ensure the correct source is selected
- Review Query Examples: Start with simpler queries and build complexity
Common Issues
- Incorrect JSONPath Syntax: Verify syntax matches JSONPath specification
- Data Structure Mismatch: Ensure query matches actual data structure
- Missing Fields: Handle cases where expected fields may not exist
- Null Values: Account for null or undefined values in data
Related Commands
- HTTP Commands - Fetch data to parse
- Object Mapper - Transform parsed data
- Validation Commands - Validate parsed data