Skip to Content

AI Agents & Automation

Workflow automation with n8n, Make and Zapier

Sometimes the right answer is a no-code tool, and I'll say so. When your apps need an integration the tools can't handle, or the volume makes them costly, I write custom code instead. You get a clear recommendation, not whatever I'd like to build.

Updated

Problems this solves

  • Your apps don't talk to each other, so someone copies data from one into another each day.
  • A Zapier or Make setup grew into a tangle that nobody dares touch.
  • No-code costs have crept up as your volume grew, or a task limit keeps stopping the flow.
  • An automation failed quietly weeks ago and you only found out when a customer complained.

What I build

  • n8n workflows, hosted by you or on a managed instance, connecting your SaaS tools
  • Make and Zapier scenarios built cleanly, documented and handed over
  • Custom integrations and webhooks for apps with no ready-made connector
  • Cleanup of an existing tangle of automations into something readable
  • Error alerts and retries so a failure is noticed and fixed, not hidden
  • A move from no-code to custom code when volume, cost or logic outgrow it

How it works

  1. 1List the apps

    We list the tools involved, what should trigger each action and what must never happen by mistake.

  2. 2Choose the tool

    No-code if it fits, custom code if it doesn't. I explain why, including the running costs of each.

  3. 3Build with alerts

    I build the flows with logging and failure alerts, then test them with real sample data.

  4. 4Document and hand over

    You get a diagram of what connects to what, access to every account and a short guide for small changes.

Try it live

Try the lead-to-CRM workflowSubmit a sample lead and watch each step run: enrich, score, route, save, notify. Failures and retries are shown, not hidden.

Work that shows it

Tools I use

  • n8n
  • Make
  • Zapier
  • Webhooks and REST APIs
  • Node.js and TypeScript
  • Python
  • Supabase
  • Google Workspace APIs

Working with clients abroad

I work remotely with clients worldwide from Assam, India, and in person across Assam and Guwahati. Quotes are in USD and paid by Wise or international bank transfer. Code lives in your GitHub from day one, and you get a staging link to try at every step.

Questions

No-code is enough for simple, low-volume flows between popular apps. Custom code makes sense for unusual apps, heavy volume, complex logic or when you want predictable running costs.
Yes. I review what's there, find what is failing or duplicated, and either tidy it or rebuild it, and document it so it stops being a mystery.
Yes. I work remotely with clients in several countries and quote in USD. Payment is by Wise or international bank transfer.
You do. The accounts and any hosting are in your name, and I'm given access only while working on them, which you can remove at any time.
It depends on the number of apps and how unusual their APIs are. You get an estimate after a first call, and a working version to try early.

Tell me what you have in mind, and I'll tell you how I'd build it.