> For the complete documentation index, see [llms.txt](https://docs.diaflow.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diaflow.io/workflow-builder/nodes/built-in-tools/file-creator.md).

# File creator

## File creator

### What does it do?

The **File creator** node builds a brand-new file from the content in your workflow. Think of it like an assistant who takes your notes, report data, or AI output and turns it into a finished document you can download or send.

It works well for reports, exports, transcripts, summaries, and formatted handoff files.

#### Smart features

* **Builds a file from workflow content**: use typed text or insert values from earlier steps with **@**.
* **Fills in dynamic values automatically**: file names and file content can use values from earlier nodes.
* **Recognizes common file type names**: choices like **word**, **document**, **excel**, **text**, **markdown**, and **subtitle** are matched to the right output format.
* **Detects rich content automatically**: if your content already looks like a web page, Diaflow uses a richer path for **PDF** output.
* **Prepares spreadsheets from structured content**: for **XLSX** and **CSV**, Diaflow can turn table-style content into a usable spreadsheet file.
* **Cleans subtitle files for you**: for **SRT**, Diaflow fixes timing formatting before creating the file.
* **Returns a ready-to-use download link**: the output is a file link you can pass to later steps or an **Output** node.

<figure><img src="/files/hCc8rGR0LITEbJuYvmJy" alt=""><figcaption></figcaption></figure>

### Real-World Business Value

* Turn an AI-generated meeting summary into a **DOCX** file for managers and clients.
* Create a **CSV** or **XLSX** export from structured workflow results before sending it to finance or operations.
* Generate a branded **PDF** report from workflow content and share it as a downloadable file.

### Step-by-Step Setup

* Drag **File creator** onto the canvas.
* In **File type**, choose the format you want to create, such as `pdf`, `docx`, `xlsx`, `txt`, `md`, `html`, `json`, `csv`, or `srt`.
* In **File name**, enter a clear file name, such as `weekly-sales-report`.
* In **Content**, type the content you want in the file or insert values from earlier nodes with **@**.
* If you are creating **XLSX** or **CSV**, paste clean table-style content or structured data.
* If you are creating **JSON**, enter valid JSON if you want the file to keep an exact JSON structure.
* Save the node and run the workflow once to confirm the file opens as expected.

### The Transformation: Before & After

**Before  raw content entered in the node**

<figure><img src="/files/rYEqBkMNdxhbh6VTjND8" alt=""><figcaption></figcaption></figure>

**After  downloadable file returned by the node**

<figure><img src="/files/eBkasiOvUodNvwHiqlQj" alt=""><figcaption></figcaption></figure>

In this example, plain workflow text becomes a shareable **DOCX** file.

### Tips & Warnings for First-Timers

#### Best practices

* Choose the output format based on how people will use the file.
* Keep **File name** short and clear.
* Test one small file first before generating a large PDF or spreadsheet.
* For **XLSX**, use clean structured content with consistent columns.
* For **JSON**, paste valid JSON when you need exact field structure.
* For **PDF**, use well-formatted content if layout matters.

#### Warnings

* Do not leave **Content** empty. The file will fail to generate.
* Do not choose a file type that the node does not support yet.
* Do not expect **XLSX** to work from free-form text. Use table-style or structured content.
* Do not expect **XLSX** to create multiple sheets. It creates one sheet only.
* Do not expect mixed text and JSON notes to become a clean **JSON** file automatically. Use valid JSON only when exact structure matters.
* Do not paste broken web page content into **HTML** if you need a clean browser-ready file.
* Do not rely on repeated runs producing a reused file automatically. This node creates the file again each time.
* Do not use very long untested content for your first **PDF** run. Review the output once before sharing it widely.

### Need help?

* Learn the basics in [How a node works](/getting-started/lets-start-with-the-basics/how-a-node-works.md)
* Build the full flow in [Create a workflow](/workflow-builder/create-a-workflow.md)
* Browse related nodes in [Component List](/workflow-builder/component-list.md)


---

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

```
GET https://docs.diaflow.io/workflow-builder/nodes/built-in-tools/file-creator.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.