One existing workflow. One agreed failure. A repaired export and repeatable test evidence.

Work sample: a synthetic API rate-limit repair, tested with n8n 1.121.3. See the before/after workflows, runnable local fixture, five test cases, and documented limitations: https://github.com/shivanshjain456/n8n-api-retry-demo

See the response-aware lead-write demo: 19 synthetic requests across eight behavior families in n8n 2.47.3, using a local Python/SQLite destination and local alert sink.

Included: reproduce one agreed Code node, webhook mapping, or API configuration failure; repair it within the agreed workflow scope; test the agreed successful case and relevant invalid-input or failure case; deliver the repaired export or documented node changes, test evidence, and a short explanation of the cause and limitations.

Before ordering, send a sanitized workflow export, exact error, n8n version and hosting details, expected behavior, and sample input/output. Remove credentials, tokens, and private client data. Any live test access must be agreed separately and provided securely with minimum permissions. Please message first so we can confirm fit and acceptance criteria.

Delivery: 3 days after the agreed scope, required inputs, and safe test access are complete. Includes one correction within the agreed acceptance criteria.

Excluded: new workflows, redesigns, unrelated bugs, third-party subscriptions, and production changes without agreed rollback and access. No guarantee to resolve external outages. Broader work is quoted separately.

Acceptance: the agreed fixture reproduces the failure before the change and passes after it; the relevant failure case behaves as agreed; and export/change notes and test evidence are delivered. External dependency limits are documented.

Need a new workflow rather than a repair? Ask for a separate implementation scope: discovery and a process map for one incoming lead event, one n8n workflow, one agreed destination API, validation and field mapping, named success/failure checks, an export and a handoff guide. Before a quote, we need the source and destination API documentation, redacted input/output examples, expected record changes, duplicate/conflict rules and safe test access. Replay and retry behavior must match the destination's verified contract. Price, dates, access and acceptance are agreed separately; new implementations are not included in the $100 repair.

Need periodic checks after a repair or implementation? Ask whether a separately scoped, read-only evidence review fits one workflow. The proposed path is two dated reviews in one 30-day period, plus an end-of-period summary of the supplied evidence, observed failures and next decisions. We first validate the evidence format and agree the review dates, corrections to the review report, price and renewal terms. This is an inquiry option, not included repair support, an active monitor or an alert/response-time commitment. Any workflow changes require a separate agreed repair or implementation scope.