Skip to content

About the project

I taught my inbox to do the chores.

FlowPack is 6 self-hosted n8n workflows — 25 nodes across 5 integrations — that quietly handle the admin around my day. Here's why it exists, how it came together, and the bit that nearly didn't.

The why

Automation, done well, is invisible. You don't notice the workflow — you notice that the thing you used to do by hand just… happened. That's the whole goal here: take the small, repetitive, slightly annoying parts of a morning and make them disappear.

It's also a love letter to a tool. n8n looks like a toy until you wire your first real thing through it; then it looks like a power tool. I wanted a tidy set of examples — mine, that I actually use — that someone could import and learn from in an afternoon.

How it came together

A short, honest timeline.

  1. Feb 2026

    The morning-tab problem

    It started as a complaint, not a project. Every morning began the same way: weather tab, jobs tab, calendar tab, GitHub tab. Ten minutes of context-loading before I'd done anything. I wanted that to arrive, not be fetched.

  2. Mar 2026

    Scoping — one flow, end to end

    Rather than design all six up front, I built the Morning Briefing properly: three parallel API calls, one Code node, one email. Getting one workflow truly clean told me what the other five should look like.

  3. Apr 2026

    The pack takes shape

    Job digest, calendar agenda, and the Telegram capture inbox landed in quick succession — they share the same trigger → fetch → deliver spine, so each was faster than the last.

  4. Late Apr 2026where it got hard

    The part that broke everything

    Two days lost to gremlins. RemoteOK sometimes returns its array double-wrapped, so my filter silently matched nothing. Google's OAuth redirect URI has to be character-perfect. And every date was an hour off until I pinned Asia/Kolkata in every single workflow. Unglamorous, and exactly the work that makes the difference.

  5. May 2026

    Teaching it to think

    Added the AI summarizer: a synchronous webhook that hands text to Claude and returns five bullets and an action item. Mirrors my day-job LLM work, shrunk to a single reusable endpoint.

  6. May–Jun 2026

    Polish & this showcase

    Real empty states, email HTML that survives Gmail, keyword tuning — then this site: live node graphs rendered straight from each workflow's JSON, so you can read the wiring instead of taking my word for it.

Key features

What makes it more than a folder of JSON.

Live node graphs

Every workflow renders its real n8n topology as SVG — laid out from the actual node positions and connections in the JSON. What you see is what imports.

Copy or download any workflow

Each card hands you the exact JSON. Drop it into n8n → Import from File, attach your own credentials, and it runs.

Three trigger styles

Cron schedules, an event-driven Telegram trigger, and an on-demand HTTP webhook — a small tour of how automations actually get kicked off.

A real AI endpoint

POST text, get a structured summary back from Claude — synchronously, with the API key safely in a credential.

Interesting decisions

The choices worth defending.

Defensive parsing over trust

RemoteOK's response shape isn't guaranteed, so the job digest normalizes it before filtering: if it arrives as a single array-wrapped item, unwrap it first. One line that turns a silent empty inbox into a reliable one.

Inline date math, no extra nodes

The GitHub digest computes 'seven days ago' right in the request URL using n8n's Luxon helpers. Fewer nodes, less to read, nothing to keep in sync.

Synchronous webhook for the AI flow

responseMode: responseNode means the caller waits for Claude and gets clean JSON back in the same request — so the summarizer behaves like an API, not a fire-and-forget job.

Empty states are handled, not ignored

The calendar agenda uses alwaysOutputData and a fallback line, so a day with no meetings still emails 'Enjoy the focus time' instead of failing quietly.

Tech stack

And why each one earned its place.

n8nVisual orchestration I can self-host — no vendor lock, no per-run billing.
JavaScript Code nodesTen readable lines beat a tangle of UI toggles once logic gets interesting.
Claude Haiku 4.5Fast and cheap summarization that's still genuinely good.
Google & Telegram APIsFirst-party OAuth for Gmail, Calendar, Sheets; the Bot API for zero-friction capture.
DockerKeeps the n8n instance up and reproducible across machines.
Next.js + TailwindA fast, static showcase that deploys to Vercel for free.

Want to build something — or collaborate?

Whether it's an automation, an LLM system, or something nobody's tried yet, I'm up for it.