Every way a document can reach a flow: upload, email, mailbox, SFTP, FTP, S3 and API.
Every plan has every way in. You set them up on the flow's Arrives step, and only a workspace admin can change them. Upload is always on: drop a file on the flow's Documents.
Upload
Press Upload in the top bar and drop in any document. We work out what it is and put it with the flow whose documents it is like. If none fits, or we are not sure, it waits for you in Documents. A flow's own Documents page still takes files straight into that flow. See Files we read for the file types and the 10 MB limit.
Your workspace's email address
When your workspace has an address, it is shown on Add documents and at the top of each flow's Arrives step. Forward any email with documents attached to it, and we sort each file as if you had uploaded it. Each flow keeps its own address too.
From your phone
Android. Install ProcuLink from Settings first. Then, in any app, tap Share and choose ProcuLink. Share one file or several: photos, PDFs and the other files we read. Shared files always wait on your phone until you choose: ProcuLink names them, and Add them sends them in just as Add documents does, or you can delete them from your phone instead. This works offline too: the files wait until you are connected again. Your phone keeps up to 10 shared files, 50 MB in all.
iPhone. An iPhone does not list web apps in its Share menu. Copy your workspace's address from Add documents, then in any app tap Share, choose Mail, and send the file to that address. It is read and sorted like any document sent to that address.
The flow's email address
Every flow also has its own email address, on its Arrives step. Documents sent there skip the sorting and go straight into that flow. Anyone can forward or write to it. Each attached file we can read becomes a document in that flow. If a message has no file we can read, the text of the message becomes the document instead.
You can switch the address off, or get a new one. The old address stops working at once. See Receive documents by email.
Pickups
A pickup collects files from a place you already use. It checks every five minutes and takes each new file once. There are three kinds:
- A mailbox. We read unread messages in a folder of an IMAP mailbox. See Collect documents from a mailbox.
- A server. We collect files from a folder on an SFTP, FTPS or FTP server. See Collect documents from an SFTP or FTP server.
- An S3 bucket. We collect objects from a bucket, or from one prefix in it. See Collect documents from an S3 bucket.
The files stay where they are. We never move or delete a file on your server or in your bucket. The one change we make is in a mailbox, where a message we have finished with is marked as read.
The API
Your own system can post a file to the flow, using a key you create in Settings. You can also give the flow a web address to call when a document has been read or sent. See Send documents by API and the API reference.
What happens next
Whichever way a document arrives, it is read in the same way and appears on the flow's Documents page.
If your plan cannot take more documents, the email address and the pickups pause, and the Arrives step says so. See the billing FAQ.
A pickup ignores files of a type we do not read. A file over 10 MB is skipped, and the pickup tells you how many it skipped.