Automation repair · n8n, webhooks, scripts
A broken automation, fixed with a test you can run.
For small teams and agencies whose workflow has stopped working. We reproduce the failure on your redacted samples first. If we can’t, you pay nothing. Then you get a fixed price, the fix, an acceptance test that passes on your side and a rollback to your current version.
- No reproduction, no charge
- Fixed price before any payment
- Deposit refunded if the test can’t pass
| The record that fails today | the correct result |
|---|---|
| A record that worked before | the same result as before |
| A bad or rejected record | an alert, never a false success |
| The same records, run again | no duplicates |
| Roll back to your version | your old behavior returns |
Repair proof · lead cutover
9 of 9 checks pass on a rebuilt Mailchimp → Brevo cutover.
Before we quote, we rebuild the failing workflow on sample data and write the checks it has to pass. We built this one from a publicly posted repair request. It was not a customer job: three existing website forms, one welcome email, no duplicates.
| # | Situation | Observed result |
|---|---|---|
| 01 | Before the cutover | PASS One popup lead reaches Mailchimp only and gets its welcome. Brevo: 0. |
| 02 | Same person, four spellings, three forms | PASS 1 Brevo contact, 1 welcome, 0 Mailchimp calls. |
| 03 | Invalid email address | PASS Alert raised; no contact created. |
| 04 | Brevo rejects the lead (400) | PASS Alert raised; no contact created. |
| 05 | Brevo rate limit (429) | PASS Retried once after a pause; contact and welcome created once. |
| 06 | Brevo says OK but saves nothing | PASS The check reads the list back, fails, and alerts. |
| 07 | Old Mailchimp route left on | PASS Two welcomes detected and flagged. Route off: one welcome, no alert. |
| 08 | Roll back to the old version | PASS The next new lead goes to Mailchimp again. |
| 09 | Vendor failures on demand | PASS The test double replays 401, 429, a renamed field and a second page. |
| — | Can the checks fail? | With the duplicate-welcome detector removed, check 07 fails. The check is doing the work. |
9 / 9 pass
Each check makes one real situation happen and records what the workflow did. A check that cannot fail proves nothing, so the last row removes a detector and shows its check failing.
This is a rebuild, not the requester’s own scenario, accounts or mail. An alert here flags a failed lead but does not store it for replay; on a real job that is part of the hardening scope.
How a repair runs · five steps
You pay after we have reproduced it.
The clock starts only when the scope, your samples and the access route are agreed. Anything outside the written rows is quoted separately before we do it.
You send the export and samples
The workflow export or code with credentials removed, and 5–10 redacted or made-up records, including one that fails today, with the output each should give.
We reproduce the failure
On your samples, before asking for money. If they don’t reproduce it, we say so and you pay nothing.
You accept a fixed price and the rows
A written scope, the acceptance rows and the number of business days. You pay 50% when you accept them.
We hand over the fix
The working change, an error path with an alert, your previous version saved for rollback and a one-page handover. If you apply it yourself, we include an apply script.
You run the rows
The other 50% is due when they pass on your side. If we cannot make them pass within the agreed days, the deposit is refunded in full.
Scopes · one fixed price per job
Three sizes of repair.
We confirm the scope after reproducing the failure, then quote one fixed price for it. If the platform’s own feature can replace the part that broke, we quote that smaller job instead, or tell you how to do it yourself.
- Scope 1
Fix
One failing step or connection: an expired login, a field renamed by an app update, pagination, a changed payload, a missing retry.
Acceptance rows on up to 10 of your records, an alert instead of a silent failure, rollback and a handover note.
- Scope 2
Fix + harden
The fix, plus the whole workflow (about 20 steps, up to 3 connected apps): no duplicates on re-run, retry with back-off and an error queue.
Replay of the records that failed during the outage, where the source or the provider still holds them. We tell you in writing which ones cannot be recovered.
- Scope 3
Fix + harden + custom step
Both of the above, plus one custom code or API step, such as an OAuth refresh, cursor pagination or signature check, with unit tests.
A 7-day watch after handover, with one fix for the same kind of failure.
Each job runs on a written scope and acceptance sheet you confirm before paying. A failing row you report within 5 business days of handover gets one fix cycle; the Fix and Fix + harden scopes include 7 days of support for the same failure.
Fit · before you write
If a free answer fixes it, use it.
We are worth paying when the free answers haven’t worked, when records were missed or duplicated, or when you need proof that it is fixed.
We take
- n8n workflows, webhook and HTTP API integrations, and scripts in Python, JavaScript or Google Apps Script.
- Zapier or Make, when you can share a test workspace or an export with sample payloads.
- A named failure in a workflow that used to work, or was half built, where “fixed” can be written as input → expected output.
We decline
- Health, payment-card or government-ID data.
- Writes to a production database, or credentials we cannot limit to this workflow.
- A new build, an AI-agent product, a data migration or “make it smarter”.
- A failure we cannot reproduce from what you can share.
Start with the samples
Send the export. We reproduce it first.
Remove credentials from the export. Use redacted or made-up records, and include one that fails.
Email redacted samplesOpens an email to hello@cybernative.ai. Never send passwords, API keys, health records, card numbers or ID numbers.