Skip to main content

Input Formats

Agent Actions accepts multiple input formats. Place files in agent_io/staging/ before running your workflow.

Supported Formats​

FormatExtensionUse Case
JSON.jsonStructured data, API responses
CSV.csvTabular data, spreadsheets
TSV.tsvTab-separated tabular data
Excel.xlsxSpreadsheet data
XML.xmlStructured markup data
Text.txtPlain text documents
Markdown.mdDocumentation, formatted text
HTML.htmlWeb content
PDF.pdfPDF documents
Word.docxWord documents

JSON Input​

Each JSON file becomes one record. A file containing an array creates multiple records (one per element).

{
  "page_content": "The text content to process...",
  "url": "https://source.example.com/doc",
  "metadata": {
    "author": "John Doe",
    "date": "2024-01-15"
  }
}

CSV/Tabular Input​

Each row becomes a separate record. Header row defines field names.

id,title,content,category
1,First Doc,Content here...,technical
2,Second Doc,More content...,general

Accessing Source Data​

Reference source fields in prompts using {{ source.field }}:

prompt: |
  Analyze this content: {{ source.page_content }}
  From: {{ source.url }}
  Author: {{ source.metadata.author }}

Nested Fields​

Access nested objects with dot notation:

prompt: |
  Author: {{ source.metadata.author }}
  Date: {{ source.metadata.date }}

Iteration​

Loop over arrays in source data:

prompt: |
  Process these items:
  {% for item in source.items %}
  - {{ item.name }}: {{ item.value }}
  {% endfor %}

Best Practices​

  1. Use consistent structure: All input files should have the same field structure
  2. Include metadata: Add tracking fields like id, source, timestamp
  3. Analyze schemas: Use agac schema -a my_workflow to check field dependencies before running

See Also​