Data & reporting Starts from form submission
Document intake and retention
Collect documents, decide the retention class, store them in S3 and hand off processing to Lambda.
How it runs
4 steps, from form submission to outcome
See how “Document intake and retention” runs inside a governed flow.
- Trigger: On form submission. Documents are collected through a form.
- Decision: Decide the retention class. A governed decision sets the retention class.
- Action: Upload a file. The documents are stored in S3.
- Action: Invoke a function. Processing is handed off to Lambda.
Step by step
- 1 Trigger On form submission
Documents are collected through a form.
- 2 Decision Decide the retention class
A governed decision sets the retention class.
- 3 Action Upload a file
The documents are stored in S3.
- 4 Action Invoke a function
Processing is handed off to Lambda.
Governed by design
The decision step is a DMN model: rules your team can read, test and version, instead of logic hidden in code. Runs record the model or flow version that produced the outcome, so answers stay explainable.
Related use cases
Browse all →- Data & reporting Eligibility report export Read rows from a sheet, apply eligibility rules and write the results as CSV to an R2 bucket.
- Finance ops Expense report review Check claims against policy limits, route exceptions to a reviewer and log the result to a sheet.
- Approvals Employee onboarding Approve the new hire, create and share a Drive folder and send the welcome mail.