Skip to main content
Active developmentWorkflow Automation

Scheduled Research Automation

An n8n automation that researches a defined topic on a schedule, composes a briefing and delivers it by email — a worked example of replacing a recurring manual task.

There is no packaged download for this project yet — the link below goes to the source code.

The problem

Keeping up with a fast-moving technical field means somebody reads through sources and summarises them, repeatedly, at a fixed time every day. It is low-value work that competes directly with actual work, and it stops entirely when the person is away.

The approach

A scheduled n8n workflow that runs research through a model API, composes the briefing, and delivers it through a mail integration on a daily trigger. Credentials are held in the automation platform’s own credential store rather than in the repository, and the repository ships both a manual-trigger version for testing and a production scheduled version, alongside validation that runs on every push.

What is implemented

  • Scheduled daily execution plus a separate manual-trigger workflow for testing
  • Research performed through a model API integration
  • Briefing composition and email delivery through a mail integration
  • Credentials held in the platform credential store rather than committed to the repository
  • Version-control sync scripts for Windows and Unix-like systems
  • Continuous integration that validates workflow JSON, verifies repository structure and scans for accidentally committed credentials
  • A reusable internal library of documented n8n patterns covering JavaScript and Python nodes, expression syntax, node configuration, validation and workflow architecture
  • Planning documents for workflow design

Current status and limitations

  • Nothing runs on its own: it requires a hosted or self-hosted n8n instance plus credentials for the model API and the mail account. It is an automation design, not a service anyone can sign up to.
  • No released version and no packaged download — the workflows are imported into an existing n8n instance.
  • No automated test suite; validation is limited to JSON syntax and structural checks.
  • The repository describes itself as open source, but no licence file is published, so it is not licensed for reuse. This site therefore does not describe it as open source.
  • The subject matter it researches ages quickly, which makes it more useful as a demonstration of automation capability than as a product.

Technology

  • n8n
  • OpenRouter
  • Gmail API
  • GitHub Actions
  • PowerShell

Links


Status
Active development
Last reviewed
2026-10-15

Have a similar problem?

If this is close to something you are dealing with, describe your situation and we will tell you whether it is a good fit.