My $79 Fixed-Price n8n Builds Are One Config File: How I Ship Custom Workflows Without Rewriting Them

Описание и применение

Автор продаёт фикс‑ценные сборки n8n за 79 $, используя единственный канонический workflow и 40‑строчный JSON‑конфиг для каждого клиента. Конфиг валидируется, версия фиксируется и используется во всех узлах, что позволяет быстро развернуть и передать клиенту, избегая переписывания кода.

Задача

Fixed‑price custom n8n builds often turn into rewrites because each client requests small tweaks, turning a $79 job into many hours of work.

Результат

By separating workflow logic from configuration, the author can deliver fixed‑price custom builds in about two hours of work for $79, maintaining margin and avoiding scope creep.

Рабочий процесс

• 1. Create a single Set node named CLIENT_CONFIG that holds a JSON object.
• 2. Add a Code node immediately after CLIENT_CONFIG that validates the config against a schema and writes the config_version into execution metadata.
• 3. Use the config values in downstream nodes: Gmail trigger filters, LLM prompt assembly, draft formatting, routing, and logging.
• 4. Deploy the workflow and hand off the config file to the client, instructing them to edit only the config, not the workflow.

Доказательства

I refuse to reprice per client, because the moment the price depends on a scoping call, I'm selling hours again.

Источник

The workflow JSON is identical across clients. What differs is the config: Forty lines. A new client is a new forty lines.

Источник

Rule 2: a validator node runs first, always. Right after CLIENT_CONFIG, a Code node validates the config against a schema... An invalid config fails the execution in the first 200 milliseconds with a message naming the exact field.

Источник

Rule 3: stamp the config version on every execution. The validator also writes config_version into the execution's metadata log.

Источник

Total: about two hours of my time for $79.

Источник