# Parsing JSONL Files in Celigo

**URL:** <https://connective.celigo.com/t/parsing-jsonl-files-in-celigo/2882>\
**Category:** Integrator.io\
**Tags:** script, csv, jsonl, transformation, file-transfer\
**Created:** [January 21, 2025, 12:42am UTC](https://connective.celigo.com/t/parsing-jsonl-files-in-celigo/2882 "2025-01-21T00:42:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![tylerlamparter](https://sea1.discourse-cdn.com/flex001/user_avatar/connective.celigo.com/tylerlamparter/32/9204_2.png) [@tylerlamparter](https://connective.celigo.com/u/tylerlamparter)\
**Post date:** [January 21, 2025, 12:42am UTC](https://connective.celigo.com/t/parsing-jsonl-files-in-celigo/2882/1 "2025-01-21T00:42:21Z")

</div>

Ever need to work with a JSONL file but don't see JSONL listed as a file type within Celigo file provider exports? No worries—here’s a simple workaround to parse JSONL files and make them usable in your flows:

**Steps to Parse JSONL Files:**

1. **Import JSONL as a CSV:**
  - Treat the JSONL file as a CSV file by selecting the **CSV (or any delimited text file)** option in the file provider setup.
  - Use a custom column delimiter (e.g., `celigo_dummy_delimiter`) that would never exist in the file itself. This ensures each JSONL row is treated as an individual column.

2. **Add a Transformation Script:**
  - Create a transformation script to parse the stringified JSON in each row. Below is a sample transformation script:

```javascript
function transform (options) {
  
  options.record = JSON.parse(options.record.Column0);
  
  return options.record;
}

```

 ![5301043caa20740200000001-014706f61a9d4826842118db38174476.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/8/867b534b0f402acc83f6f23754c40bfa75c35cea.png)

 ![5301043caa20740200000001-aa1c26309333420895ad7e2148e5f1af.png](https://us1.discourse-cdn.com/flex001/uploads/celigo/original/2X/5/5de4b33da77265ad76a173b7cd3df6d0650aedd3.png)