For the complete documentation index, see llms.txt. This page is also available as Markdown.

Document to Plain Text

Turn document files into clean text for the next step in your workflow.

Document to Plain Text

Overview & The "Smart" Mechanism

The Document to Plain Text node turns document files into readable text. Think of it like an assistant who opens every attachment, reads it, and gives you the important words in one clean note.

Use it when the next step needs document content, not the file itself. It works well for PDFs, Word files, spreadsheets, CSVs, JSON files, text files, web pages saved as HTML, and subtitle files.

Smart features

  • Works with one file or many: send a single file or a batch from an earlier step.

  • Finds the file link automatically: it can read common file outputs without extra cleanup.

  • Handles scanned PDFs: if a PDF is image-based, it still tries to read the visible text.

  • Keeps multi-file output organized: each file is labeled and separated in the final result.

  • Can reuse recent results: turn on cache when the same files run often.

Common Use Cases

  • Turn customer contracts into text before sending them to an AI summary step.

  • Extract policy, invoice, or report content from mixed document uploads.

  • Read spreadsheet or CSV files as text before routing, checking, or comparing data.

How to Configure

  • Input: Select the file field from an earlier step with @. You can pass one file or a list of files.

  • Use supported file types such as .pdf, .docx, .xlsx, .xls, .csv, .json, .txt, .html, .htm, and .srt.

  • Enable caching: Turn this on when the same document is used often and does not change.

  • Caching time: Enter how long Diaflow should reuse the saved result. Start with 60 seconds.

  • Run the workflow and review the extracted text before sending it to the next node.

Before & After Example

Before

After

Important Warnings & Best Practices

  • Very large files can slow the workflow or fail during processing. Split large PDFs or spreadsheets first.

  • If one file in a batch is not supported, the whole batch stops. Test mixed file lists early.

  • Older .xls files may lose some layout or unusual spreadsheet features. Use .xlsx when possible.

  • .srt subtitle files keep their timestamps. Add a cleanup step if you only need spoken text.

  • Rare text encodings in CSV or JSON files can drop special characters. Check accents, symbols, and non-English text after import.

  • If a filename contains __, the displayed filename may appear shortened.

  • When cache is on for multiple files, any file change refreshes the whole batch result.

  • Usage reporting for scanned PDFs may look simplified right now.

Need help?

Last updated