App file uploads are the upload fields in a published Taskade Genesis app. The people who use your app can attach a site photo, a signed contract, a receipt or an invoice. Taskade stores the file in your workspace, next to the record it belongs to. Then an automation reads what is inside the file and fills in the record.
TL;DR: Ask Taskade Genesis for an upload field on a form. Each file that a user sends is saved with the submission and lands in Media Files in your workspace. A Convert File to Text step reads the file, and an AI step pulls out the details that you name. Learn: Let people send files to your app
What Are App File Uploads?
App file uploads turn paperwork into data. A file is not a name in a text box. It is a real stored file that travels with the form submission into your automations. It also stays in Media Files, so you always have the original.
Two kinds of file exist in a Taskade Genesis app. Keep them apart:
| Files you attach while you build | Files your app users send | |
|---|---|---|
| Who attaches it | You | Clients, field crews, vendors, applicants |
| What it is for | It shows Taskade Genesis what to build, for example a brand guide | Data that your app reads, for example a receipt |
| When it happens | Before you publish | Every day after you publish |
How App File Uploads Work
App file uploads connect the three layers of Workspace DNA. The project remembers, the AI reads, and the automation acts.
app user picks a file
│
▼
upload field on your form ──► Media Files
│
▼
automation starts (form or webhook)
│
▼
Convert File to Text ──► AI step reads the fields
│
▼
row in your project ──► email, task or payment
- Ask for the field. Tell Taskade Genesis who sends the file, what the file is, and what happens next. For example: "Clients attach their signed agreement, and the app fills in the start date."
- The user sends the file. The user drops the file on the form and clicks submit.
- The automation reads it. A Convert File to Text step hands the words in the file to an AI step.
- The record fills in. The AI step writes the details to the row, and the next step can act on them.
What People Build With App File Uploads
| Job | File | What the automation does |
|---|---|---|
| Expenses | A photo of a receipt | Pulls the amount and the vendor, then sends it to finance |
| Field work | A site photo | Attaches it to the job and starts the next step |
| Client intake | Signed documents | Starts the onboarding workflow |
| Invoices | A supplier PDF | Reads the total and tracks the payment |
If the file is a contract or a resume, turn on App Users. Then each upload arrives from a named, signed-in person. Sign-in confirms who the person is. It does not hide the records of other people, so match each record to its login and test the app with a second account.
Plans and Limits for File Uploads
Each file that an app user sends can be up to 10 MB on every plan. It can be an image, a PDF or an Office file (.docx, .xlsx, .pptx). Inside your workspace, the upload size depends on the plan, and an upload of a PDF, a document or a spreadsheet to a project or to agent knowledge needs a paid plan. Images upload on every plan. See pricing for the current limits.
Related Concepts
Frequently Asked Questions About App File Uploads
Can people upload files to a Taskade Genesis app?
Yes. Ask Taskade Genesis to add an upload field to a form. The people who use the app can then send photos, PDFs and other files with their submission.
Where do uploaded files go?
Each file is saved with the submission and lands in Media Files in your workspace. The automation behind the form gets the file too, so the next step can open it.
Can Taskade read the text inside an uploaded file?
Yes. Add a Convert File to Text step after the trigger. An AI step can then pull the details that you name, such as a client name, a date or a total.
Do my app users need a Taskade account to upload a file?
No. A public form takes files without an account. Turn on App Users when you need each upload to come from a named, signed-in person.