Elysia Tools
Navigation
Workflow Playbook
Format, inspect, compare, merge, transform, validate, analyze, and watermark JSON payloads for API and data workflows.
Hubs
JSON work usually fails when the team edits a blob they cannot safely inspect. Begin with json-formatter, json-path-visualizer, and json-visualizer so the source is readable, nested fields are easy to locate, and everyone can reference the same paths.
Before changing structure, compare the candidate and baseline with pretty-json-diff. Once the changes are understood, use json-merger for controlled combination and jsonata-query-transform-studio for targeted reshaping. This keeps formatting, diffing, merging, and transformation decisions auditable.
Use json-schema-validator for standalone JSON rules and api-response-contract-validator for real API responses tied to OpenAPI contracts. If the source is log data, parse it with structured-log-analyzer; if the result will be shared, add traceability with csv-json-data-watermarker.
A useful final package contains the original payload, the formatted view, relevant JSONPath references, diff notes, transform rules, validation results, and any watermark details needed for downstream review.
Workflow playbook
Format the source JSON, open it as an interactive tree, and copy important JSONPath locations so reviewers can discuss the same fields.
Run a readable JSON diff between the baseline and candidate payloads, then record added, removed, and changed fields before any transformation work.
Combine approved files with the selected merge policy and use JSONata-style queries to reshape data for review, export, or downstream ingestion.
Check the final payload against schemas or API contracts, parse structured logs when needed, and watermark CSV or JSON exports before sharing.
Start with formatting and visualization when people need to understand the payload, then use diffing or path inspection when the question is what changed or where a nested value lives.
Use merge and JSONata steps for controlled transformations, then validate with JSON Schema or an API response contract before shipping the output.
Analyze structured logs when JSON-like records come from observability systems, and watermark CSV or JSON exports when shared datasets must remain attributable.