Skip to main content
The File Helpers toolkit gives agents file utilities: save base64 payloads to storage, read files with intelligent text extraction, change text encodings, and detect MIME types. No connection or API key is required. Add it on the agent Toolkits tab, then reference the tools with @ in the personality prompt when the agent should handle files.

​
Prerequisites

  • An agent you can edit
  • For Read File, Change File Encoding, and Check File Type: a filesystem path returned by a prior save step (or another tool that writes a local file path)

​
Available tools

​
How the tools work together

Typical flow:
  1. Save Base64 File — for example from an email attachment or integration payload
  2. Use the returned file path with Read File, Check File Type, or Change File Encoding
Read File needs a server filesystem path. It does not take a public URL or Knowledge Base name by itself — save or obtain a path first.

​
Use cases

  • Persist base64 attachments from email or webhook steps, then read them as text
  • Inspect MIME type before routing a file to another toolkit
  • Normalize encoding for CSV or log files before analysis
  • Pair with the PDF toolkit when you need PDF-specific page images or PDF generation (File Helpers Read File can extract PDF text as one of many formats)

​
Tips

  • Prefer clear file names when saving so later steps can identify the file.
  • Use Check File Type before downstream tools that only accept certain formats.
  • Files saved by this toolkit are not automatically available inside the Python sandbox. To analyze them with Python Code Execution, upload into the sandbox separately when your flow requires it.
  • For in-chat markdown documents (create/edit/list), use Document Manager.

​
Troubleshooting