Quick post about a change I made that's worked out well.

I was using OpenAI API for automations in n8n — email summaries, content drafts, that kind of thing. Was spending ~$40/month.

Switched everything to Ollama running locally. The migration was pretty straightforward since n8n just hits an HTTP endpoint. Changed the URL from api.openai.com to localhost:11434 and updated the request format.

For most tasks (summarization, classification, drafting) the local models are good enough. Complex reasoning is worse but I don't need that for automation workflows.

Hardware: i7 with 16GB RAM, running Llama 3 8B. Plenty fast for async tasks.

Been running n8n with Ollama for a few months now for work automation. Wanted to share what I've learned since it's not super well-documented.

The setup is just Docker Compose with n8n + Ollama + Postgres. n8n's HTTP Request node talks directly to Ollama's REST API — no custom nodes needed.

What I'm running:

• Email digest every morning (IMAP → Ollama → Slack)
• Document summarization (PDF watcher → Ollama → notes)
• Lead scoring from form webhooks

Zero API costs, everything stays on my server. If anyone wants the workflow templates I have a pack: https://workflows.neatbites.com/

Happy to answer questions about the setup.

Honest question: does anyone read DESTRUCTOID's reviews and feel like the score doesn't match what they actually wrote?

No Mans Sky is a recent example — ? with writing that reads more like a 1/10.

I've been documenting this kind of thing at https://reviewofareview.com/destructoid-no-mans-sky/ if anyone wants to dig in.

If you archive emails to S3 (via AWS SES inbound or other pipelines), QuickMailBites lets you browse them with a proper native email client.

No need to write scripts to pull emails from S3 anymore — just configure the bucket and folder prefix.

For anyone using AWS SES inbound to route email into S3 — there is now a native email client that reads directly from your bucket.

QuickMailBites v0.1.0:

• Native S3 backend: browse SES-routed emails as if they were in an inbox
• Also works as a normal IMAP or Gmail client
• Flutter-based (Linux, Windows, Android)
• Keyboard-driven (vim shortcuts)
• Free and open source

Sharing a side project: a Flutter desktop+mobile email client with a unique feature — it reads raw MIME emails directly from AWS S3 buckets.

Tech highlights:

• Flutter desktop (Linux/Windows) + Android
• Custom S3 backend service (aws_s3_client)
• MIME parsing from scratch
• IMAP + Gmail OAuth also supported
• Keyboard shortcuts throughout

Landing page has Linux, Windows, and Android APK downloads.

Free and open source Flutter email client. Unique feature: reads raw MIME emails directly from AWS S3 buckets. Also supports IMAP and Gmail OAuth.

Linux, Windows, Android. Keyboard-driven. MIT licensed.

Sharing a native email client I built — it reads raw emails directly from AWS S3 buckets (for those routing email via AWS SES to S3), plus standard IMAP and Gmail OAuth.

Not Electron — real Flutter native build. Keyboard shortcuts (vim-style). Available as Linux binary, Windows installer, and Android APK.

Built an email client that reads raw MIME emails directly from AWS S3 buckets. If you route inbound email via AWS SES to S3, this is the client for you.

Features:

• Native S3 support (browse emails directly from your bucket)
• IMAP + Gmail OAuth for regular email too
• Built with Flutter (not Electron) — real native performance
• Keyboard-driven: j/k navigation, r=reply, c=compose
• Cross-platform: Linux, Windows, Android
• Free and open source

Downloads on the landing page.