ACADEMY · FORMS & DATA
Forms & Data Workflows
Design reliable intake, validation and downstream data handoffs.
WHY THIS MATTERS
Bad intake data silently propagates risk into every downstream automation step.
DESIRED OUTCOMEA validated, normalized data package with a confirmed downstream handoff.
How this workflow works
Intake to notification
Form schema → validation → handoff → notification → receipt.
Open lessonDATA ARTIFACT LAB
Do not talk about validation without showing the data that gets rejected.
RAW INPUT · INVALID{
"name": "Lan",
"phone": "09x-12",
"email": "",
"consent": false
}- phone: malformed
- email: required
- consent: missing
VALIDATION → REJECT
CORRECTED INPUT · VALID{
"name": "Lan",
"phone": "+84912345678",
"email": "lan@example.com",
"consent": true
}Schema valid → normalize → hand off.
VALIDATION → PASS
NORMALIZED RECORD · ACCEPTED CONTRACT{
"contact_id": "lead_1042",
"phone_e164": "+84912345678",
"email": "lan@example.com",
"consent_status": "accepted"
}Downstream automation receives one contract, not raw form ambiguity.
APPLY THIS PATTERN
Treat every form as an input contract for downstream automation.
01Validate required fields before any irreversible action.
02Normalize values into a predictable schema before routing.
03Confirm the downstream system accepted the data before notifying success.
DATA FAILURE MODES
Catch bad state before it becomes downstream work.
01Incomplete inputReject missing required values before routing or notification.
02Invalid structureNormalize types, enums, identifiers and dates before automation consumes them.
03Rejected handoffDo not report success until the downstream system confirms the normalized record was accepted.
DATA DEPTH
Reliable automation starts with trustworthy intake.
01Schema
Define required fields, types and allowed values before submission.
02Validation
Separate incomplete or unsafe inputs from executable requests.
03Handoff receipt
Confirm downstream systems received and accepted the normalized data.
EXPECTED MATERIAL OUTPUTA validated data package with a traceable downstream handoff.
PUT THE PATTERN TO WORK
Follow one intake record through validation, normalization, downstream acceptance and receipt.