n8n Workflow: Sync GitHub Integration Catalog to StudioCMS

Keep your StudioCMS integration catalog in sync with GitHub—automatically

This n8n workflow reads each matching GitHub repository’s README, package.json, and latest release, then creates or updates a deterministic integration page in StudioCMS. It also flags conflicts and warnings and supports a safe `preview mode` so you can review changes before publishing.

What this workflow does

• Runs on demand or daily (scheduled for 06:00), validating catalog configuration such as GitHub org, repository prefix, folder name, slug prefix, and preview mode.
• Validates/creates the target StudioCMS folder by name only when preview mode is disabled; otherwise it reports the folder creation it would perform.
• Loads existing StudioCMS pages once, lists repositories in the configured GitHub organization, and filters to non-fork repositories matching the configured repository name prefix.
• Processes repositories sequentially, building a standardized Markdown catalog page per integration using repository content (README + package.json) and the latest GitHub release.
• Creates or updates pages safely via exact slug matching and ownership checks—without overwriting unowned pages. Archived repos are marked as drafts.
• Reports conflicts, warnings, and proposed changes, then outputs a final summary of created/updated/unchanged items, preview-only actions, and errors.

Use cases

• Automation engineers maintaining a StudioCMS integration catalog for a growing set of GitHub integrations.
• SaaS operators who need release-note propagation from GitHub into StudioCMS without manual page edits.
• Teams using preview mode to review catalog changes before pushing updates to production.

Technical details

• GitHub integration (credentials to list organization repos; read README, package.json, and latest release).
• StudioCMS page sync with exact slug matching and ownership/conflict protection.
• n8n nodes/logic: code, github, switch, sticky note, manual trigger, and batching via split in batches.

Setup note: Add GitHub API credentials with access to list the target organization.