Automation library · Alerts and monitoring

Qualify Polish public tenders with Anthropic and Telegram

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

MediumCalls a model: Claude

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

The flow

Starts it 2Model 4Logic 3Service 2

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

  1. 1Manual Execution TriggerManual triggerStarts it
  2. 2Scheduled Trigger: Twice DailySchedule triggerStarts it
  3. 3Claude Language ModelLm Chat AnthropicModel
  4. 4Fetch Tender DetailsTool Http RequestModel
  5. 5Parse Tender VerdictOutput Parser StructuredModel
  6. 6Set API and KeywordsSetLogic
  7. 7Qualify Tender AgentAgentModel
  8. 8Fetch Tender AnnouncementsHttp RequestService
  9. 9Generate Tender ReportCodeLogic
  10. 10Local Pre-Filter TendersCodeLogic
  11. 11Send Telegram NotificationTelegramService

How it's built

Starts on
A clock
Steps
11
Size
Medium: a working afternoon
Connects to
Telegram
Model
Claude

Questions

What does it need to run?

An n8n account, plus your own Telegram account, and a key for Claude. 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 Claude. 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.