The problem
Customers email packets that mix invoices, contracts, and IDs. Staff download attachments, rename files, and retype fields into another system. The customer never sees status, and the only copy of the packet is a mailbox.
How the workflow runs
Customer uploads the packet
The hosted portal collects the files and customer details. That submit starts the run, so status is visible on the same app.
Classify each file
Each upload is classified as invoice, contract, ID, or other. That first label decides how your team reads the packet before anyone opens it.
Extract the fields
An extract step then pulls structured fields from the file. Results show the category, the fields, and the original documents together.
What the hosted app shows
The portal is a branded hosted app: upload, customer form, run status, a results table, and a document viewer. Customers stay on that URL. Your team edits the workflow on the canvas.
Who it is for
Teams that need an external intake surface: customer onboarding, vendor packets, or any process where the person uploading the file is not a studio user.
Questions
They use the hosted app URL. Studio access stays with the people who edit the workflow.
Add a human review step on the canvas for exceptions. The starter classifies and extracts so the common path completes without a custom frontend.
Hosted apps are branded for your organization. The page layout is the published app schema: upload, form, status, results, and documents.