You will get your broken Zapier Make or n8n automation fixed and documented
Project details
Someone built you an automation. It worked for a while. Then it stopped, or worse, it kept running and quietly did the wrong thing. Whoever built it is gone, there is no documentation, and nobody wants to touch it.
That is what this project is for.
I trace the run history to find where it actually breaks, rather than patching whatever looks wrong on the surface. Most failures I see are the same handful of causes: a changed API, an expired credential, a step with no error handling, or a race between two workflows that were never meant to run together.
On the Standard tier I fix it and document it. On Advanced I also rebuild the fragile parts properly, with retries, error handling and failure alerts, so you find out the next time something breaks instead of discovering it a week later.
You get a written explanation of what was wrong either way, even if the honest answer is that a rebuild would cost less than the repair. I work in n8n, Make and Zapier, and I can read what someone else built.
That is what this project is for.
I trace the run history to find where it actually breaks, rather than patching whatever looks wrong on the surface. Most failures I see are the same handful of causes: a changed API, an expired credential, a step with no error handling, or a race between two workflows that were never meant to run together.
On the Standard tier I fix it and document it. On Advanced I also rebuild the fragile parts properly, with retries, error handling and failure alerts, so you find out the next time something breaks instead of discovering it a week later.
You get a written explanation of what was wrong either way, even if the honest answer is that a rebuild would cost less than the repair. I work in n8n, Make and Zapier, and I can read what someone else built.
AI Development Type
Software MaintenanceWhat's included
| Service Tiers |
Starter
$150
|
Standard
$400
|
Advanced
$800
|
|---|---|---|---|
| Delivery Time | 2 days | 4 days | 7 days |
Number of Revisions | 1 | 2 | 3 |
AI Model Integration | - | - | - |
Detailed Code Comments | - | - | - |
Knowledge Graph | - | - | - |
Model Documentation | |||
Ontology | - | - | - |
Source Code | - | ||
Taxonomy | - | - | - |
Frequently asked questions
About Uttam
AI Automation Specialist | n8n, Make | Lead Intake, CRM & Support
Dhanbad, India - 11:14 am local time
I build the systems that close that gap, and the ones that handle everything after it.
I'm an automation specialist. I use n8n, Make, and the OpenAI and Claude APIs to connect the tools you already run, including your CRM, inbox, forms, store and database, into workflows that capture, qualify, route and respond without anyone watching them.
WHAT I BUILD
• Lead intake & qualification: a form or call comes in, gets enriched, scored, written to your CRM and routed to the right person, with an intelligent first response inside five minutes
• AI support & response agents: drafts or sends replies from your real customer data, escalating only what genuinely needs a human
• CRM & systems integration: stop paying someone to retype data between tools that should be talking to each other
• Document & data extraction: pull structured data out of invoices, contracts, leases and PDFs at volume
• Ops reporting: one daily digest in Slack instead of five dashboards nobody remembers to open
WHO I WORK WITH
Real estate teams · Law firms & professional services · E-commerce brands · Agencies (white-label)
The intake workflow is the same in all four. A lead arrives, gets qualified, lands in a system, and someone responds fast. What changes is the vocabulary. A brokerage calls it speed-to-lead, a firm calls it client intake, a store calls it support triage.
TOOLS
n8n · Make · Zapier · OpenAI API · Claude API · GoHighLevel · HubSpot · Airtable · Shopify · Zendesk · Google Sheets · Slack · REST APIs & webhooks
HOW I WORK
1. Free 20-minute audit. I map where your manual hours actually go, before either of us commits to anything
2. Fixed-price build. You know the number before I start, with no hourly surprises
3. Documentation and handoff. Every build ships with a Loom walkthrough and written docs, so you're never locked to me
4. 14 days of free fixes after delivery
WHY ME
Most automation freelancers can wire two APIs together but need you to explain your business first. I run the AI and automation for two online reputation management companies, which means the systems I build are ones I also have to live with. When something breaks at 2am, I am the one it wakes up.
That changes how I build. Error handling, retries and failure alerts are not extras I upsell you, they are the difference between a system that works and one that quietly stops.
I'm also a Zendesk Certified Support Admin, which matters most on support automation: I know what a good ticket flow looks like before I automate one.
I'll tell you when automation isn't the answer. Some processes are too irregular to automate well, and a system that breaks quietly is worse than a manual one that doesn't.
Message me with the single manual task eating the most time in your week. I'll tell you free whether it's automatable, roughly what it would cost, and how many hours it would save.
Steps for completing your project
After purchasing the project, send requirements so Uttam can start the project.
Delivery time starts when Uttam receives requirements from you.
Uttam works on your project following the steps below.
Revisions may occur after the delivery date.
Diagnose the actual failure
I trace the run history to find where it breaks and why, rather than patching the symptom. You get a written explanation either way.
Repair, test and document
I fix it, run it against real data to prove it holds, and write up what was wrong and how it works now, so the next person is not guessing.