I will fix broken n8n workflows and add error handling

Please send (1) your workflow export JSON (or screenshots if you can’t export), (2) what you expect vs what happens now, (3) 1–3 sample inputs and the current outputs, and (4) where you want alerts/logs (Email/Telegram + Google Sheets/Postgres).

No. Work is done on a copy first, then tested. After you approve, changes are applied to production (or you can apply them yourself using my delivered JSON + instructions).

The updated n8n workflow JSON, a short report on what was wrong and what changed, and setup or handoff instructions. Fix + Alerts also includes the agreed error alerts and recovery path.

One n8n workflow file (one workflow ID) with its internal nodes. Connected workflows count separately unless agreed. An issue is one distinct error or failing node: Quick Fix covers 1, Fix + Speed-up 3, Fix + Alerts 6.

Yes. This includes incorrect tool selection, wrong output format, missing required fields, and improving prompts/logic so the agent follows the intended steps.

Yes, in Fix + Alerts: structured error handling, failure alerts by Email or Telegram, and optional logging to Google Sheets or Postgres. Quick Fix and Fix + Speed-up fix the errors only; alerts can be quoted as an add-on.

A separate fallback route. When the main workflow fails, it stores the failed input safely, alerts your team, or handles the critical step until the main workflow is fixed. It is not server uptime or high availability. It is included in Fix + Alerts.

Revisions follow the package you purchase. A revision covers adjustments to the delivered workflow within the original agreed scope. New workflows, new integrations, additional features, or changed requirements are considered separate scope.

Fix + Alerts includes 7 days of free fixes for defects caused by my changes, within the original scope. On Quick Fix and Fix + Speed-up, later fixes are quoted. Every package includes basic guidance to import, configure and test. Monitoring and new integrations are quoted separately.

Multiply hours lost per week x hourly cost x 52, then add the cost of each failed run. If a broken workflow costs you more each month than the package, the repair usually pays back quickly. Send me your numbers and I will give an honest estimate.