Overview

I kept doing the same ten minutes of admin every morning — checking weather, scanning jobs, opening my calendar, skimming repos. So I taught a handful of small robots to do it for me. FlowPack is those robots: six production-ready n8n automations, plus a Next.js site that lets you read the wiring instead of taking my word for it. Every workflow is a .json you can import into your own n8n.

Tech Stack

Challenges

• Drawing node graphs that never drift from reality — the site has to render the exact files you'd import, not hand-drawn diagrams.
• RemoteOK occasionally double-wraps its JSON array, which silently makes the keyword filter match nothing — an empty inbox with no error.
• Making a webhook behave like a synchronous API while it waits on Claude.
• Days with no calendar events failing quietly instead of saying something useful.

Solution

Every flow follows the same spine — trigger → fetch & shape → deliver — across cron, an event-driven Telegram trigger, and an on-demand webhook. The showcase imports the same JSON n8n does and renders it as a pure, server-side SVG directed graph straight from the node positions and connections, so the diagram can't lie. The fiddly bits are handled defensively: unwrap the double-wrapped array before filtering, responseMode: responseNode to make the AI webhook wait and return clean JSON, and alwaysOutputData plus a fallback string so an empty day still emails "Enjoy the focus time."

Outcome

I stopped doing the morning-admin shuffle — it's done before I wake up — and the site lets people read the wiring instead of trusting a screenshot. Nothing secret ships in the files: every credential is an n8n reference resolved at runtime, so the workflows are safe to publish and import as-is.

What I'd do differently

It's personal tooling, so it has no retries or alerting on failed runs yet — the first thing I'd add if it graduated to a shared tool. I'd also wire in an India-specific job source, since the current ones skew remote and US-heavy.