- Setup
- 45 minutes
- Tested with
- n8n 1.90+
- File
- 23.6 KB
- Revision
- 1.0.0
The entry, in plain prose.
A data-ops workflow that validates uploaded CSVs, normalizes columns, enriches company domains, and exports clean files.
How it runs.
- 01.
Intake
Read Binary File receives the inbound payload. Schema validation runs first; failures are surfaced rather than silently dropped, so you never lose context to a malformed webhook.
- 02.
Enrichment
Spreadsheet File → HTTP Request performs deduplication, enrichment, and routing logic. Each step is idempotent; transient retries are safe by design.
- 03.
Routing
Owner routing applies a round-robin fallback when no explicit assignment exists. Holiday-mode flags and on-call schedules are respected where the source system surfaces them.
- 04.
Delivery
Google Drive commits the result. Errors past this point alert via Slack with the failing payload attached; downstream systems never see partial state.
Indexed tools.
- Read Binary File
- Spreadsheet File
- HTTP Request
- Google Drive
License.
| Tier | Seats | Resale | Price |
|---|---|---|---|
| Single Business | 1 | Not permitted | $49.00 |
| Client Delivery | 10 | Not permitted | $149.00 |
Tested through twelve client deployments before archival. Setup consistently lands under 45minutes when integrations are pre-authorised. Recovers from upstream failures without intervention.