Workflow code: WF-CSV03
Email Format Normalizer is aimed at low-risk cleanup of email fields inside CSV files. It helps position Flowwyn as a practical workflow catalog for common operational cleanup tasks without promising external validation or outbound actions.
Points estimate: Estimated usage: low point cost for routine normalization tasks.
Privacy note: The catalog does not expose files publicly and does not imply creator file access.
Who it is for
- Teams standardizing contact exports before import.
- Marketing operations reviewing inconsistent email field formatting.
- Support teams consolidating CSV-based contact lists.
Input requirements
- CSV input with one or more email-related columns.
- Best used when formatting cleanup matters more than verification.
- Header names should make email columns identifiable.
Output
- A normalized CSV output focused on email formatting cleanup.
- A short workflow summary that explains the normalization scope.
Limitations
- Does not verify inbox existence or external service deliverability.
- Does not send email or connect to third-party providers.
- Execution is not enabled yet in this local catalog release.
Workflow access
Email Format Normalizer
This page explains the workflow scope before you commit to a run. Universal CSV Cleaner already supports a browser-local demo plus an authenticated hosted path. Other workflows remain catalog-first until their hosted execution path is ready.
View run accessBrowser-local demo access stays visually separate from the hosted upload and paid-run flow. Account access, points, and private output delivery begin only on the hosted path.
FAQ
Does this workflow verify whether an email address is real?
No. This catalog entry does not imply external verification or API-based enrichment.
Can it send outreach after normalization?
No. Automated email sending is outside the MVP boundaries.