> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/tools/jolt-v2.md). # Transformer (JOLT) V2 Discover more about the Transformer (JOLT) V2 component and how to use it on the Digibee Integration Platform. **Transformer (JOLT) V2** allows the manipulation of a JSON through JOLT technology. The component is useful: * To modify the structure of a JSON and keep its values. * To add, extract, and remove data from a JSON. * To sort the structure of a JSON. * To modify the values contained in a JSON through functions, such as text manipulation, mathematical calculations, conversions between data types, among others. * To access and manipulate data from arrays. Learn more about [**How to apply JOLT for JSON transformations**](/documentation/resources/use-cases/how-to-jolt.md). {% hint style="info" %} This connector supports AI-assisted configuration. [Learn more.](/documentation/development-cycle/build-overview/canvas/connector-ai-assistant.md) {% endhint %} ## **Parameters** Take a look at the configuration parameters of the component. Parameters supported by [Double Braces expressions](/documentation/connectors-and-triggers/double-braces/overview.md) are marked with `(DB)`.
ParameterDescriptionDefault valueData type
Expression ReferenceIf the option is activated, the JOLT Reference parameter expects a JOLT expression declaration through Double Braces reference.FalseBoolean
JOLTThe JOLT expression to be executed.N/AJSON
JOLT Reference (DB)The Double Braces reference to the JOLT expression to be executed. This parameter is available only if Expression Reference is activated.N/AString
Fail On ErrorIf the option is activated, the execution of the pipeline with an error will be interrupted. Otherwise, the pipeline execution proceeds, but the result will show a false value for the “success” property.FalseBoolean
## **Recommended use for Expression Reference** The **Expression Reference** parameter is only recommended for highly dynamic scenarios, as maintaining the JOLT operations separately from the **Transformer (JOLT) V2** component is very complex. These scenarios require some precautions depending on how they are implemented, such as: managing JOLT operations through the [**Object Store**](/documentation/connectors-and-triggers/connectors/structured-data/object-store.md) component, transformations versioning, segregating definition and execution of the JOLT transformations between pipelines, and so on. In addition, these scenarios can also increase the need for [**Log**](/documentation/connectors-and-triggers/connectors/tools/log.md) components in the pipeline due to the lack of visibility with dynamic scenarios. ## **JOLT operations** ### **Shift** Used to change the structure of a JSON, keeping the values contained in that same JSON. **Example:** **Input** ``` { "body": { "userName": "John" } } ``` **Transformation** ``` [ { "operation": "shift", "spec": { "body": { "userName": "data.user_name" } } } ] ``` **Output** ``` { "data" : { "user_name" : "John" } } ``` ### **Default** Used to add new fields or objects in a JSON, if they don't already exist. **Example:** **Input** ``` { "body": { "userName": "John" } } ``` **Transformation** ``` [ { "operation": "default", "spec": { "body": { "email": "default@email.com" } } } ] ``` **Output** ``` { "body": { "userName": "John", "email": "default@email.com" } } ``` ### **Remove** Used to remove fields or objects from a JSON. **Example:** **Input** ``` { "body": { "userName": "John", "email": "default@email.com" } } ``` **Transformation** ``` [ { "operation": "remove", "spec": { "body": { "email": "" } } } ] ``` **Output** ``` { "body" : { "userName" : "John" } } ``` ### **Sort** Used to sort fields and objects in a JSON, in alphabetical order. **Example:** **Input** ``` { "employee": { "phone": "999999999", "name": "Sort Employee", "birthDate": "1980-01-01", "role": "analyst" } } ``` **Transformation:** ``` [ { "operation": "sort" } ] ``` **Output** ``` { "employee" : { "birthDate" : "1980-01-01", "name" : "Sort Employee", "phone" : "999999999", "role" : "analyst" } } ``` ### **Cardinality** Used to transform simple fields and objects into arrays and vice-versa. **Example:** **Input** ``` { "products": { "name": "Product A", "id": "123-A", "value": 10 } } ``` **Transformation** ``` [ { "operation": "cardinality", "spec": { "products": "MANY" } } ] ``` **Output** ``` { "products" : [ { "name": "Product A", "id": "123-A", "value": 10 } ] } ``` ### **Modify-default-beta** Used to add values ​​and apply functions to a JSON. **Example:** **Input** ``` { "products": [ { "name": "Product A", "price": 10 }, { "name": "Product B", "price": 20 } ] } ``` **Transformation** ``` [ { "operation": "modify-default-beta", "spec": { "products": { "*": { "manufacturer": "Manufacturer default" } } } } ] ``` **Output** ``` { "products" : [ { "name" : "Product A", "price" : 10, "manufacturer": "Manufacturer default" }, { "name" : "Product B", "price" : 20, "manufacturer": "Manufacturer default" } ] } ``` ### **Modify-overwrite-beta** Used to override values ​​and apply functions to a JSON. **Example:** **Input** ``` { "data": { "firstName": "John", "lastName": "Smith" } } ``` **Transformation** ``` [ { "operation": "modify-overwrite-beta", "spec": { "data": { "fullName": "=concat(@(1,firstName),' ',@(1,lastName))" } } } ] ``` **Output** ``` { "data" : { "firstName" : "John", "lastName" : "Smith", "fullName" : "John Smith" } } ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.digibee.com/documentation/connectors-and-triggers/connectors/tools/jolt-v2.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.