N8N Automation Demo

Problem

n8n workflows built during internship work can't be shared directly — they contain sensitive endpoints and client data. But the automation patterns themselves (document intake → classification → routing → notification) are genuinely reusable and worth documenting.

Approach

Rebuilt one representative workflow pattern from scratch using entirely synthetic data and public APIs. The workflow demonstrates: webhook trigger → document parsing → LLM classification → conditional routing → email/Slack notification.

Key technical decisions

Using n8n's native HTTP Request and Code nodes rather than pre-built integrations, so the pattern is portable to other tools. All credentials replaced with environment variable references.

Note: This is a sanitised personal demo. None of the data, endpoints, or logic comes from client work.

Outcome

In progress. The workflow JSON will be published openly so others can fork and adapt it.