Upload documents
Get a document into a process so it can act on it. A document enters through the process’s trigger — the same way any input does — and the process reads it from there.
Supported types
Section titled “Supported types”PDF, common image formats (PNG, JPG, TIFF), Word, plain text, CSV, and JSON are handled out of the box. Other formats are accepted but may not be readable by an AI agent.
How documents get in
Section titled “How documents get in”Match the method to the process’s trigger:
- Email / message — attach the document to an email sent to the mailbox on the process’s Message start event. The trigger fires within a few seconds. Best for production.
- Webhook / API — POST the document (as a multipart request) to the process’s webhook endpoint. Each request starts a run.
Whichever fires, the document lands in the platform’s object storage, and the process’s steps — a document-processing step, or an agent reading the file — extract what they need from it.
Test it end to end
Section titled “Test it end to end”To try a document through a process, send it the way the process listens — email it to the mailbox, or POST it to the webhook — then open Workflow Executions and watch the run appear and move through its steps.
Common variations
Section titled “Common variations”- Multiple documents in one run. A process whose input schema declares a list can take a batch — several attachments on one email — and package them into a single run.
- Re-run on failure. If a run failed because the document was malformed, fix it and send it again; a new run starts. Cancel the failed run from Workflow Executions if you don’t want it lingering.
Troubleshooting
Section titled “Troubleshooting”- Sent but no run started. The trigger didn’t match. Check Workflow Executions filtered by your process, and confirm the mailbox/filter (for example, the trigger may only fire on emails that carry a PDF).
- Accepted but the agent extracted nothing. The document was probably scanned without OCR, or is very low quality. Re-scan at a higher DPI.
- Large document rejected. The endpoint has a per-request size limit. Split or compress the document, or ask your admin to raise the limit.