Trigger from a file upload
Start care flows in batches by uploading a CSV to an Awell FTP server, with almost no engineering work.
This trigger starts care flows from files uploaded to an FTP server Awell provisions. It takes practically no engineering effort and starts many care flows in one batch.
Not to be confused with collecting files and images, which is a form question type. This page is about a file that starts care flows.
Awell polls the server and starts the flows it finds
- Awell provisions a secure FTP server and provides the login credentials.
- Files arrive as CSV (or a similar format), in a structure agreed in advance.
- Awell polls the server periodically, for example hourly. When it finds a new file it processes it and starts the required care flows.
- Awell handles the patient side: checking whether the patient already exists, creating the record if not, then starting the flow.
- Awell keeps logs for auditability.
Monitor → Data Ingestion is where those runs are reviewed, per file.
Polling is the part to design around: enrollment happens on the poll interval rather than the moment the file lands. If a flow needs to start within seconds, use a webhook instead.
Best for scheduled batches and systems that can't call an API
- A batch of patients enrolls on a schedule, for example a weekly list from another team.
- The source system can produce a file but can't call an API.
- The audit trail a file leaves behind is worth having.
Agree the format first
Agree the file format before the first upload: which columns map to which baseline data points, what identifies the patient, and what happens to a malformed row.
Next steps
Next: ADT feeds for hospital-driven enrollment.