Zahurul Islam Book an audit

Available · Dhaka, Bangladesh · US EST/PST & EU hours

Your orders shouldn't be re-typed by hand.

I connect Shopify, BigCommerce and WooCommerce storefronts to Zoho — CRM, Inventory, Books and Desk — so orders, stock and customers sync themselves.

Automations built for the failure path: retries, idempotent writes, error alerting, clean handover.

Book a free automation audit See the work
Zoho Creator Certified Developer Zoho CRM Advanced Specialist 3+ years shipping to production
Md. Zahurul Islam
Md. Zahurul Islam
AI Automation & Integration Engineer
Dhaka, Bangladesh · Remote
Systems I connect
shopify-to-zoho-order-routing· a flow I built and run live
Shopify order.created Webhook POST /orders n8n validate · map · route idempotency key Zoho Inventory sales order + stock Zoho Books invoice Zoho Desk retry ×3, then alert on API timeout

The lower branch is what most demos leave out. Storefront APIs time out eventually, so this flow retries and then opens a Desk ticket instead of silently dropping the order. Drag the canvas sideways to see it all.

01 — Services

How we can work together

Scope agreed before anything is built

Start here

Automation audit

Before anything gets built, we find out what's actually costing you time.

  • Walkthrough of your current stack and handoffs
  • A map of every point where data is re-keyed by hand
  • Written plan naming the most expensive gaps
  • An estimate and a sensible order to fix them in
Free. You keep the plan either way.
Core work

Storefront to ERP integration

Orders, stock and invoices moving between your store and your back office without manual entry.

  • Shopify, BigCommerce or WooCommerce connected to Zoho Inventory, Books, CRM and Desk
  • Retry logic, idempotent writes and failure alerting
  • Workflow exports and credential setup handed over
  • Documentation and a recorded walkthrough
Quoted after the audit, once the scope is actually known.
AI agents

AI agent workflow

An n8n agent that reads, decides and acts on work your team currently does by hand.

  • Ticket triage, lead qualification, research or document extraction
  • Multi-step agent chaining with structured outputs
  • Human review on low-confidence runs
  • Cost monitoring so token spend stays predictable
Quoted after the audit, once the scope is actually known.

02 — Selected work

Three builds, start to finish

Recordings of the real thing running

CASE 01

Shopify orders that land in Zoho Inventory by themselves

n8n · Shopify Admin API · webhooks · Zoho Inventory — Wenexus, 2024–present

Zero
orders typed in by hand
Zero
duplicate sales orders on webhook replay
×3
retries with backoff, then a Desk ticket

The problem

Orders were read off the Shopify admin and typed into Zoho Inventory by hand. Slow, and every mistyped SKU turned into a fulfilment problem days later.

What I built

A webhook-driven pipeline that pulls each order into Zoho Inventory, keeps stock levels synchronised and passes clean data to fulfilment. Writes carry an idempotency key, so a webhook firing twice doesn't create two sales orders. When the API times out the flow retries with backoff, then raises an alert rather than dropping the record.

Shopify order→ Webhook + retry→ Map & validate→ Zoho Inventory
  • Shopify Admin API
  • Zoho Inventory
  • Idempotent writes
  • Error alerting
CASE 02

Abandoned wholesale carts that turn themselves into tracked deals

BigCommerce · WooCommerce · Zoho CRM, Books & Desk — Wenexus, 2024–present

2
storefronts on one recovery flow
4
records per cart: order, invoice, ticket, deal
Zero
carts left without an owner

The problem

Wholesale carts were being abandoned and nothing happened afterwards. No record, no follow-up, and no way to tell how much revenue was sitting there.

What I built

An end-to-end recovery flow spanning both storefronts. One abandoned cart now generates a Zoho Sales Order and Invoice, opens a Desk ticket, notifies the team and logs a CRM deal — so the cart becomes a tracked opportunity with an owner and a next step instead of a dead end.

Abandoned cart→ Sales order + invoice→ Desk ticket→ CRM deal
  • BigCommerce API
  • WooCommerce
  • Zoho CRM
  • Zoho Books
  • Zoho Desk
CASE 03

Six content tools collapsed into one AI agent pipeline

n8n AI Agent · chained LLM calls — Wenexus, 2024–present

6
stages chained in a single workflow
1
handoff left, instead of five
Auto
content audit before a person reads it

The problem

Producing one piece of content meant a person moving between separate tools for keyword research, outlining, GPT research, internal linking, schema markup and a manual quality check. The handoffs between them were where things got dropped.

What I built

A multi-stage agent pipeline in n8n chaining LLM calls across every one of those stages, with structured outputs at each step so the next stage receives clean input rather than prose it has to re-parse. The final stage is an automated content audit that flags problems before a person sees the draft.

Keyword research→ Outline→ GPT research→ Internal links→ Schema→ Audit
  • n8n AI Agent
  • LLM / GPT APIs
  • Structured outputs
  • Prompt engineering

03 — Archive

Everything else I've shipped

Most rows open a recording

  • Unified operations hub Zoho One · Shopify · BigCommerce · WooCommerce Live site
  • Resort management platform React · Node.js · MongoDB · Prisma · bookings and payments Live site
  • Marketing image automation n8n · asset generation Ask
  • Custom middleware services Node.js · REST · OAuth 2.0 Ask

04 — Stack

Grouped by the job it does

Certified where it counts

Automation & orchestration

  • n8n
  • Zapier
  • Pipedream
  • Zoho Flow
  • Monday.com
  • Webhook-driven
  • Event-driven
  • Scheduled

AI & agent workflows

  • n8n AI Agent
  • LLM / GPT APIs
  • Multi-step chaining
  • Prompt engineering
  • Structured outputs
  • Content auditing

E-commerce & ERP

  • Shopify Admin API
  • BigCommerce API
  • WooCommerce
  • Zoho Commerce
  • Order routing
  • Inventory sync

Integration engineering

  • REST APIs
  • Webhooks
  • OAuth 2.0
  • Retry & idempotency
  • Error alerting
  • Run logging
  • Custom middleware

Zoho ecosystem

  • CRM — SDK, widgets, Deluge
  • Inventory
  • Books
  • Desk
  • Creator
  • Analytics
  • Flow
  • Catalyst
  • Commerce
  • Projects

Development

  • Node.js
  • Express
  • React
  • Next.js
  • PostgreSQL
  • MySQL
  • MongoDB
  • Prisma
  • Git

05 — Approach

Why these keep running

The part that separates a build from a demo

Most automation demos work once, on a good day, with a clean payload. Production is not that. Storefront APIs time out, webhooks fire twice, tokens expire at 3am, and someone always pastes a malformed address into a checkout field.

So I build for the bad day. Every flow decides in advance what happens when a call fails: retry, skip, alert, or open a ticket for a person. That is the difference between an automation that saves your team time and one that quietly creates a mess they find on Monday.

I trained as an economist, which shapes the order I work in. Before I open n8n I map the business process and where its cost actually sits, because automating a broken process just produces broken output faster.

Map the process and its cost drivers first, then build the system. The tooling is the easy part.

06 — Experience

Three years in production

Dhaka · remote · US and EU hours

Zoho Automation & Integration Engineer

Wenexus

2024 — present

  • Designed and shipped a production multi-step AI-agent workflow in n8n, orchestrating chained LLM calls across keyword research, outline generation, GPT research, internal link suggestion, schema generation and automated content auditing.
  • Architected a unified operations hub integrating Zoho CRM, Inventory, Books and Desk with Shopify, BigCommerce and WooCommerce, centralising sales, finance and fulfilment data for wholesale and B2B operations.
  • Built Shopify to Zoho Inventory order routing with webhook retry logic and failure alerting, eliminating manual order entry.
  • Designed an end-to-end wholesale abandoned-cart recovery flow across BigCommerce and WooCommerce into Zoho Sales Orders, Invoices, Desk tickets and CRM deals.
  • Developed custom Zoho CRM widgets on the CRM SDK for lead conversion, ticket creation, junk-lead management and email validation.
  • Implemented barcode and document automation across Monday.com, n8n and Zoho Catalyst, generating PDFs and writing results back to project boards.
  • Built operations and sales dashboards in Zoho Analytics covering carton cost tracking, consignment vendor performance and SKU-level sales trends for leadership.

Software Developer

Merinasoft Ltd.

2023 — 2024

  • Developed and maintained full-stack production web applications using React, Node.js, Express and MongoDB.
  • Improved frontend and backend integration through REST API design and Redux state management, owning database operations and query optimisation.
  • Collaborated cross-functionally to ship features on schedule and improve application performance.

07 — Credentials

Certifications and education

Zoho Creator Certified Developer

Zoho Corporation

Zoho CRM Advanced Specialist

Zoho Corporation

MSS, Economics

Begum Rokeya University, Rangpur · 2022

BSS, Economics

Begum Rokeya University, Rangpur · 2020

08 — FAQ

Questions people ask first

What does the automation audit include?

A walkthrough of your current stack, a map of where data is being re-keyed by hand, and a written plan naming the handoffs costing you the most time, with an estimate and a sensible order to fix them in. You keep the plan whether or not you hire me.

Do you only work with Zoho?

No. Zoho One is where I hold certifications and the deepest experience, but the actual job is connecting systems. I build across Shopify, BigCommerce, WooCommerce, Monday.com and anything exposing a REST API or webhook. If your ERP is something else, the integration patterns are the same.

What happens when an automation breaks?

It shouldn't fail silently, which is the real risk. Every flow gets retry logic with backoff, idempotent writes so a duplicate webhook doesn't create a duplicate record, and alerting that opens a ticket or notifies a person when a run fails. You find out from the system, not from a customer.

Can you work US or EU hours from Bangladesh?

Yes, and I already do. I keep overlapping hours with US EST and PST and with European time zones, and have worked this way in my current role. Standups, reviews and incident calls are not a problem.

Do I own the workflows, or am I locked to you?

You own everything. You get the workflow exports, the credential setup, written documentation and a recorded walkthrough, so another engineer can take it over without me. Lock-in is a business model, not an engineering practice.

Are you available for full-time work or contracts?

Both. I take fixed-scope contract builds and I'm open to full-time remote roles. I'm based in Dhaka and work US EST/PST and EU hours. Email me and say which you have in mind.

Md. Zahurul Islam
Md. Zahurul Islam
Replies within a day, in your time zone

Tell me what's still being done by hand.

If your team is copying orders between a storefront and an ERP, or chasing invoices across three tools, describe it in a few lines and I'll tell you honestly whether it's worth automating.

Download CV
eco1603021brur@gmail.com +880 1710-815467 /in/zahurul-islam /zahuruli

Start a conversation

No newsletter, no CRM sequence. It goes straight to my inbox.