n8n-commit

Export n8n workflows from a GKE pod and commit them via PR.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill n8n-commit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: n8n-commit
Source: https://github.com/declanshanaghy/fenrir-ledger/tree/main/.claude/skills/n8n-commit
Command: npx skills add https://github.com/declanshanaghy/fenrir-ledger --skill n8n-commit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Exports n8n workflows from the running GKE pod in the fenrir-marketing namespace and commits them to infrastructure/n8n/workflows/. Creates a PR automatically.

Core Features & Use Cases

  • Exports all n8n workflows from the live pod in the fenrir-marketing namespace.
  • Copies them into infrastructure/n8n/workflows/, commits any changes, and opens a PR.
  • Use cases include maintaining version-controlled n8n workflows and automating updates via PRs triggered by commands like /n8n-commit.

Quick Start

Run /n8n-commit to export all workflows from the running pod and create a PR with the updated files.

Frequently Asked Questions about n8n-commit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I export n8n workflows from a Kubernetes pod to Git?

Exporting n8n workflows to Git involves extracting configurations from a running GKE pod and committing them to a repository path before opening a pull request. This automation handles the extraction, commit, and PR creation automatically.

Can I automatically create a PR for n8n workflow changes in CI/CD?

Yes, you can automatically create a PR for n8n workflow changes by triggering this process within CI/CD pipelines. It copies workflow files from the pod, commits any differences, and opens a pull request using the gh CLI.

Do I need kubectl and gh CLI to version control n8n configurations?

Yes, you need kubectl and the gh CLI to version control n8n configurations this way. Kubectl provides access to the GKE pod to extract workflows, while the gh CLI is required to automatically create the pull request.

What is the best way to maintain version-controlled n8n workflows?

The best way to maintain version-controlled n8n workflows is to automate exports from the live pod into a Git repository. This ensures traceability by committing configuration changes and opening PRs for review.

Does exporting n8n workflows to Git require a specific Git branch setup?

Yes, exporting n8n workflows to Git requires a git repository rooted on the main branch. This setup ensures that the automated pull request containing the updated workflow files can be created successfully.