CSV to JSON Converter with Multilingual Metadata Generation

• Accepts CSV data via webhook.
• Supports multiple input content types (file, text/plain, application/json).
• Converts CSV to JSON using a flexible delimiter (comma or semicolon).
• Generates structured metadata in both English and Chinese.
• Provides clear success and error responses.
• Integrates with Slack for error notifications.

1. Webhook Trigger: The workflow starts with a POST webhook node (70a46bce-32da-4868-a960-3ee1cefbed1f) listening for incoming data on the /tool/csv-to-json path.
2. Input Routing: A Switch node (cede2fad-f0ee-4082-a403-81f6d8eb188e) directs the incoming data based on its content-type or presence of binary data.
3. File Handling: If binary data is detected (Extract From File node 4eff962e-e636-4704-835a-672ccd705e16), the data is processed. This branch is intended for binary file uploads.
4. Text/JSON Handling: If the content type is text/plain or application/json:
   • The Change Field node (3484b148-4ba5-4b54-9401-44010ac31178) captures the raw CSV body into a field named csv.
   • The Convert Raw Text To CSV node (b21c88d1-6f21-4ada-95ef-8ea91463e7ad) parses the CSV data, splitting it by comma or semicolon, and structuring it into an array of JSON objects. This node includes error handling for empty data.
5. Conditional Processing: An If node (8fb97224-706b-41de-a7ab-cbe2191436e9) checks for errors after the CSV conversion.
6. Data Aggregation: For successful conversions:
   • The Aggregate node (116cfc2c-6e5f-4367-8c80-e1341e7d196a) aggregates the JSON data for the appJSON branch (likely for handling multiple JSON inputs or arrays).
   • The Aggregate1 node (967dc555-2599-4fb0-b3e1-00164bae4120) aggregates the JSON data for the File or Data/Text branches.
7. Response Generation:
   • Success Response (a7d34aba-6ded-4cc8-8866-7d4aa6ae3255) and Success Response2 (51c77def-cdf7-41da-bfd1-e585f0553672) return the aggregated JSON data upon success.
   • Error Response (ccc66f1e-e000-4048-a492-b80fbf8c8fce) sends a generic error message.
8. Error Notification: If an error occurs at any stage, the Send to Error Channel node (a2d92aeb-25eb-4d3c-82ad-16d2124099a8) sends a notification to Slack.

Metadata Generation: The workflow, as provided, focuses on CSV to JSON conversion. To incorporate multilingual metadata generation, additional nodes would be required after the JSON conversion. This would typically involve:

• Language Detection/Selection: Determine the target languages (en, zh) based on request parameters or workflow configuration.

• Metadata Extraction/Mapping: Map relevant fields from the converted JSON to predefined metadata structures for each language.

• Translation Services (Optional): If the source data is only in one language, integrate with translation APIs to generate localized metadata.

• Data Structuring: Create the final JSON output containing the converted data and the language-specific metadata.

• Example: A subsequent Set node could be used to create en_metadata and zh_metadata fields based on the jsondata output. For instance, to generate a simple en_metadata object: javascript { "en_metadata": { "title": "{{ $json.jsondata.0.some_field_for_title }}", // Example: map from a field in your JSON "description": "{{ $json.jsondata.0.some_field_for_description }}" }, "zh_metadata": { "title": "[Translated title]", // Placeholder for translation "description": "[Translated description]" } }

  This would require further nodes to handle the translation aspect.