> For the complete documentation index, see [llms.txt](https://docs.dckapintegrator.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dckapintegrator.com/tutorials/workflow-builder-tutorial/2.-hello-workflow/2.4-lets-transform-data-inline.md).

# 2.4🔖Let's Transform Data Inline

{% stepper %}
{% step %}

#### Initialize a Variable

In the same workflow, let’s initialize a variable with the following details: 

| Variable      | Type | Value                                                           |
| ------------- | ---- | --------------------------------------------------------------- |
| emails        | JSON | `["<Add your company mail ID>", "<Add your personal mail ID>"]` |
| {% endstep %} |      |                                                                 |

{% step %}

#### Use Inline Transformation

* Edit the Notification step
* In the **Send To** field:
* Select the emails variable from Data Hub

👉 Now, instead of using it directly, apply transformation:

`{{variables.emails.join(",")}}`

📌 Why?

* The system expects comma-separated emails
* But our variable is a JSON array
* `.join(",")` converts it into the required format

<figure><img src="/files/W01xaZQN7gOUeHejhLXW" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Run and Verify

* Save the workflow
* Click Sync Now&#x20;
* Check your inbox
  {% endstep %}
  {% endstepper %}

#### 🎉 Congratulations, you have successfully experimented with an inline transformation.

To explore more, check [Inline Transformations](https://docs.dckapintegrator.com/project-manager/workflows/inline-transformations) and [Allowed Functions in Inline Transformation](https://docs.dckapintegrator.com/project-manager/workflows/inline-transformations/allowed-functions) with [examples](https://docs.dckapintegrator.com/project-manager/workflows/inline-transformations/examples).

<br>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.dckapintegrator.com/tutorials/workflow-builder-tutorial/2.-hello-workflow/2.4-lets-transform-data-inline.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.