I will diagnose and repair one existing n8n workflow or one small API automation involving up to two connected external services and one clearly scoped primary failure or missing behavior.
The fixed $75 scope includes:
- inspection of the exported workflow JSON or supplied script
- reproduction using sanitized sample inputs
- correction of workflow logic
- basic error handling
- retry handling where appropriate
- duplicate or idempotency protection where appropriate
- one tested output path
- an updated workflow export or script
- concise setup and handoff notes
The 2-day delivery period begins only after both the LaborX order is visibly funded and the complete workflow export and sanitized test materials have been received.
The Gig includes one clarification/revision of the delivered workflow and handoff notes.
The base scope excludes a complete business-automation platform, multiple independent workflows, paid third-party subscriptions, paid OCR, AI, SMS, voice, or scraping services, API-credit purchases, production credentials, unrestricted database access, customer personal or financial data, anti-bot bypasses, WhatsApp Business approval, Meta app approval, production deployment, permanent hosting, large AI-agent systems, voice agents, authenticated or restricted-site scraping, ongoing administration, and unlimited revisions.
Additional workflows, services, deployment, or larger implementations require a separately agreed and funded contract.
Client requirements:
- exported n8n workflow JSON or current script
- n8n version
- whether the installation is n8n Cloud or self-hosted
- the exact current error or missing behavior
- the expected input and output
- sanitized sample payloads
- approved documentation for the connected external services
- the existing deduplication or storage design, if relevant
- test credentials only after funding and only when genuinely required
Do not provide production passwords, API keys, private keys, seed phrases, unrestricted database credentials, customer data, or unrelated secrets. Where possible, you should enter production credentials personally after handoff.
