# Sync a GitHub integration catalog from GitHub to StudioCMS pages: n8n workflow

> 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.

Source: https://millionrounds.com/workflow/sync-a-github-integration-catalog-from-github-to-studiocms-p (Millionrounds; every figure on the page links to its filing or article)

[Automation library](https://millionrounds.com/workflows) · [Data collection](https://millionrounds.com/workflows?category=Data+collection#library)

# 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

[Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fsync-a-github-integration-catalog-from-github-to-studiocms-p)

**33 steps** Large: read it before trusting it with anything live

**2** Branches: places the flow splits

**1** Loop or waits

**1** Service it connects to

## The flow

Starts it 2 Logic 22 Service 9

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

- 1 **Run Catalog Sync Manually** Manual trigger *Starts it*
- 2 **Run Daily at 06:00** Schedule trigger *Starts it*
- 3 **Configure Integration Catalog** Code *Logic*
- 4 **Validate Catalog Settings** Code *Logic*
- 5 **Find StudioCMS Catalog Folder** Studio Cms *Service*
- 6 **Plan Catalog Folder** Code *Logic*
- 7 **Route Catalog Folder Action** Switch *Logic*
- 8 **Reuse Existing Catalog Folder** Code *Logic*
- 9 **Create StudioCMS Catalog Folder** Studio Cms *Service*
- 10 **Preview Missing Catalog Folder** Code *Logic*
- 11 **Preserve Unexpected Folder Action** Code *Logic*
- 12 **Resolve Catalog Folder Context** Code *Logic*
- 13 **Fetch Existing StudioCMS Pages** Studio Cms *Service*
- 14 **List GitHub Organization Repositories** Github *Service*
- 15 **Select Managed Integration Repositories** Code *Logic*
- 16 **Process Repositories Sequentially** Split In Batches *Logic*
- 17 **Compile Integration Catalog Report** Code *Logic*
- 18 **Read Repository README** Github *Service*
- 19 **Decode README Content** Code *Logic*
- 20 **Read Repository Package Metadata** Github *Service*
- 21 **Decode Package Metadata** Code *Logic*
- 22 **Fetch Latest GitHub Release** Github *Service*
- 23 **Build Structured Catalog Page** Code *Logic*
- 24 **Plan Safe StudioCMS Upsert** Code *Logic*
- 25 **Route Catalog Page Action** Switch *Logic*
- 26 **Create StudioCMS Integration Page** Studio Cms *Service*
- 27 **Update StudioCMS Integration Page** Studio Cms *Service*
- 28 **Keep Current Catalog Page** Code *Logic*
- 29 **Preview Catalog Page Creation** Code *Logic*
- 30 **Preview Catalog Page Update** Code *Logic*
- 31 **Preserve Catalog Ownership Conflict** Code *Logic*
- 32 **Preserve Unexpected Catalog Action** Code *Logic*
- 33 **Record Repository Outcome** Code *Logic*

## 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.

## Run it in n8n

- **Create your n8n account** Free to start. n8n is where the workflow runs. [Create an n8n account ↗](https://millionrounds.com/n8n)
- **Download the workflow** Free with a Millionrounds account. [Download free](https://millionrounds.com/login?next=%2Fapp%2Fworkflow%2Fsync-a-github-integration-catalog-from-github-to-studiocms-p)
- **Paste it into n8n** Open a new workflow in n8n and paste. Then connect your own accounts.

Stored with the author's traces removed: canvas notes, instance identifiers, saved credential names and any live document they had left behind.

## Connects to

Each opens the other workflows that use it.

[GitHub](https://millionrounds.com/workflows?service=GitHub#library)

## Workflows like it

Also data collection, with the same services where possible, closest in size first.

- [**Automatic Typebot flows two-way sync with GitHub** 27 steps · GitHub](https://millionrounds.com/workflow/automatic-typebot-flows-two-way-sync-with-github)
- [**Back up and restore n8n workflows with GitHub** 27 steps · GitHub](https://millionrounds.com/workflow/back-up-and-restore-n8n-workflows-with-github)
- [**Selectively import workflows** 26 steps · GitHub](https://millionrounds.com/workflow/selectively-import-workflows)
- [**Analyze npm packages with Firecrawl and GitHub** 24 steps · calls a model · GitHub, Slack](https://millionrounds.com/workflow/analyze-npm-packages-with-firecrawl-and-github)
- [**Bidirectional GitHub workflow sync & version control** 22 steps · GitHub](https://millionrounds.com/workflow/bidirectional-github-workflow-sync-and-version-control)
- [**Find and track flaky CI jobs in GitHub Actions with OpenAI** 19 steps · calls a model · GitHub, Slack](https://millionrounds.com/workflow/find-and-track-flaky-ci-jobs-in-github-actions-with-openai)