# Binary Data

#### Nodes <a href="#nodes" id="nodes"></a>

There are three key nodes dedicated to handling binary data files:

* `Read/Write Files from Disk` to read and write files from/to the machine where Appizap Workflow Builder is running.
* `Convert to File` to take input data and output it as a file.
* `Extract From File` to get data from a binary format and convert it to JSON.

There are separate nodes for working with XML and HTML data:

* `HTML`
* `XML`

And nodes for performing common tasks:

* `Compression`
* `Edit Image`
* `FTP`

You can trigger a workflow based on changes to a local file using the `Local File trigger.`

To split or concatenate binary data items, use the `data transformation nodes.`

### Configure binary data mode when self-hosting <a href="#configure-binary-data-mode-when-self-hosting" id="configure-binary-data-mode-when-self-hosting"></a>

You can customize how your self-hosted Appizap Workflow Builder manages binary data by using Binary data environment variables. This involves setting storage path and selecting storage methods for binary data.

Reading and writing binary files can pose security risks. To prevent reading and writing binary data, use the `NODES_EXCLUDE` environment variable.


---

# Agent Instructions: 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:

```
GET https://docs.appizap.ae/appizap-workflow-builder-pro/data-handling/binary-data.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.