Rachel

Problem

Part of the team correspondence landed in shared inboxes, where messages got lost among notifications — the real recipient saw them too late. We needed a way to route each email to a specific person without opening a mail client.

Solution

A no-code pipeline on n8n: team members forward their emails to a shared Rachel mailbox; a webhook receives each incoming message, n8n parses the subject, sender and body, applies routing rules to find the recipient and posts a formatted notification to their Telegram. Conversation state is stored in a no-code database.

Result

Emails no longer get lost in the shared inbox: every notification reaches the right person in Telegram, reaction time drops to minutes.

My contribution

• Workflow design in n8n: webhook → email parsing → routing → Telegram
• Inbound email parsing (subject, sender, body, attachments)
• Routing rules: where the email goes based on sender and subject
• Telegram message formatting (Markdown, quoting, links)
• No-code database for tracking conversation state

Stack