Automated Weekly AI Newsletter
Published on 15.10.2025, Edited on 21.01.2026
At a recent happyhotel Dev Offsite, our team spent a lot of time talking about AI trends. During an open space session I got introduced to n8n, an AI workflow automation framework. The idea hit me just a little after: instead of struggling to keep up with all the news of AI research, why not build a system that filters and curates it for me?
The Technical Stack
N8n offers both cloud-hosted and self-hosted options. Since I was building a lightweight workflow and wanted to avoid subscription costs, I opted for the self-hosted version deployed via Docker on my server.
Initially, I attempted to access the n8n UI through an Apache reverse proxy to enable SSL encryption and secure this part of my server. However, n8n proved surprisingly restrictive with reverse proxy configurations, and I found myself losing too much time troubleshooting. That’s why I pivoted to a simpler approach: only exposing the docker container to localhost and then using a SSH Tunnel to access it, if I need to. This way I don’t lose functionality like Error Workflows, that rely on the instance running all the time.
This decision reminded me of the value of pragmatic solutions that suit your needs, allowing me to focus on the functionality without getting stuck chasing some kind of over-engineered perfection.
Building the Workflow
With the infrastructure running smoothly, I got to dive into n8n's workflow ecosystem. After getting inspiration from various examples, I assembled my own pipeline:
- Feed Aggregation: The workflow fetches content from specified RSS feeds
- AI Processing: An AI agent analyzes the aggregated articles using iteratively refined prompts
- Delivery: The curated content is formatted in HTML and sent via email, simultaneously updating my website's project page
The Curation Criteria
The prompt engineering became the most crucial and challenging part of this project, as I wanted a specific mix of content:
- 6-8 articles on AI applications in ecological and environmental fields
- 2-3 articles on general AI research breakthroughs
- 1-2 articles on major tool or model releases
- 0-2 articles on educational posts covering important techniques or frameworks
- 0-1 article on significant industry news
The Hallucination Problem
The biggest source for headaches was quite stubborn. The AI agent kept hallucinating AI involvement in articles that merely mentioned environmental technology. A robotics article about soft sensors became "AI-powered navigation systems." A water quality monitoring project suddenly involved "machine learning analysis", despite no mention of ML in the source.
This led to me spending a lot of time testing and refining the system prompt. The agent now must explicitly identify and quote the exact sentences proving AI usage before selecting any environmental article. If it can't cite specific techniques. like neural networks, computer vision, transformers, reinforcement learning, the article gets excluded, no matter how relevant it seems.
Counterintuitively, I learned that telling an LLM not to do something often backfires. Instead of saying "don't use titles that start with AI for … " I had to build a positive verification framework: "your titles have to be significantly different from one another and start with different formulations."
Output Formatting
The HTML formatting presented its own challenge. Since I'm not comfortable with HTML styling, I had AI generate the template. Through iterative refinement, I arrived at a clean, readable format with proper spacing and typography.
Title generation required fine-tuning through few-shot prompting. Early versions produced generic titles like "AI for Climate Monitoring" or "New AI Breakthrough in Species Detection." I taught the agent to lead with specific techniques instead: "CNNs Detect Deforestation in Satellite Data" or "Transformer-Based Species Classification."
Key Takeaways
This project delivered several unexpected lessons:
- Scoping complexity: Sometimes a pragmatic solution like exposing to localhost beats the theoretically better, at least more fancy, one, which was the SSL setup in this case.
- Prompt engineering is hard work: Iteratively testing and refining prompts is not as easy as it seems, which is related to LLMs not being deterministic
- Negative instructions can go wrong: LLMs often respond better to positive instructions than telling them what not to do.
- Specificity matters: Vague titles and summaries indicate the AI is working from inference rather than facts
Try It Yourself
If you'd like to build your own tailored newsletter, you can set up an n8n instance and import my workflow JSON from GitHub. Just modify the RSS feed Urls, the credentials and adjust the selection criteria to match your interests.
The beauty of this system is its modularity: swap the environmental AI focus for cybersecurity, web development, or any other domain. The verification framework I built for environmental articles can be adapted to catch hallucinations in any technical field.
Want to see the newsletter in action? The latest curated edition is automatically published below every Saturday.