INPUT_FILE_AS_TEXT when a flow needs the contents of a file available at a direct URL. The value input accepts one URL or an array of URLs. The result is the file content as text: one string for a single URL, or an array for multiple URLs. A one-element array returns one string.
Fetch the file content
result for the text you expect. The file picker lists plain text, CSV, HTML, XML, JSON, and YAML types; this tool returns text rather than parsing those formats. description is optional. use_as_input defaults to true, and optional defaults to false.
Use the returned text
A later step can consume the returned text directly; parse JSON or CSV explicitly when you need fields or rows:INPUT_CSV_FILE instead; see Summarize a CSV file. Avoid putting API keys or other secrets from a configuration file into an AI prompt.
Check a JSON configuration file
Parse the text in Python and check for required keys without printing their values:steps.check_config.result.data.valid is true only when the file is a JSON object with every required key set. Otherwise result.data.error explains a parse problem or result.data.missing lists keys that are absent or empty. Edit required to match your file. To reject bad JSON sent to a published workflow instead, use Input JSON with Validation.
Check file input failures
If no URL is supplied, the step fails with “File URL is required.” A failed fetch reports its HTTP status. Check the URL, access permissions, and response status. A file larger than 100 MiB, a download that takes longer than 5 minutes, or more than 50 URLs in one step also fails the step (see Download limits). Ifoptional is true and no URL is supplied, result is null.