File upload
Upload one or more files
File upload is a simple intake that lets you drop one file or many into a workflow to get it going. It is the general-purpose starting point when the job begins with documents you already have in hand.
How it works
Point this node at the start of a workflow and it gives you a spot to add files. A single PDF, a folder's worth of scans, a mix of spreadsheets and images: they all go in the same way, and the workflow you designed takes over from there.
Think of it as the loading dock for your process. It does not read or change anything itself; its only job is to accept the files cleanly and pass them along to whatever comes next, whether that is reading a statement, filling a form, or merging pages.
Because it is deliberately plain, it fits almost any workflow. When you are not sure which specialized intake to use, this is the safe default for getting files into the pipeline.
Common use cases
Real situations where this node earns its place in a flow.
Process a stack at once
Upload a folder of statements or invoices together and run the whole batch through extraction and analysis in one job.
Re-run a single document
When something needs a second pass, upload the file directly instead of waiting for it to arrive by email again.
Staff-initiated jobs
Let your own team kick off work by hand for one-off documents that do not come through an automated channel.
File upload in a workflow
A simple example of where this node sits in a flow.
What you set up
- Set whether the job accepts a single file or several at once.
- Optionally limit which file types are allowed (for example PDFs only).
- Wire its output into the first step that should act on the files.
Common questions
What file types can I put in?
By default common documents and images. You can restrict it to specific types if your workflow only expects one kind.
How is this different from Direct upload?
They overlap. Direct upload is the built-in staff form on the new-job screen; File upload is the generic building block you can place inside any workflow.
Settings you configure on this node, stored under data.config in the workflow JSON. Leave a field unset to use its default.
acceptComma-separated allowed file extensions (.csv, .xlsx, .pdf); empty means any file.
Type: stringmultipleWhether more than one file may be uploaded; false forces a single-file run.
Type: booleanDefault:truemaxSizeBytesPer-file size ceiling in bytes; when set it lowers the default max file size.
Type: number
How this node appears inside a workflow's nodes[] array (the shape you see in the Developer export / import). A full workflow is { nodes: [...], edges: [...] }.
{
"id": "file-upload",
"type": "card",
"position": {
"x": 160,
"y": 120
},
"data": {
"type": "file-upload",
"kind": "input",
"title": "File upload",
"subtitle": "Upload one or more files",
"config": {
"accept": "",
"multiple": "true",
"maxSizeBytes": "0"
}
}
}