export-cloud-workflow

Export n8n cloud workflows to local JSON files for version control.

1|Updated Feb 6, 2026

Search Tags:#API #version control #n8n #cloud migration #workflow export #JSON normalization

Ready to run

npx skills add https://github.com/williamsforeal/Cyclone-SS --skill export-cloud-workflow

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: export-cloud-workflow
Source: https://github.com/williamsforeal/Cyclone-SS/tree/main/.cursor/skills/export-cloud-workflow
Command: npx skills add https://github.com/williamsforeal/Cyclone-SS --skill export-cloud-workflow

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of moving working n8n automations off an n8n cloud instance and into your local Cyclone-SS repository so you can version, review, and run them consistently.

Core Features & Use Cases

List and select cloud workflows: Connect to the n8n cloud API and present available workflows when no ID or name is provided.
Export and normalize workflow JSON: Download a specific workflow, extract its JSON, and remove cloud-specific metadata such as instance IDs and cloud URLs.
Save into the local workflows folder: Convert the workflow name into a safe filename and write it to the /workflows directory, with overwrite handling guidance.

Quick Start

Run the export command and provide the workflow name or ID to download it from the n8n cloud instance into the local workflows directory.

Frequently Asked Questions about export-cloud-workflow

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

FAQPage Schema

How do I migrate n8n cloud workflows to a local repository for version control?▼

To migrate n8n cloud workflows, you can export specific workflows by ID or name into your local repository. This process downloads the workflow JSON, removes cloud-specific metadata, and writes the normalized file to a local /workflows directory for consistent versioning.

How do I list available workflows from my n8n cloud instance before exporting?▼

You can list available workflows from your n8n cloud instance by connecting to the cloud API without providing a specific workflow ID or name. The tool enumerates and presents available cloud workflows, allowing you to select the correct automation for export.

Do I need an API key to export workflows from the n8n cloud?▼

Yes, you need an API key to export workflows from the n8n cloud. You must authenticate using the N8N_CLOUD_API_KEY and N8N_CLOUD_URL environment variables, or alternatively provide session credentials to access your cloud workflows endpoints.

What is JSON normalization when exporting n8n cloud workflows?▼

JSON normalization when exporting n8n cloud workflows is the process of cleaning cloud-specific metadata, such as instance IDs and cloud URLs, from the downloaded workflow file. This ensures the workflow JSON is portable and ready for local version control.

How are exported n8n workflow files named in the local directory?▼

Exported n8n workflow files are saved with deterministic filenames in the local /workflows directory. The system converts the workflow name into a safe filename, ensuring consistent file naming and providing guidance for overwrite handling during the export process.

Can I download a specific n8n workflow by its name instead of its ID?▼

Yes, you can download a specific n8n workflow by providing its name instead of its ID. The tool accepts either a workflow name or ID as input to target and download the correct automation from the n8n cloud instance for local migration.