template

Convert n8n workflow JSON into environment-agnostic templates with placeholders.

Updated Mar 16, 2026
One-click install
npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill template-mj-agentlab
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: template
Source: https://github.com/MJ-AgentLab/mj-agentlab-marketplace/tree/main/plugins/mj-n8n/skills/mj-n8n-template
Command: npx skills add https://github.com/MJ-AgentLab/mj-agentlab-marketplace --skill template-mj-agentlab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the conversion of n8n workflow JSON, exported from the UI, into environment-agnostic templates. This process replaces environment-specific values with placeholders, making workflows easily adaptable across development, testing, and production environments.

Core Features & Use Cases

  • Environment Normalization: Transforms exported n8n JSON into a reusable template format by replacing hardcoded values (like URLs, credentials, and environment names) with standardized placeholders (e.g., {{ENV_PREFIX}}, {{WECHAT_WEBHOOK_URL}}, "PLACEHOLDER").
  • Workflow Templating: Prepares n8n workflows for CI/CD pipelines by creating a single source of truth that can be rendered into environment-specific configurations.
  • Use Case: After designing a workflow in n8n and exporting its JSON, use this Skill to create a template. Later, you can use a rendering script with environment-specific configuration files (e.g., dev.yaml, prod.yaml) to generate the final, deployable workflow JSON for each environment.

Quick Start

Convert the exported n8n workflow JSON into an environment-agnostic template.

Frequently Asked Questions about template

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

FAQPage Schema
How do I convert n8n workflow JSON into an environment-agnostic template?

An environment-agnostic n8n template replaces hardcoded values like URLs and credentials with placeholders such as `{{ENV_PREFIX}}` and `PLACEHOLDER`. This allows a single exported workflow JSON to be rendered across development, testing, and production environments.

Why does my exported n8n workflow JSON need placeholder substitution for CI/CD?

Exported n8n workflow JSON needs placeholder substitution for CI/CD because it contains hardcoded values and credential IDs. Replacing them with double-brace placeholders creates a single source of truth that a render script can safely configure per environment.

How do I clean up credential IDs in exported n8n JSON?

To clean up credential IDs in exported n8n JSON, this Skill automatically removes or replaces them with standardized placeholders during the template conversion process. This ensures sensitive environment-specific credentials are not exposed in your base workflow templates.

Are the generated n8n base templates valid JSON files?

The generated n8n base templates are not valid JSON files by design. They intentionally contain double-brace placeholders like `{{WECHAT_WEBHOOK_URL}}` that a render script substitutes with environment-specific configuration values during deployment.

Can I use environment-specific configuration files to render n8n workflow templates?

You can use environment-specific configuration files like `dev.yaml` or `prod.yaml` with a rendering script to substitute the double-brace placeholders in the base template. This process generates the final, deployable n8n workflow JSON for each target environment.