القائمة
Export all workflows from the local n8n instance into version-controlled JSON under apps/automation/workflows/. Use when the user asks to export, pull, snapshot, or sync workflows from the local n8n.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | n8n-export |
| description | Export all workflows from the local n8n instance into version-controlled JSON under apps/automation/workflows/. Use when the user asks to export, pull, snapshot, or sync workflows from the local n8n. |
Fetches every workflow from the local n8n instance via the REST API and writes each one to apps/automation/workflows/<slug>/workflow.json with instance-specific fields stripped for clean diffs.
pnpm --filter automation n8n:ps shows it).apps/automation/.env has N8N_API_KEY set. If missing, stop and direct the user to create one at http://localhost:5678/settings/api and paste into .env.Pre-flight checks:
grep -E '^N8N_API_KEY=.+' apps/automation/.env >/dev/null || echo 'MISSING N8N_API_KEY'
curl -sf http://localhost:5678/healthz >/dev/null || echo 'n8n not reachable'
Run the export:
pnpm --filter automation workflows:export
Report the summary to the user (added / updated / removed / skipped-with-notes counts printed by the script).
Instance-specific fields (id, versionId, createdAt, updatedAt, triggerCount, active, shared, meta, pinData) are removed before writing. Tag IDs/timestamps are stripped too; tag names are kept.
If apps/automation/workflows/<slug>/README.md exists and is non-empty, the script will NOT delete that directory even if the workflow has been removed from n8n. It warns instead, so you notice the dangling directory and can resolve it intentionally.
Credentials are never exported. Only the reference (name + id) appears in the JSON; secrets stay in n8n's encrypted store.
Start the local n8n instance for the Strapi community hub. Use when the user asks to start, launch, bring up, or run n8n or the automation stack. Pass --mcp to also bring up n8n-mcp (requires N8N_API_KEY and MCP_AUTH_TOKEN in .env).
Show the health and status of the local n8n automation stack. Use when the user asks about n8n status, health, whether it is running, or which containers are up.
Import workflows from apps/automation/workflows/ into the local n8n instance. Use when the user asks to import, push, load, or sync workflow JSON files to the local n8n.
Restart the local n8n automation stack, preserving whatever profile (plain or mcp) is currently running. Use when the user asks to restart, reload, or reboot n8n.
Stop the local n8n automation stack. Use when the user asks to stop, shut down, halt, or bring down n8n. Data in the n8n_data volume persists across stops.
Domain-expertise guide for designing, building, validating, and modifying n8n workflows using the n8n-mcp tools. Use whenever the user asks to build, create, design, edit, or validate an n8n workflow. Requires the n8n-mcp server to be running (see n8n-start).