Short answer: Drop the "OpenAI → List Files" action anywhere in your workflow, map the inputs from upstream nodes, and publish.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Filter by Purpose purpose | options | Optional | Filter by Purpose. Options: All, Fine-tune, Assistants, Batch |
{"purpose": "{{trigger.purpose}}"}
{"data": [{"id": "file-abc123","bytes": 1024,"purpose": "fine-tune","filename": "data.jsonl"}]}
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.
Triggered by anything in the catalog. Free tier available. No credit card.