Automation library · Alerts and monitoring

Alert crop scouts to wind-driven pest threats with GBIF

Started by a clock, and works across Slack. It hands the judgement calls to Gemini. 10 steps, 2 branches: a working afternoon to understand properly.

MediumCalls a model: Gemini

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

The flow

Starts it 1Model 2Logic 4Service 3

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

  1. 1Every Morning at 6amSchedule triggerStarts it
  2. 2Gemini LLM ModelLm Chat Google GeminiModel
  3. 3Set Search ParametersSetLogic
  4. 4Scout Alert Generator AgentAgentModel
  5. 5Fetch GBIF Pest OccurrencesHttp RequestService
  6. 6Send Slack Alert to ScoutsSlackService
  7. 7Check for Nearby PestsIfLogic
  8. 8Fetch Wind DataHttp RequestService
  9. 9Calculate Wind Threat AlignmentCodeLogic
  10. 10Check Wind Alignment ThreatIfLogic

How it's built

Starts on
A clock
Steps
10, with 2 branches
Size
Medium: a working afternoon
Connects to
Slack
Model
Gemini

Questions

What does it need to run?

An n8n account, plus your own Slack account, and a key for Gemini. 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 Gemini. Model calls are billed by the provider, not by n8n.

How long does it take to set up?

Plan an afternoon. 10 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 10 steps before you point it at anything that matters.