Automation library · Data collection

Sync a GitHub integration catalog from GitHub to StudioCMS pages

Started by a clock, and works across GitHub. 33 steps, 2 branches, 1 loop or waits: large, and worth reading before you trust it with anything live.

Large

33 stepsLarge: read it before trusting it with anything live
2Branches: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 2Logic 22Service 9

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

  1. 1Run Catalog Sync ManuallyManual triggerStarts it
  2. 2Run Daily at 06:00Schedule triggerStarts it
  3. 3Configure Integration CatalogCodeLogic
  4. 4Validate Catalog SettingsCodeLogic
  5. 5Find StudioCMS Catalog FolderStudio CmsService
  6. 6Plan Catalog FolderCodeLogic
  7. 7Route Catalog Folder ActionSwitchLogic
  8. 8Reuse Existing Catalog FolderCodeLogic
  9. 9Create StudioCMS Catalog FolderStudio CmsService
  10. 10Preview Missing Catalog FolderCodeLogic
  11. 11Preserve Unexpected Folder ActionCodeLogic
  12. 12Resolve Catalog Folder ContextCodeLogic
  13. 13Fetch Existing StudioCMS PagesStudio CmsService
  14. 14List GitHub Organization RepositoriesGithubService
  15. 15Select Managed Integration RepositoriesCodeLogic
  16. 16Process Repositories SequentiallySplit In BatchesLogic
  17. 17Compile Integration Catalog ReportCodeLogic
  18. 18Read Repository READMEGithubService
  19. 19Decode README ContentCodeLogic
  20. 20Read Repository Package MetadataGithubService
  21. 21Decode Package MetadataCodeLogic
  22. 22Fetch Latest GitHub ReleaseGithubService
  23. 23Build Structured Catalog PageCodeLogic
  24. 24Plan Safe StudioCMS UpsertCodeLogic
  25. 25Route Catalog Page ActionSwitchLogic
  26. 26Create StudioCMS Integration PageStudio CmsService
  27. 27Update StudioCMS Integration PageStudio CmsService
  28. 28Keep Current Catalog PageCodeLogic
  29. 29Preview Catalog Page CreationCodeLogic
  30. 30Preview Catalog Page UpdateCodeLogic
  31. 31Preserve Catalog Ownership ConflictCodeLogic
  32. 32Preserve Unexpected Catalog ActionCodeLogic
  33. 33Record Repository OutcomeCodeLogic

How it's built

Starts on
A clock
Steps
33, with 2 branches, 1 loop or waits
Size
Large: read it before trusting it with anything live
Connects to
GitHub
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub account. 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?

Take your time. At 33 steps it is large: read it before trusting it with anything live.

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 33 steps before you point it at anything that matters.