Data & reporting Starts from form submission
Eligibility report export
Read rows from a sheet, apply eligibility rules and write the results as CSV to an R2 bucket.
How it runs
4 steps, from form submission to outcome
See how “Eligibility report export” runs inside a governed flow.
- Trigger: On form submission. A form submission starts the export.
- Action: Get rows. The rows are read from a sheet.
- Decision: Apply eligibility rules. Governed eligibility rules run on every row.
- Action: Write an object. The results are written as CSV to an R2 bucket.
Step by step
- 1 Trigger On form submission
A form submission starts the export.
- 2 Action Get rows
The rows are read from a sheet.
- 3 Decision Apply eligibility rules
Governed eligibility rules run on every row.
- 4 Action Write an object
The results are written as CSV to an R2 bucket.
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.