Automation library · Documents and files

Weekly GitHub trends translated to zh-ch with DeepSeek

Started by a clock, and works across Email. It hands the judgement calls to DeepSeek. 11 steps: a working afternoon to understand properly.

MediumCalls a model: DeepSeek

11 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 1Model 2Logic 6Service 2

The steps in the order they run, from what starts it.

  1. 1DeepSeek Chat ModelLm Chat Deep SeekModel
  2. 2Schedule TriggerSchedule triggerStarts it
  3. 3Send Email and CodeChain LlmModel
  4. 4Request to Github TrendHttp RequestService
  5. 5CodeCodeLogic
  6. 6Extract BoxHtmlLogic
  7. 7Send EmailEmail SendService
  8. 8Extract all repositoriesHtmlLogic
  9. 9Turn to a listSplit OutLogic
  10. 10Extract repository dataHtmlLogic
  11. 11Set Result VariablesSetLogic

How it's built

Starts on
A clock
Steps
11
Size
Medium: a working afternoon
Connects to
Email
Model
DeepSeek

Questions

What does it need to run?

An n8n account, plus your own Email account, and a key for DeepSeek. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

Yes. It calls DeepSeek. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 11 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 11 steps before you point it at anything that matters.