Automation library · Data collection

Track certification requirements with ScrapeGraphAI and GitLab

Started by another system calling it, and works across GitLab. 12 steps, 1 branch: a working afternoon to understand properly.

Medium

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

The flow

Starts it 2Logic 6Service 4

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

  1. 1Incoming WebhookWebhookStarts it
  2. 2Prepare Certification URLsCodeLogic
  3. 3Scrape Certification RequirementsScrapegraph AiService
  4. 4Normalize Requirement DataCodeLogic
  5. 5Aggregate ResultsCodeLogic
  6. 6Get Baseline From GitLabGitlabService
  7. 7Merge Current & BaselineMergeLogic
  8. 8Detect ChangesCodeLogic
  9. 9Requirements Changed?IfLogic
  10. 10Send Rocket.Chat AlertRocketchatService
  11. 11Update GitLab RecordGitlabService
  12. 12Respond to WebhookRespond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
12, with 1 branch
Size
Medium: a working afternoon
Connects to
GitLab
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on another system calling it.

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.