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

Description and use

The author sells fixed‑price n8n builds for $79 by using a single canonical workflow and a 40‑line JSON config per client. The config is validated, versioned, and read by all nodes, enabling quick deployment and client handoff without rewriting the workflow.

Problem

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

Outcome

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.

Workflow

• 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.

Evidence

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

Source

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

Source

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.

Source

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

Source

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

Source