FlowPack: Six Automations That Run My Day Before I'm Awake
Six Automations That Run My Day Before I'm Awake
Six n8n workflows I use daily (weather, jobs, my calendar, the week's best repos, a Telegram capture inbox and an AI summarizer endpoint), plus a Next.js site that renders each one's node topology as an SVG graph from the same JSON you would import.
- Year
- Oct 2025
- Timeline
- 4 weeks
- Type
- Automation
- Status
- Live
6 flows
Six automations run on a schedule in Asia/Kolkata. The showcase renders each one's node graph from the same JSON you would import into n8n.
Overview
I kept doing the same ten minutes of admin every morning: checking weather, scanning jobs, opening my calendar, skimming repos. So I automated it. FlowPack is six n8n workflows plus a Next.js site that shows the wiring of each one. Every workflow is a .json you can import into your own n8n.
The hard parts
- 01
Drawing node graphs that never drift from the workflows: the site has to render the exact files you would import, not hand-drawn diagrams.
- 02
RemoteOK occasionally double-wraps its JSON array, which makes the keyword filter match nothing and produces an empty inbox with no error.
- 03
Making a webhook behave like a synchronous API while it waits on Claude.
- 04
Days with no calendar events used to fail without saying anything useful.
The approach
Every flow follows the same shape (trigger, fetch and 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 server-side as an SVG directed graph from the node positions and connections, so the diagram always matches the workflow. The edge cases are handled explicitly: the double-wrapped array is unwrapped before filtering, responseMode: responseNode makes the AI webhook wait and return clean JSON, and alwaysOutputData plus a fallback string means an empty day still emails "Enjoy the focus time."
Outcome
The morning admin is done before I wake up, and the site lets people read the wiring instead of trusting a screenshot. No secrets ship in the files: every credential is an n8n reference resolved at runtime, so the workflows are safe to publish and import as they are.
What I'd do differently
It is personal tooling, so it has no retries or alerting on failed runs yet. That is the first thing I would add if other people used it. I would also add an India-specific job source, since the current ones skew remote and US-heavy.
Stack
Like what you see?
Let's build the next one.
Hiring, or have a problem that needs this kind of engineering? I read every message myself.