Automation library · Data collection

Certification requirement tracker with Telegram and Zendesk

Started by a clock, and works across Telegram and Zendesk. 12 steps, 1 branch, 1 loop or waits: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
1Branch: places the flow splits
1Loop or waits
2Services it connects to

The flow

Starts it 1Logic 6Service 5

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

  1. 1Daily CheckSchedule triggerStarts it
  2. 2Prepare Certification URLsCodeLogic
  3. 3Iterate URLsSplit In BatchesLogic
  4. 4Scrape Certification PageScrapegraph AiService
  5. 5Enrich with Industry APIHttp RequestService
  6. 6Log Scrape ErrorCodeLogic
  7. 7Combine Scraped + EnrichedMergeLogic
  8. 8Send Error AlertTelegramService
  9. 9Transform & ValidateCodeLogic
  10. 10Is New/Updated?IfLogic
  11. 11Create Zendesk TicketZendeskService
  12. 12Send Telegram UpdateTelegramService

How it's built

Starts on
A clock
Steps
12, with 1 branch, 1 loop or waits
Size
Medium: a working afternoon
Connects to
Telegram, Zendesk
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Telegram and Zendesk accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

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