Just shipped the most ridiculous thing i've built in a while.
A focus timer that creates custom motivational songs about LITERALLY any goal you want to spend an hour on. Yes, really.
AI has too much enthusiasm for mundane tasks and I'm here for it. Every 15 minutes you get a new banger. the results are slightly unhinged and always motivating.
You'll find it at all good app retailers, especially Apple's App Store: https://testflight.apple.com/join/TB3PTdUu
and Google Play Store: https://play.google.com/store/apps/details?id=com.connectio.hourofpower
This is absolutely brilliant! The "slightly unhinged" part is what makes it work - peak AI absurdism meets genuine utility. Love that you leaned into the ridiculousness instead of trying to make it serious. Getting a new banger every 15 minutes is genius pacing too. Are you...
The 30–60 minute delay then 24-hour follow-up is a sensible cadence. The part I would harden next is the stop conditions: once the cart converts or the customer replies, every channel should cancel, and WhatsApp especially needs a clear opt-in trail before the first send....
Built my portfolio in 1 hour after years of procrastinating. The trick: references first, design every motion yourself, dictate prompts with Wispr Flow, name #GSAP + #Lenis, build with Claude, publish with #Lovable. AI executes, you direct. 👇
Your Logistics Team Shouldn't Have to Chase Every Shipment Manually. 🚢
A shipment is delayed. Your customer wants an update. Your operations team is checking carrier portals, copying tracking numbers into spreadsheets, and sending the same status emails repeatedly.
By the time everyone has the right information, the next shipment needs attention.
The problem isn't a lack of effort. It's disconnected logistics operations.
Common challenges:
Shipment updates scattered across multiple carrier systems.
Delayed shipments discovered too late.
Manual customer status emails.
Tracking spreadsheets that quickly become outdated.
Repetitive follow-ups between operations and customer service.
Limited visibility into shipment exceptions.
The solution: An automated logistics operations workflow built with n8n.
I can design an automation that connects carrier tracking APIs, your shipment database, and customer communication channels.
Instead of manually checking every shipment, your team receives structured updates when something actually needs attention.
What the automation handles:
📦 Shipment Tracking — Retrieve updates from supported carrier APIs.
📊 Operations Visibility — Maintain synchronized shipment records and exception histories.
🔁 Escalation Management — Notify the responsible team when an exception requires action.
The goal: Less repetitive tracking work, faster exception awareness, and more consistent customer communication.
Two ways we can work together:
Option 1: Already have carrier APIs, a TMS, or a defined tracking workflow? Share your requirements, and I'll help design the integration.
Option 2: Not sure which logistics tasks should be automated? We can map your shipment lifecycle and identify the highest-value starting point.
Make your logistics operations easier to manage as shipment volume grows.
Workflow architecture
Scheduled Trigger → Carrier API Request → Normalize Tracking Events → Match Shipment Records → Detect Status Changes → Route Exceptions → AI Summary → Customer Email / Operations Alert → Database Update
Implementation: Authenticate carrier integrations, normalize differing event codes, compare timestamps and event IDs, prevent duplicate alerts, route exceptions by severity, and log delivery failures for retry.
Benefits: Reduced manual tracking, clearer exception ownership, more timely customer updates, and an auditable shipment history.
Result: A centralized shipment monitoring workflow that allows operations teams to focus on resolving exceptions instead of repeatedly checking tracking portals.
The customs-hold exception is the one I'd find hardest to route, since it needs a different owner than a plain delay. Do you map each exception type to its own team in the escalation step, or is it one shared alert queue?