Elysia Tools
Navigation
Workflow Playbook
Turn a structured source into a checked JSON representation, then export the exact table, configuration, document, API, XML, CSON, EDN, BSON, or UBJSON form required downstream.
Hubs
This workflow is for a specific handoff: take one structured source, establish a JSON representation that the team can inspect, then produce the one format required by the next system. The source branch matters. A spreadsheet is a set of rows with header and cell conventions; HCL, TOML, and YAML carry configuration conventions; BSON and UBJSON carry binary JSON details. Treating them as interchangeable text hides the very data-loss risks the conversion is meant to control.
Inspect the JSON checkpoint before choosing a destination. Confirm object versus array shape, required keys, nested structures, identifier strings, nulls, dates, and decimal values. This is also the point to decide whether a nested object may be flattened for CSV or XLSX, whether configuration comments are out of scope, and whether a GraphQL consumer needs a response-shaped payload rather than arbitrary JSON.
Choose a target because a named consumer needs it, not because it is another available converter. CSV is useful for flat records, XML for an agreed hierarchy, Markdown for a review artifact, and CSON or EDN for language-specific workflows. Parse or re-import a representative result and compare the fields that matter to the business. A file that opens successfully is not evidence that its data contract survived.
Workflow playbook
Choose the importer for the supplied source: decode BSON or UBJSON payloads, parse CSON or EDN data, turn a GraphQL response into JSON, or extract structured Markdown. Retain the original beside the JSON checkpoint so ambiguity is traceable.
For CSV or Excel, confirm which row is the header, preserve identifiers that look numeric, and choose whether nested JSON objects must be flattened or restored for an XLSX exchange. Compare row counts and a few difficult cells before proceeding.
Use the YAML, TOML, or HCL branch only for the source format in hand. Inspect nesting, quoted scalars, arrays, and configuration-specific constructs; comments and duplicate-key behavior may not survive a JSON representation.
Export the checked JSON only to the target the next system needs: CSV for a flat record handoff, XML for a hierarchical exchange, GraphQL for a query-oriented payload, Markdown for review, or CSON and EDN for language-specific consumers. Validate the chosen target against a representative re-import or parser.
Choose one importer that matches the real grammar. A CSV row set, Terraform-style HCL, Markdown document, BSON payload, and GraphQL response do not share the same structural assumptions.
Keep JSON as the reviewed handoff when the consumer accepts it; otherwise export exactly one target branch and document intentional flattening, stringification, or hierarchy changes.
Test the fields that carry business meaning: identifiers and leading zeros, null versus empty values, nested arrays, dates, decimal precision, key names, and binary types.